Just wanted to put together a clip that covers this condition which can be seen on Unix clients for Simpana 9 and Simpana 10. The steps to resolve it on both versions are exactly the same.
This condition is typically seen when Simpana services do not get shutdown cleanly. Maybe the system never ran all the init scripts during shutdown including ours, or the system wasn’t shutdown cleanly.
What will happen in that condition is that on the next simpana services start you will get an error as shown below;
**** There is already another simpana running.
However if you run a “simpana list” you’ll notice that no simpana services are running despite the failure to start up and the error indicating simpana is already running.
Our software during start up will create a lock file, which is referenced and checked at start up. If it exists you will get the message. During shutdown its removed.
Best way to find out the name of the lock file is to take part of the error message and grep for it in the simpana script. Make sure your in the correct path when you grep for it. i.e. default install location is /opt/simpana/Base
cat simpana | grep "There is already another simpana running"
From the output shown you will see the full path to the file and the filename we test exists. Please watch the video clip below for a complete walk through.