This content has been marked as final. Show 13 replies
no problems here - what are the specs of the server?
when did u move it to a vmware server - before or after the 3.6.1 upgrade?
The server has been moved to VMware for some time, since running 3.5, and has been running OK, the upgrade to 3.6 went ok, but has been running terrible since 3.6.1
the spec is a 3Gb CPU, but has only 750MB RAM allocated.
you running sql as well - not much memory allocated there.
I will be upgrading the allocated memory, will upgrade this to about 2gig, but need to confirm this with our server team.
The SQL database is not actually on this box, we have a dedicated SQL server(s) that handles this task
I have had our server team allocat 2Gb RAM, and allow more CPU sharing on the VM server.
But still the Apache and Tomcat service are still causing the server to run at 100% CPU
Please can someone help
I has something simliar not long after my upgrade to 3.6.1, apache started using close to 100% and apache and tomcat started using 1GB of mem instead of 10's of MB. The I found some idiot had sabotaged our SQL cluster and apache was having problems authenticating with the database, got them to sort it and restarted services.. no more issues.
Doesnt have to be the EPO server at fault to max these out it could be bad agents, lots of task traffic or SQL database/network connectivity.
I'd check the SQL first as its probably the easiest to rule out.
I have passed this onto our server guys, hoping they can resolve this.
Just a thought, did you have McAfee VirusScan installed on the server when you upgraded to the new EPO version?
I had a similar problem when testing a upgrade to EPO 3.6.1 from EPO 3.5.0. McAfee tech support told me that the McAfee VirusScan on the server was putting a time delay in the jar files thus affecting Tomcat/Apache. They suggested that you uninstall the McAfee VirusScan from the server during the upgrade to prevent this issue.
AV has been installed on the server for some time, even from the time of running ePO 3.1.
I will want to rule out the SQL server before uninstalling AV, ePO and redeploying ePO once again.