The problem is seen more often in older versions of Spectrum before Spectrum 10.0 because of the limitation of 32bit memory for the SpectroSERVER process.
However the same problem can be seen in newer versions of Spectrum as well.
Why does the SpectroSERVER shut itself down very quickly after startup with an error message in the VNM.OUT that it was unable to allocate a very small amount of memory (11 bytes)? In the VNM.OUT I can see that the SpectroSERVER has printed this stack after shutting down.
Jul 18 13:16:17 ERROR TRACE at VNM.cc(797): S:/CA/SPECTRUM/SS/SpectroSERVER.exe is out of memory while allocating 11 bytes. Scheduling shutdown.
Jul 18 13:16:20 ERROR TRACE at VNM.cc(841): C:/SPECTRUM/SS/SpectroSERVER.exe is out of memory while allocating 12 bytes. Continuing shutdown.
CA memory allocation error. Aborting.
The cause of this excessive memory consumption in a very short time is due to an excessive number of traps that are being sent to the SpectroSERVER. Spectrum does have trap storm alarming and suppression built in, but Spectrum as designed, must first read the traps, which uses memory, in order to know that it is part of a trap storm and not a valid trap. This causes the memory exhaustion and will eventually use up all of the free memory and Spectrum will shutdown as a result.
You will need to locate the devices that are sending an excessive number of traps and resolve the problem that causes them to send the traps to Spectrum.
If it is not known or it is not possible to resolve this problem the only option is to disable all trap processing on the SpectroSERVER.
You can do this by editing the .vnmrc file ($SPECROOT/SS) and changing the option:
This will allow the SpectroSERVER to start up and it shouldn´t crash as it is not processing traps.
Alternatively you can also change the SNMP Trap Port number in the .vnmrc file
This will also stop Spectrum from receiving traps on the default port of 162.
Once the devices have been identified that are sending excessive traps via wireshark or tcpdump, you can stop the SpectroSERVER and change back these settings to the original values of empty (default).