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

linux systemd python Python

Hey everyone, I'm running into an issue that's driving me crazy. I've been struggling with this for a few days now and could really use some help... I'm working with an scenario with my custom Python application that runs fine when executed manually but fails when started as a Systemd service. The behavior message I receive is `ModuleNotFoundError: No module named 'my_module'`. I have checked that the module is installed in the correct Python environment, which is Python 3.9, and it works when I run it directly from the terminal using the same user account. My Systemd service file located at `/etc/systemd/system/myapp.service` looks like this: ```ini [Unit] Description=My Custom Python App After=network.target [Service] User=myuser Group=mygroup WorkingDirectory=/home/myuser/myapp Environment="PATH=/home/myuser/myapp/venv/bin" ExecStart=/home/myuser/myapp/venv/bin/python /home/myuser/myapp/main.py [Install] WantedBy=multi-user.target ``` I have ensured that the virtual environment is activated properly by checking the `PATH`, and I can confirm that the `my_module` exists in the virtual environment. However, when I try to start the service using `sudo systemctl start myapp`, the logs show the above behavior when I check using `journalctl -xe`. Furthermore, I have tried running this command in the terminal: ```bash sudo -u myuser /home/myuser/myapp/venv/bin/python /home/myuser/myapp/main.py ``` which executes without any issues. I’ve also looked into the permissions and made sure that `myuser` has the necessary access to the files and directories involved. Any suggestions on what might be causing this discrepancy? Could it be related to how Systemd handles environments or paths? This is for a REST API running on Windows 10.