Symptom
- main instance was stopped because a planned operation (Linux system patch)
- system uses a script during start-up and shutdown according to Sysam Users Guide : 7.10 Running a License Server Automatically on UNIX Systems (https://help.sap.com/doc/download_multimedia_zip-esp_51sp11_esp_sysam_pdf/5.1.11/en-US/esp_sysam.pdf)
- script different from the provided template and does not contain a log redirection for troubleshooting errors
- the license server did not restart from /etc/init.d
- a few mins later the secondary license server in the quorum assumes the master role and established connection with the tertiary server in the quorum, but soon exited with status 127 when trying to start the vendor daemon. It tried several times to restart the daemon but failed with the same status
- finally lost connection to the tertiary server and exited with error "EXITING DUE TO SIGNAL 127 Exit reason 95"
Read more...
Environment
SYSAM 2.4 - FlexNet Licensing (v11.14.0.0 build 183228 x64_lsb) (linux)
Running on Hypervisor: VMWare
Product
SAP Adaptive Server Enterprise 16.0
Keywords
signal 127, reason 95, unknown status, lmgrd fails to start , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.