Siebel Administration >  Crashes during startup and shutdown of Siebel server

Siebel crashes during startup and shutdown are quite common.
These crashes are easy to identify.
The thread ID is always 1 and in many cases they can be ignored.
The most frequent reason for these crashes is when you type a ./stop –ALL command to shut down all siebel servers in a group.
Another reason is that in the Siebns file, the minserver and maxserver values are different.
Siebel advises that these values should be the same.
If you choose to make minserver=maxserver,
one problem that we faced is that starting Siebel servers took much longer than before.
The other way to find out that this crash occurred would be to check the callstack file size.
It should be 620 bytes with this content.
/apps/siebel/8.1/siebsrvr/lib/libsslcosd.so:0x4b344
/opt/ibm/ldap/v6.0/lib/libc.so.1:0xc8d08
/opt/ibm/ldap/v6.0/lib/libc.so.1:0xbd3a0
/opt/ibm/ldap/v6.0/lib/libc.so.1:0xbd588
/apps/siebel/8.1/siebsrvr/lib/libsslcshar.so:__1cISSstring2T6M_v_+0x8 [ Signal 11 (SEGV)]
/apps/siebel/8.1/siebsrvr/lib/libsscfcli.so:0x1f4ba0
/opt/ibm/ldap/v6.0/lib/libc.so.1:_exithandle+0x40
/opt/ibm/ldap/v6.0/lib/libc.so.1:exit+0x4
/apps/siebel/8.1/siebsrvr/bin/siebmtshmw:app_main+0x798
/apps/siebel/8.1/siebsrvr/bin/siebmtshmw:main+0x128
/apps/siebel/8.1/siebsrvr/bin/siebmtshmw:_start+0x108

Note that most lines in the callstack write down your application folder path,
if you have a shorter installation path or longer one, the callstack file will change slightly.