Sentinel: Diagnosing SONIC

  • 3946236
  • 05-Sep-2007
  • 26-Apr-2012


Microsoft Windows Server 2003
Microsoft Windows Server 2000
RedHat Linux
Solaris 9
Sentinel 5.1.x


Diagnosing SONIC
Problems connecting to the Sentinel Communication Service
A lock was found on the "esecDomain" domain storage. (Message found in the log file for Sentinel Communication service: %ESEC_HOME%\3rdparty\SonicMQ\MQ6.1\esecDomain.esecContainer.log)


Troubleshooting steps:
1. Is the configuration.xml file pointing to server with Sonic on it? (configuration.xml is found on Windows in %ESEC_HOME% or Unix/Linux in $ESEC_HOME)
2. Is the information in the configuration.xml ip address or hostname?
3. If it is hostname, try the ip address.
4. If it is ip address, is a ping successful?
5. If the above steps are working bring up $ESEC_HOME/3rdparty/SonicMQ/MQ6.1/bin/ or startmc.bat on the Sonic server and see what connections are showing.
6. If it looks like nothing is being received make certain that that global filter is not set to drop everything.
7. If login fails, check the various DAS logs for errors.
8. If the DAS logs have a message that the sonic broker has not started. Stop sentinel and all esec processes. On Unix/Linux you can use "ps -ef | grep esec" to see all the processes. Kill any processes left after stopping the system with the or on Windows after stopping all services in the services control . Then go to /ESEC_HOME/3rdparty/SonicMQ5.0/esecDomain/data/_MFSystem and remove the lock file in that directory. Once the lock file has been removed restart the system and test the connections.