👀 Views: 67 💬 Answers: 1 📅 Created: 2025-06-08

systemd ubuntu environment-variables Python

Quick question that's been bugging me - I've searched everywhere and can't find a clear answer. I've been working on a Systemd service for a Python application that requires certain environment variables to run correctly. After updating the service file to include new environment variables, I'm finding that the service fails to start with the behavior message: `Failed to start my_app.service: Unit my_app.service not found.` When I check the status with `systemctl status my_app.service`, I see the following output: ``` ● my_app.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) ``` I’ve ensured that the service file is located in `/etc/systemd/system/` and contains the necessary configuration. Here is the content of my service file: ```ini [Unit] Description=My Python Application [Service] Type=simple ExecStart=/usr/bin/python3 /path/to/my_app.py Environment=MY_ENV_VAR=/path/to/resource Environment=ANOTHER_VAR=value [Install] WantedBy=multi-user.target ``` I’ve run `systemctl daemon-reload` several times after modifying the service file, but the question continues. I also checked the permissions of the service file and it seems to be correctly set to `644`. Additionally, I’ve verified that Python is installed and the path to my script is correct. The service does start successfully when run manually using the command line, which leads me to believe that it’s an scenario with how Systemd is interpreting the environment variables. Could this scenario be related to the syntax in the service file, or is there a potential caching scenario with Systemd? Any guidance on how to troubleshoot this further would be appreciated! I'm working on a service that needs to handle this. Has anyone else encountered this? I'm working on a CLI tool that needs to handle this.