cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Hi,

we moved or EPO server to another VMWare server host (hardware change). The VMWare image was copied to the new host and the former MAC was restored. The VMWare image icluding IP address was not modified. After moving the EPO server starts without problems. Also the master repository update works fine. The logon to the EPO console is also working.

But the communication between EPO server and client agents doesn’t work. The agent monitor shows “Agent failed to communicate with ePO Server”.
I also tried to push or install the EPO agent to a new testing client. If I try to push using the EPO console no communication is performed. If I install a fresh created agent installer package I get the same error message in agent monitor. I also checked the configured and used communication ports 81, 8081, 8443 and 8444 between agent and server without problems (telnet eposerver port).

The local stored EPO agent log shows the following:

...

2012-04-20 09:57:26.492 I #456 Agent Started processing a package..
2012-04-20 09:57:26.492 I #456 Agent Preparing Props Version Package
2012-04-20 09:57:26.508 I #456 Agent Collecting IP address using Internet Manager
2012-04-20 09:57:26.539 I #456 naInet HTTP Session initialized
2012-04-20 09:57:26.539 I #456 imsite Connecting to site: 10.200.200.200 on port: 81
2012-04-20 09:57:26.554 I #456 naInet HTTP Session closed
2012-04-20 09:57:26.570 I #456 SpiPkgr Using sequence number 12513
2012-04-20 09:57:26.570 i #456 Agent Agent communication session started
2012-04-20 09:57:26.570 i #456 Agent Agent is sending PROPS VERSION package to ePO server
2012-04-20 09:57:26.570 i #456 Agent Agent is connecting to ePO server
2012-04-20 09:57:26.601 I #456 imutils Trying with site: 10.200.200.200:81
2012-04-20 09:57:26.601 I #456 naInet HTTP Session initialized
2012-04-20 09:57:26.601 I #456 imsite  Upload from: C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\McAfee\Common Framework\Unpack\pkg00129793822464920000_419585352.spkg
2012-04-20 09:57:26.601 I #456 imsite  Upload response target: C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\McAfee\Common Framework\Unpack\pkg00129793822465700000_3846297733.spkg
2012-04-20 09:57:26.664 I #456 naInet failed to receive package..server is busy
2012-04-20 09:57:26.664 I #456 imsite NaInet library returned code == 12
2012-04-20 09:57:26.664 I #456 naInet HTTP Session closed
2012-04-20 09:57:26.664 e #456 Agent Agent failed to communicate with ePO Server
2012-04-20 09:57:26.664 i #456 Agent Agent communication session closed
2012-04-20 09:57:26.664 I #456 Agent Agent communication failed, result=-2400
2012-04-20 09:57:26.664 I #456 Agent Exponential retry in 1024 seconds, error=-2400(Unable to connect to ePO Server)
2012-04-20 09:57:26.664 i #456 Agent Agent will connect to the ePO Server in 17 minutes and 4 seconds.
2012-04-20 09:57:28.398 I #464 Agent Sending the next batch of immediate events
2012-04-20 09:57:28.398 i #464 Agent Agent is looking for events to upload

...

What can I do next to check or solve the problem? Thanks.

Best regards and greetings from Germany

Janni

1 Solution

Accepted Solutions

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Hi,

the RAM update has solved the problem ! Thanks for help and have a nice weekend.

Regards Janni

View solution in original post

9 Replies
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 10

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Where is the ePO database? Is it on the same machine as the ePO server, or a separate SQL server?

What does the server.log say at the time that an agent is trying to communicate?

Thanks -

Joe

Highlighted

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Hi,

thanks for fast answer. The SQL EPO database is on another server and wasn't moved or modified.

The server log shows a lot of this lines:

20120420104010 E #04164 mod_epo  Server is too busy (245 connections) to process request

20120420104011 E #04404 mod_epo  Server is too busy (245 connections) to process request

20120420104012 E #04476 mod_epo  Server is too busy (245 connections) to process request

20120420104013 E #04700 mod_epo  Server is too busy (245 connections) to process request

20120420104013 E #04164 mod_epo  Server is too busy (245 connections) to process request

20120420104014 E #04700 mod_epo  Server is too busy (245 connections) to process request

20120420104015 E #04144 mod_epo  Server is too busy (245 connections) to process request

We also restarted the database after shutting down the EPO. Without success.

Regards Janni

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 10

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Can you stop the ePO services, rename server.log and orion.log, then start the services again. When you are able to log in to the console, can you zip and attach the new server and orion logs? This should give us a matched pair of log files starting from a clean start...

Thanks -

Joe

Highlighted

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Hi Joe,

I just phoned with McAfee gold support. They told me that error 2400 is a RAM problem of the EPO server. We currently use 2 GB for round about 6.000 clients. But on the former VMWare hardware the EPO had no problems with 2 GB RAM installed on server 2003 std. Now we try to rise up to 4 GB RAM. Let'S hope that the problem will be solved after RAM upgrade.

Regards Janni

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 6 of 10

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Well, strictly speaking, 2400 means "I can't communicate" - but the "mod_epo  Server is too busy (245 connections) to process request" errors can certainly be caused by a lack of resources on the server, which in turn would cause the communication problems.

That said, 2GB is definitely on the low side - we specify 1GB available RAM as a minimum for ePO 4.5, and 2GB available for 4.6 - but these are definite minimums, and we recommend at least double this for adequate performance. Hopefully increasing the RAM will help.

Regards -

Joe

Highlighted

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Thanks for your answer. I let you know about the result...

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Hi,

the RAM update has solved the problem ! Thanks for help and have a nice weekend.

Regards Janni

View solution in original post

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 9 of 10

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

Glad to hear it

You too -

Joe

Highlighted

Re: EPO agent-server communication problem after moving EPO server to another VMWare hardware

Jump to solution

I received the same errors in my logs but it had nothing to do with amount of RAM. Mine occured after we changed the domain membership of the ePO server. For some strange reason a new Agent Handler was created which had the FQDN of the new hostname, this made a total of two agent handlers both with the same IP and NETBIOS name but different FQDN's. After I enabled the new Agent Handler and sent a wakeup call using 'All agent Handlers' devices bagan to report in. I'm going to give it a few days before I disable the original agent handler and eventually delete it.

Unfortunately I didn't perform the domain change and don't know too much about it's prior state. I was called in to fix the mess so don't know how this all happened.

Hope that helps.

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community