Hello, I am going to post this "idea" on behalve of multiple customers including @bheinsius, @JuanS_OCS and I ran into it myself once or twice too:
At Linux crash, existing pid or lock files prevent sas services to start.
When a Linux server containing SAS 9.4 processes (M0 - M4), and pid files or lock files (exmaples below) are not being deleted, the sas services might be prevented from starting in the following case:
When the pid file contains a proces number of a process that is running (with a different service): For example when my /opt/sas/config/Lev1/SASMeta/MetadataServer/server.sas.pid file has pid 4964, and my server crashes, and the server restart, having a process like /usr/sbin/crond (system service) running on the proces id 4964 (the old metadataserver pid), then my metadataserver will not start, until I manually remove the .pid file;
A list of pid files that make the basic sas installations to crash are:
The customer(s) think(s) when a server is stopped, or when a server is started, these pid files and lck files should be taken care of in a more graceful way than SAS services not starting. I.E. Adding it to the SAS startup script or the Linux OS boot services.