5 Replies Latest reply on Sep 10, 2010 4:49 AM by rackroyd

    Problem: EPO 4.5, Agents able to update DATs but not policy updates

      An interesting problem this one.

       

      I noticed this morning that clients are able to contact the server to update their DATs (1st screenshot from my machine), but cannot connect to the EPO on their regular cycle to get policy updates and send events (2nd screenshot from my machine).

       

      Looking at the log on the client machine I noticed that the server was reporting back as busy

       

       

       

      2010-09-09 09:30:12  i          #4076  Agent  Agent is connecting to ePO server

      2010-09-09 09:30:12  I          #4076  imutils Trying with site: 10.161.191.9:83

      2010-09-09 09:30:12  I          #4076  naInet  HTTP Session initialized

      2010-09-09 09:30:12  I          #4076  imsite              Upload from: C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Unpack\pkg00129284946126760000_3113113718.spkg

      2010-09-09 09:30:12  I          #4076  imsite              Upload response target: C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Unpack\pkg00129284946127850000_2237799213.spkg

      2010-09-09 09:30:12  I          #4076  naInet  failed to receive package..server is busy

      2010-09-09 09:30:12  I          #4076  imsite  NaInet library returned code == 12

      2010-09-09 09:30:12  I          #4076  naInet  HTTP Session closed

      2010-09-09 09:30:12  e          #4076  Agent  Agent failed to communicate with ePO Server

      2010-09-09 09:30:12  i          #4076  Agent  Agent communication session closed

      2010-09-09 09:30:12  I          #4076  Agent  Agent communication failed, result=-2400

      2010-09-09 09:30:12  I          #4076  Agent  Exponential retry in 961 seconds, error=-2400(Unable to connect to ePO Server)

       

      After some hunting about I tried a restart of the web server on the epo server, Apache, by restarting the McAfee Epolicy Orchestrator 4.5.0 Server Service. This seemed to return things to normal.

       

      However what is going on? why did the epo server stop responding to policy update requests and what can we do to stop it happening again?

       

      Any thoughts / ideas much appreciated.

       

       

       

       

       

      Message was edited by: Geascian on 09/09/10 07:32:19 CDT