I'm trying to test the implementation of Arcsight ESM 6.5c in Centos in a virtual machine before doing it in production system. but while installing the manager I'm getting this error " waited too long for the manager to be up ". I have given 4gb memory, 100 gb hard drive, configured static IP for the virtual machine and host name is resolvable but still i'm unable to solve this issue. Please find the screenshot of the error below
I have found below in /opt/arcsight/manager/logs/default/ServiceStatusChecker.log
[2014-10-21 04:30:57,131][INFO ][default.com.arcsight.common.services.ManagerRPCChecker] Ending status checks of manager rpc
[2014-10-21 04:30:57,133][INFO ][default.com.arcsight.common.services.ManagerChecker] Finished status check: manager: unavailable [
manager rpc: unavailable
manager heartbeat "managerup": unavailable
manager heartbeat "server": unavailable
manager heartbeat "server.starting": unavailable
Can anyone please help me. Thanks in Advance.
You need to look into the server.std.log and server.log to get more information.
Look in the /opt/arcsight/manager/logs/default/ folder.
Also, was the mysql database up and running at that point? The logs above should be able to give you more information.
Bump up the RAM to at least 6GB as I have seen ESM 6.5c refuse to start with less than that in a VM environment. Don't expect it to be in any way fast with less than 8GB though as it will be constantly swapping to disk, which is still useable to some degree if you have the VM on an SSD.
I faced that exact same problem while testing out 6.0c a while ago. It's simply because the manager doesn't have the time to start in the allowed period by the installer.
But I was infact able to manually launch the remaining parts and everything worked out ok. I don't remember the details, but you can manually start the web server config, which is the only part remaining. Or maybe there is a variable somewhere you could trick to change the timeout.
I see you're testing with ESM 6.0
I have tested with ESM 6.5c SP1 in my environment using at least 10G of RAM and 4 CPU Cores and have not had major problems.