0 Replies Latest reply on Feb 6, 2013 9:08 AM by dmease729

    Linux ePO agent - cma log - Trying to start http server thread -> Failed to bind socket -> Failed to start listen server

    dmease729

      Hi,

       

      I noted that this doesnt appear to be listed anywhere when trying to search, so I thought I would post this just in case it helps anybody in the future.  Agent log after an install showed the following every 20 seconds:

       

      2013-02-05 11:38:44 [9482]  [ListenServer]  [I] Trying to start http server thread 164411320

      2013-02-05 11:38:44 [9482]  [ListenServer]  [I] Started http server thread. Thread object is  -186601072

      2013-02-05 11:38:44 [31634]  [ListenServer]  [E] Failed to bind socket. Error number 98

      2013-02-05 11:38:44 [31634]  [ListenServer]  [E] Failed to open socket

      2013-02-05 11:38:44 [31634]  [ListenServer]  [E] Failed to start server

      2013-02-05 11:38:44 [9482] [ListenServer] [I] Failed to start listen server, will retry in 20 seconds

       

      As the only port I would suspect the agent to try to listen to was 8081/tcp I was guessing that the port was in use.  This could be shown as below.  The first of the below shows the output from a system where these errors do not occur, and the second shows output from the system that was seeing the above errors in /opt/McAfee/cma/scratch/etc/log:

       

      System without the issue:

      (host)#netstat –tupln | grep 8081

      tcp          0              0              0.0.0.0:8081        0.0.0.0:*               LISTEN  6870/cma

       

      System with the issue:

      (host)#netstat –tupln | grep 8081

      tcp          0              0              0.0.0.0:8081        0.0.0.0:*               LISTEN  16086/java

       

      On the second host we can see that the java process is already listening on port 8081, therefore the ePO agent software cannot bind to this port.  A linux admin asked if this would be an issue on further boots (ie would the agent kick in first, and stop the java process from listening on this port, potentially killing something else).  I advised that the default run level and appropriate rc directories (or files, depending on specific OS) would need to be checked to confirm.  Another alternative would be to try to make java use a different port, but that would involve further investigation with regards to why it is actually using this port.

       

      Hope this helps somebody in the future!