If event.cache file in streamcache of PatrolAgent 9.6.00.1i reaches to filesize bigger than 10 Mb, a reboot of the machine can cause the streamcache to get corrupted and not allow PatrolAgent to startup automatically after reboot. Fix_cache tool crashes when running it to repair the streamcache. |
A manual start of the Patrolagent service should be able to make the Patrolagent to start up. If that doesn't happen, and the fix_cache -p <port> utility is not able to repair the event cache file, to start the PatrolAgent then rename first the %PATROL_HOME%\log\streamcache\servername>\<port> directory with a different name, and then start the PatrolAgent service so that PatrolAgent creates a new streamcache directory. The reason for the streamcache files growing must be investigated. One reason could be the EventCell specified in the "/EventSetup/Configuration/EventCells" agent config var maybe incorrect and therefore causing the PatrolAgent to send all events to the cache as the cell specified is unreachable. Or if the cell name is correct, then it could be the cell has been stopped for long time and events are being cached up. BMC is currently working to get both issues (Patrolagent not starting up automatically after reboot, and fix_cache utility failing) solved. |