Kotori development with systemd


Run as service

You should go to the Setup on Debian packages.

When still having the desire to run the application as system service while being in development mode, read on.

We actively use this scenario for integration scenarios and debugging.

general

Let’s add a user to the system and proceed as non-root:

useradd --create-home --shell /bin/bash kotori
su - kotori

systemd service

  1. The systemd startup script expects the kotori executable to be at /usr/local/sbin/kotori and its configuration file at /etc/kotori/kotori.ini:

    mkdir -p /etc/kotori
    chown kotori:kotori /etc/kotori
    ln -s /home/kotori/develop/kotori/.venv2/bin/kotori /usr/local/sbin/kotori
    ln -s /home/kotori/develop/kotori/etc/hiveeyes.ini /etc/kotori/kotori.ini
    
  2. Create the log directory:

    mkdir /var/log/kotori
    chown kotori:kotori /var/log/kotori
    
  3. Copy the systemd script kotori.service into the system:

    cp /home/kotori/develop/kotori/packaging/systemd/kotori.service /usr/lib/systemd/system/
    

    Amend /usr/lib/systemd/system/kotori.service and adapt path to executable to /usr/local/sbin/kotori in ExecStart

Attention

Symlinking does not always work! See also:

systemctl enable fails for symlinks in /etc/systemd/system
  1. Add yet another file /etc/default/kotori:

    KOTORI_OPTS="--debug"
    
  2. Profit:

    systemctl enable kotori
    systemctl start kotori
    
  3. Check:

    root@elbanco:~# systemctl status kotori
    ● kotori.service - Kotori data acquisition and graphing toolkit
       Loaded: loaded (/usr/lib/systemd/system/kotori.service; enabled)
       Active: active (running) since Wed 2016-01-27 03:47:05 CET; 1h 4min ago
         Docs: https://getkotori.org/docs/
     Main PID: 345 (sh)
       CGroup: /system.slice/kotori.service
               ├─345 /bin/sh -c /usr/local/sbin/kotori --config /etc/kotori/kotori.ini --debug >>/var/log/kotori/kotori.log 2>>/var/log/kotor...
               └─355 /home/kotori/develop/kotori-daq/.venv2/bin/python /usr/local/sbin/kotori --config /etc/kotori/kotori.ini --debug
    
    Jan 27 03:47:05 elbanco systemd[1]: Started Kotori data acquisition and graphing toolkit.
    
  4. Watch:

    tail -F /var/log/kotori/kotori.log
    
    2016-01-27T03:17:57+0100 [kotori                            ] INFO: Kotori version 0.5.1
    2016-01-27T03:17:57+0100 [kotori.vendor.hiveeyes.application] INFO: Starting HiveeyesApplication
    2016-01-27T03:17:57+0100 [kotori.daq.graphing.grafana       ] INFO: Starting GrafanaManager "HiveeyesGrafanaManager". grafana=localhost:3000
    2016-01-27T03:17:57+0100 [kotori.daq.intercom.mqtt_adapter  ] INFO: Starting MQTTAdapter. broker=localhost:1883
    2016-01-27T03:17:57+0100 [mqtt.client.factory               ] INFO: MQTT Client library version 0.1.2
    2016-01-27T03:17:57+0100 [mqtt.client.factory.MQTTFactory   ] INFO: Starting factory <mqtt.client.factory.MQTTFactory instance at 0x7f745c54aa28>
    2016-01-27T03:17:57+0100 [mqtt.client.base                  ] DEBUG: ==> CONNECT (id=kotori.mqtt keepalive=0 clean=True)
    2016-01-27T03:17:57+0100 [mqtt.client.base                  ] DEBUG: <== CONNACK (code=0 session=False)
    

systemd troubleshooting

systemctl enable /opt/kotori/kotori.service

systemctl is-enabled kotori
enabled

systemctl is-active kotori
inactive
systemctl status kotori

● kotori.service - Kotori is a multi-channel, multi-protocol data acquisition and graphing toolkit
   Loaded: loaded (/opt/kotori/kotori.service; enabled)
   Active: inactive (dead)
     Docs: https://getkotori.org/docs/
systemctl list-unit-files kotori*

UNIT FILE      STATE
kotori.service enabled
systemctl is-active kotori
unknown
systemctl is-active kotori
active
root@elbanco:~# tail -F /var/log/syslog /var/log/kotori/kotori.log
==> /var/log/syslog <==
Jan 27 03:17:56 elbanco systemd[1]: Starting Kotori is a multi-channel, multi-protocol data acquisition and graphing toolkit...
Jan 27 03:17:56 elbanco systemd[1]: Started Kotori is a multi-channel, multi-protocol data acquisition and graphing toolkit.


==> /var/log/kotori/kotori.log <==

2016-01-27T03:17:57+0100 [kotori                           ] INFO: Kotori version 0.5.1
2016-01-27T03:17:57+0100 [kotori                           ] INFO: options: {'--config': '/etc/kotori/kotori.ini', '--debug': True, '--help': False, '--version': False}
2016-01-27T03:17:57+0100 [kotori                           ] INFO: debug: True
2016-01-27T03:17:57+0100 [kotori.vendor.hiveeyes.application] INFO: Starting HiveeyesApplication
2016-01-27T03:17:57+0100 [kotori.daq.graphing.grafana      ] INFO: Starting GrafanaManager "HiveeyesGrafanaManager". grafana=localhost:3000
2016-01-27T03:17:57+0100 [kotori.daq.intercom.mqtt_adapter ] INFO: Starting MQTTAdapter. broker=localhost:1883
2016-01-27T03:17:57+0100 [mqtt.client.factory              ] INFO: MQTT Client library version 0.1.2
2016-01-27T03:17:57+0100 [mqtt.client.factory.MQTTFactory  ] INFO: Starting factory <mqtt.client.factory.MQTTFactory instance at 0x7f745c54aa28>
2016-01-27T03:17:57+0100 [mqtt.client.base                 ] DEBUG: ==> CONNECT (id=kotori.mqtt keepalive=0 clean=True)
2016-01-27T03:17:57+0100 [mqtt.client.base                 ] DEBUG: <== CONNACK (code=0 session=False)
service --status-all | grep kotori

systemctl list-units --all kotori*
systemctl status influxdb mosquitto grafana-server kotori
systemctl list-unit-files kotori* influx* grafana* mosquitto*
[    4.043574] systemd[1]: Cannot add dependency job for unit kotori.service, ignoring: Unit kotori.service failed to load: No such file or directory.