Vagrantfile for digdag servers running with PostgreSQL

June 4, 2017

I made a Vagranfile in order to launch digdag servers with postgresql backend. Digdag is a workflow manager being developed by Treasure Data. You can easily try digdag server with high availabiity.

https://github.com/tmtk75/vagrant-digdag

I got stuck when I implemented a systemd unit file for digdag server. For the first time, I wrote like this.

[Unit]
Description=digdag
...
[Service]
ExecStart=/usr/local/bin/digdag server --config ...

Seeing log by journalctl, I couldn't find any helpful clues. It only said status=203/EXEC.

digdag.service: main process exited, code=exited, status=203/EXEC

Googling with systemd 203/EXEC, I knew I needed to check syslog. I checked /var/log/messages and I found out Exec format error.

Failed at step EXEC spawning /usr/local/bin/digdag: Exec format error

Yes, digdag is not a usual executable file. Systemd detects it and handles as irregular one. So I made a simple wrapper shell script to avoid it.

I've understood we need to check not only log by journalctl but also syslog in troubleshooting of systemd unit file.