sudo cp logos-blockchain-node.service /etc/systemd/system/
sudo nano /etc/systemd/system/logos-blockchain-node.service
# Replace <username> with your actual username
# Adjust paths to binary and config file

Reload systemd and start the service:

sudo systemctl daemon-reload
sudo systemctl start logos-blockchain-node
# Optional: enable auto-start at boot
sudo systemctl enable logos-blockchain-node

Check status and logs:

sudo systemctl status logos-blockchain-node
journalctl -u logos-blockchain-node -f

Raspberry Pi / Volatile Storage

If journald logs are not persisting across reboots (common on Raspberry Pi), uncomment the StandardOutput and StandardError lines in the service file to write logs directly to a file.

When using file-based logging, optionally set up logrotate to prevent disk fill:

sudo cp logrotate-logos-blockchain-node.conf /etc/logrotate.d/logos-blockchain-node
sudo nano /etc/logrotate.d/logos-blockchain-node
# Replace <username> with your actual username

Commands

# Start/stop/restart
sudo systemctl start logos-blockchain-node
sudo systemctl stop logos-blockchain-node
sudo systemctl restart logos-blockchain-node

# View logs (journald)
journalctl -u logos-blockchain-node -f           # follow
journalctl -u logos-blockchain-node --no-pager   # dump all

# Export logs to file
journalctl -u logos-blockchain-node --no-pager > node.log