Replies: 4 comments 2 replies
-
Use
|
Beta Was this translation helpful? Give feedback.
-
Thanks, so much for using AI to help me troubleshoot and structure my ask. So how does one work around this issue? I've spent way too much time trying to figure it out. Thanks for the fast reply.
|
Beta Was this translation helpful? Give feedback.
-
@tamarw I'm sorry I dont appreciate being offended by being called "AI", I spent my own time, for free, for you, to help you, so you can use software that is free for you to use, that was written by me when I should have been spending time with my family
"
Since you didnt attach your systemd setup config files i cannot help you, this from something you are doing custom, we do not yet have an official systemd recipe |
Beta Was this translation helpful? Give feedback.
-
Sorry you thought I was referring to YOU as AI. I wouldn't call a creator of excellent software AI. But to save you the trouble, that's where I started my troubleshooting. I've spent probably two days over maybe 18 hours to guide me here. After what can probably be more than 400 pages printed out across ChatGPT and Gemini, I have not gotten an answer. Are you seeing anything here that might trigger it?
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Environment:
Bug Description:
When attempting to run changedetection.io as a systemd service with the --user-data-dir argument specified in ExecStart (to provide unique browser profiles using systemd's %t), the main changedetection.py process exits immediately after starting. Systemd logs show the process exiting with code=exited, status=2/INVALIDARGUMENT. This prevents the service from starting successfully and makes the web UI (port 5000) inaccessible.
This occurs even when the specified --user-data-dir path points to a valid location (e.g., /path/to/userhome/app/data/profile-%t) where the user has write permissions, and even if the target profile directory is freshly created and empty.
Steps to Reproduce:
Logs & Evidence:
Bash
Non-existent backend.py: The backend.py script referred to in the erroneous output does not exist in the repository structure.
Consequence of Workaround: If --user-data-dir is removed from ExecStart, the service does start and port 5000 is accessible. However, this leads back to the expected browser profile locking errors during concurrent checks:
Expected Behavior:
The changedetection.py script should start successfully via systemd when the --user-data-dir argument is provided, bind to the specified host/port (e.g., 5000), and remain running to serve the web UI and perform checks using unique browser profiles based on the %t specifier. The --help argument should also function correctly.
Relevant Systemd Configuration Snippet:
Ini, TOML
Beta Was this translation helpful? Give feedback.
All reactions