👀 Views: 74 💬 Answers: 1 📅 Created: 2025-06-07

linux systemd debian services Python

I've hit a wall trying to I'm having trouble with a custom Systemd service on my Debian 11 server. I created a service file located at `/etc/systemd/system/my_custom_service.service` with the following content: ```ini [Unit] Description=My Custom Service After=network.target [Service] Type=simple ExecStart=/usr/bin/python3 /path/to/my_script.py Restart=on-failure [Install] WantedBy=multi-user.target ``` After creating the service, I ran `systemctl daemon-reload`, followed by `systemctl enable my_custom_service.service` to ensure it starts at boot. However, when I reboot the server, the service doesn’t start and I see the following behavior in the logs: ```bash systemctl status my_custom_service.service ● my_custom_service.service - My Custom Service Loaded: loaded (/etc/systemd/system/my_custom_service.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2023-10-15 12:34:56 UTC; 5s ago Process: 12345 ExecStart=/usr/bin/python3 /path/to/my_script.py (code=exited, status=1/FAILURE) ``` When I check the logs using `journalctl -u my_custom_service.service`, I see: ```bash Oct 15 12:34:56 myhostname my_script.py: behavior: Unable to connect to database ``` I’ve checked that the database server is running and accessible. I also verified the script runs fine when manually executed using `python3 /path/to/my_script.py`. I'm not sure why it need to connect to the database when started through Systemd. I even tried adding `Environment=DATABASE_URL=mysql://user:password@localhost/dbname` in the service file but that didn’t resolve the scenario. Any insights on why this might be happening or how to troubleshoot further? My development environment is Windows. How would you solve this? I'm working with Python in a Docker container on Linux. What's the best practice here? I'm coming from a different tech stack and learning Python. Thanks for any help you can provide!