SAP Knowledge Base Article - Preview

3587376 - LNX: FAIL: Service start failed: systemdI_msg_handler

Symptom

  • After new SAP installation on new server, SAP instance fails to startup due to error: 
    FAIL: Service start failed: systemd_msg_handler: job '/org/freedesktop/systemd1/job/417118' canceled with 'failed' 

  • The SAP service (SAP<SID>_00.service) related journal content gives following error:

    Mar 10 11:12:13  systemd[1]: Starting SAP Instance SAPXXX_00...
    Mar 10 11:12:13  SAPXXX_00[621505]: Unable to open() the lock file /tmp/.sapstartsrv00_sapstartsrv.log. (Error 13 Permission denied)  
    Mar 10 11:12:13  SAPXXX_00[621505]: Unable to open trace file sapstartsrv.log. (Error 13 Permission denied)  
    Mar 10 11:12:13  systemd[1]: SAPXXX_00.service: Main process exited, code=exited, status=1/FAILURE
    Mar 10 11:12:13  systemd[1]: SAPXXX_00.service: Failed with result 'exit-code'.
    Mar 10 11:12:13  systemd[1]: Failed to start SAP Instance SAPXXX_00.


Read more...

Environment

  • SAP system running on Linux Server
  • SAP Start Service is integrated in the systemd management

Keywords

startup , unable to open, lock file, Error 13, Permission denied, /tmp, systemd_msg_handler , KBA , BC-OP-LNX , Linux , 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.