I am using the vCO appliance and recieve these errors weekly, which cause the services to crash.
The system is setup with 12GB of RAM and the java wrapper is set to 10240MB. Not sure where to look for this memory leak and what is consuming all the resources. Any help would be greatly appreciated.
Also looked at this link http://www.vmware.com/support/orchestrator/doc/vcenter-server-plugin-5011-release-notes.htmland looked into the below workaround.
For line 4 mine is set to 256m
and for line 5 mine is set to 512
These were set before looking at this file. I didn't not lower them because i was unsure what that would do.
The vCenter Server 220.127.116.11 plug-in might run out of memory
The vCenter Server 5.0 plug-in might run out of memory with an
OutOfMemory error message when you configure it to work with vCenter Orchestrator 4.1.
Workaround: Modify the
jetty-service.conf file on the machine on which the Orchestrator server and the vCenter Server 5.0 plug-in are installed.
These settings are for the configurator service. From the log you posted it looks like the orchestrator server is running out of memory. Look at its startup script what are its current memory settings. I think by default it was 2GB.
By the way - it is actually OS which is running out of memory and not the orchestrator. There are other processes killed also. Use top or whatever tool you have to find out where the memory was consumed. If this is VM with vm tools installed you may also consider the memory balooning.
The system usually crashes after a Nessus scan is ran on the system. I just watched it using top while the scan was in process. Before the scan it was using about 2GB of RAM. After the scan it had about 64MB of RAM free. The process that consumed all the resources was va-proxy. After about 3-5 mins after the scan was over all the resources were released. But before the resources were released vcod service stopped and and kicked me out of the vCO client. Any idea of how to prevent this from happen while being able to scan the sytem still?
Probably the Nessus scan uploads large data or does other similar things. To prevent killing of processes you may need to do some or all of this steps:
Hope this helps.
BTW 10GB for the java seems reasonly high, why did you reseved so much memory for the java?
Message was edited by: dimitrovg, hit submit by mistake