This only applies to Linux. This problem does not happen on Windows:
When trying to start up the SpectroSERVER on landscape the following error is encountered: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SPC-OPC-10049: The SpectroSERVER process terminated with a Segmentation Violation. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This happens given the following scenarios (SCP is Spectrum Control Panel):
1. If the SS is stopped via stopSS.pl script and started via remote SCP, processd crashes
2. If the SS is stopped via the SCP, it will then start properly via the same SCP.
3. If the SS is stopped via SCP and the SCP is closed and a new one opened, starting the SS crashes processd
4. If the SCP is started, then SS is stopped by stopSS.pl, and you don't close SCP, you can properly start the SS via SCP.
5. If the SS is running, and you stop it via the SCP, then close or relaunch the SCP, processd crashes.
This was due to a change made for logging VNM.OUT files and the way the $SPECROOT/lib/SDPM/SS.idb file is read.
This is tentatively scheduled to be fixed in CA Spectrum release 10.3.2 once released in 2019
SS will not start using remote SCP on linux if SS is down
As a temporary solution, please utilize the $SPECROOT/bin/startSS.pl script on the SpectroSERVER to start the remote SS.