[systemd-devel] Service fails to start with no log messages

[Jeffrey Walton]

I'm trying to determine my service fails to start. I copied the
service to the systemd unit directory, and then enabled and started
the service. Upon reboot the service is not started automatically.

Here are the logs:

$ journalctl -e | grep callboot
Jan 06 20:25:33 raspberrypi systemd[1]: graphical.target: Found
dependency on callboot-ui.service/start
Jan 06 20:25:33 raspberrypi systemd[1]: graphical.target: Job
callboot-ui.service/start deleted to break ordering cycle starting
with graphical.target/start
Jan 06 20:25:39 raspberrypi callboot-trim.sh[332]: Info: Trimming
entries older than 120 days
Jan 06 20:25:58 raspberrypi callboot-trim.sh[332]: Info: Trimmed 21997
old entries
Jan 06 20:25:58 raspberrypi callboot-trim.sh[332]: Info: Vacuuming database
Jan 06 20:26:38 raspberrypi systemd[1]: callboot-trim.service: Succeeded.

Here is the status:

$ systemctl status callboot-monitor.service
● callboot-monitor.service - Callboot service
   Loaded: loaded (/etc/systemd/system/callboot-monitor.service; enabled; vendor
   Active: inactive (dead)

Here is the service:

$ cat /etc/systemd/system/callboot-monitor.service
[Unit]
Description=Callboot service

# This service waits for the UI. It slows down the
# boot so the service starts without failure.
After=graphical.target
Wants=graphical.target
# Service waits for the USB modem
After=usb.target
Wants=usb.target

[Service]
Type=simple
ExecStart=/opt/callboot/bin/callboot.exe

[Install]
WantedBy=multi-user.target