Agent suddenly aborts with Excessive Virtual Memory Use in the agent.log file. What is causing this?
This is a known Sun bug that says that MIB-II Instrumentation module may cause the Agent to grow. A workaround is to unload the MIB-II Instrumentation module and load the Simple MIB-II module. If the Agent is still growing unload the Simple MIB-II Module. 4.10 My Event Manager is terminating soon after starting up, and its logfile contains this message: “unable to open lockmgr session”. What is probably happening is that the SyMON lockmanager process was only able to partially initialize itself. This happens when it cannot write a status message to /dev/console. You can verify this is the problem you’re having by seeing if a) the lockmanager is running (ps -ef | grep lm_), and b) this file doesn’t exist: “/var/opt/SUNWsymon/db/eventmgr/log/evLckMgr”. If you’ve verified a) and b) then for some reason /dev/console cannot be written to. You can check this by running “echo Testing >> /dev/console” and noticing that this command blocks forever. One possible cause of this is because the perm
Related Questions
- How do I file a complaint against a mortgage broker, mortgage banker, mortgage agent, escrow agency, escrow agent, loan modification consultant, foreclosure consultant or covered service provider?
- Agent suddenly aborts with Excessive Virtual Memory Use in the agent.log file. What is causing this?
- Do I need to set any environment variables in the agents script or file in order to manage objects?
