I just wanted to give you a heads up on an issue being seen at a few sites. In 10.3 we removed the need for the SpectroSERVER and processd to be owned by the root user. During the install, processd is started as root. When it starts, it creates the $SPECROOT/lib/SDPM/runtime directory and it is now owned by root user. When processd is started as the spectrum install owner, this can cause issues such as the child processes not stopping when you issue processd.pl stop. Also, you may see that when you try to stop the SpectroSERVER with the stopSS.pl script, you will see this message:
Archive Manager is not running SpectroSERVER is not running
This will be fixed in the next release of Spectrum. The workaround is to stop the processd, delete the $SPECROOT/lib/SDPM/runtime directory, then start processd back up as the spectrum install owner.
BTW, in case it's needed:
To see if this is affecting you on 10.3, just navigate to the $SPECROOT/lib/SDPM directory and run a long listing (ls -al) and see if root owns the runtime directory. If it does, please apply the workaround. If it is owned by your spectrum install owner, you are good to go.
Archive Manager is not runningSpectroSERVER is not running