Results 1 to 1 of 1

Thread: migrating app from upstart to systemctl failing with 'dead'

  1. #1
    Join Date
    Feb 2015

    migrating app from upstart to systemctl failing with 'dead'


    new to this area, and trying to setup this project on Ubuntu 20.04.6 LTS

    the project is no longer maintained, but the instructions talk about using upstart to register a daemon. I understand that upstart is deprecated and is replaced by systemctl. I have setup a systemctl file as below based on the current upstart file.


    ExecStart=/usr/bin/perl /usr/local/bin/heatmiser_daemon

    I have saved this to /etc/systemd/system/heatmiser-daemon.service, and am able to register the service and start it. Checking its status shows the following:

    heatmiser-daemon.service - HeatmiserDaemon Loaded: loaded (/etc/systemd/system/heatmiser-daemon.service; enabled; vendor preset: enabled) Active: inactive (dead) since Sun 2023-11-19 15:41:40 UTC; 15s ago Process: 2213 ExecStart=/usr/bin/perl /usr/local/bin/heatmiser_daemon (code=exited, status=0/SUCCESS) Main PID: 2213 (code=exited, status=0/SUCCESS)
    However, upon querying the running services, it is not shown. It is shown when I run systemctl --type=service --state=dead as below:

    heatmiser-daemon.service loaded inactive dead HeatmiserDaemon

    So it seems to me that the service is running and calling the related .pl file, but that is exiting.

    I'm at a point where I'm not sure how to troubleshoot further, so asking for suggestions on if there are any log files etc that can help me to see what the daemon is doing. The app log file doesn't give any help either at this point.

    Any suggestions or pointers welcome.

    Last edited by nmparmar; November 20th, 2023 at 01:51 PM.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts