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

linux systemd python Python

I'm not sure how to approach I'm deploying to production and I'm attempting to set up Quick question that's been bugging me - I've searched everywhere and can't find a clear answer. I'm trying to run a Python script as a background service using systemd on my Debian 11 server. The service starts successfully, but when the script attempts to write to stdout, I get a 'Broken pipe' behavior. Here's the relevant part of my service file: ```ini [Unit] Description=My Python Script Service [Service] ExecStart=/usr/bin/python3 /path/to/my_script.py StandardOutput=journal StandardError=journal Restart=on-failure [Install] WantedBy=multi-user.target ``` I've checked the permissions on the script and the Python executable, and they seem fine. When I run the script manually from the terminal, it works without any issues. However, when I run it through systemd, I see the following behavior in the logs: ``` Feb 14 12:34:56 myserver systemd[1]: my_script.service: Failed with result 'exit-code'. Feb 14 12:34:56 myserver my_script.py: Broken pipe ``` I've tried adjusting the `StandardOutput` and `StandardError` settings to `null`, but that doesn't change the outcome. Additionally, I've made sure the script has the correct shebang at the top: ```python #!/usr/bin/env python3 ``` I've also added logging to my script to check where it might be failing, and here’s a snippet: ```python import logging logging.basicConfig(level=logging.DEBUG, filename='/var/log/my_script.log') logging.debug('Script started') # ... rest of the script ``` The log file only shows 'Script started' and nothing else gets logged before the broken pipe behavior occurs. Any insights on what might be going wrong or how to debug this further would be greatly appreciated. My development environment is macOS. Is there a better approach? This issue appeared after updating to Python LTS. The project is a microservice built with Python. I'd love to hear your thoughts on this.