👀 Views: 60 💬 Answers: 1 📅 Created: 2025-06-09

linux systemd ubuntu python Python

I'm working with an scenario with a systemd service on Ubuntu 20.04 that fails to start, and the logs indicate `ExecStartPre= Failed with Result 'exit-code'`. The service is intended to run a Python script that initializes a web application. The relevant portion of my service file looks like this: ```ini [Unit] Description=My Web App After=network.target [Service] User=myuser Group=mygroup ExecStartPre=/usr/bin/python3 /path/to/my_script.py --check ExecStart=/usr/bin/python3 /path/to/my_script.py Restart=always [Install] WantedBy=multi-user.target ``` When I check the status of the service using `systemctl status my-web-app.service`, I see the output: ``` ● my-web-app.service - My Web App Loaded: loaded (/etc/systemd/system/my-web-app.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2023-10-01 12:00:00 UTC; 5s ago ``` The logs show this specific behavior message when I run `journalctl -u my-web-app.service`: ``` my_script.py: behavior: Configuration file not found ``` I have verified that the configuration file exists at the expected path. I also ran the command manually using the same user context and it works without issues, returning the expected output. To troubleshoot further, I modified the service file to include `Environment=PYTHONUNBUFFERED=1` to help with any potential buffering issues, but the result remains the same. I suspect it might be related to the environment under which the systemd service is executing, as opposed to my user terminal. I've tried using `ExecStartPre=/bin/bash -c 'ls -l /path/to/config.yaml'` to check permissions, and that works fine, listing the file correctly. Any advice on how to resolve this scenario or what might be happening with the environment variables or permissions would be greatly appreciated! This is for a microservice running on macOS. What am I doing wrong?