Open
Description
Problem Description:
The piglet service, when installed using piglet --install on a Raspberry Pi fails to start correctly after a system reboot. However, the service can typically be started manually without issues once the system is fully booted.
Observed Behavior:
When the service fails at boot, systemctl status mackenzie-serres-pigg.piglet.service (or the actual service name) shows the service in a failed state. The journal logs (journalctl -u mackenzie-serres-pigg.piglet.service -b) reveal errors such as piglet attempting to bind network sockets before the network interfaces are fully available:
May 26 08:45:14 pi7 systemd[1]: Started mackenzie-serres-pigg.piglet.service - mackenzie-serres-pigg.piglet.
May 26 08:45:15 pi7 piglet[442]: Config loaded from file: /root/.cargo/bin/.piglet_config.json
May 26 08:45:15 pi7 piglet[442]: Error: Socket cannot bind to ipv4 or ipv6
May 26 08:45:15 pi7 systemd[1]: mackenzie-serres-pigg.piglet.service: Main process exited, code=exited, status=1/FAILURE
May 26 08:45:15 pi7 systemd[1]: mackenzie-serres-pigg.piglet.service: Failed with result 'exit-code'.
May 26 08:45:15 pi7 systemd[1]: mackenzie-serres-pigg.piglet.service: Scheduled restart job, restart counter is at 1.
Suggestion
Adding these lines solved the problem for me.
[Unit]
Description=net.mackenzie-serres.pigg.piglet
After=network-online.target pigpiod.service
Wants=network-online.target pigpiod.serviceMetadata
Metadata
Assignees
Labels
No labels