Ombi
Ombi copied to clipboard
Ombi-app
service problem after every update
Describe the bug I run ombi in port 5002, my ombi.service have the option --host http://*:5002 every update remove this option from my service and i must go to edit manually everytime.. can you leave original ombi.service on update?
To Reproduce insert option --host http://*:5002 in Exec= in ombi.service and run sudo apt upgrade (if availble)
Expected behavior ombi.service leave untouch
Screenshots If applicable, add screenshots to help explain your problem.
Logs (Logs directory where Ombi is located) If applicable, a snippet of the logs that seems relevant to the bug if present.
Desktop (please complete the following information):
- OS: [e.g. iOS]
Ombi Version (please complete the following information):
- Version [e.g. 4.0.958]
- Media Server [e.g. Plex]
- Database Type: SQLite (Please change if using MySQL)
Additional context thanx
Hi!
Thanks for the issue report. Before a real human comes by, please make sure you used our bug report format.
Have you looked at the wiki yet? https://docs.ombi.app/
Before posting make sure you also read our FAQ.
Make the title describe your issue. Having 'not working' or 'I get this bug' for 100 issues, isn't really helpful.
If we need more information or there is some progress we tag the issue or update the tag and keep you updated.
Thanks!
Ombi Bot.
Describe the bug I run ombi in port 5002, my ombi.service have the option --host http://*:5002 every update remove this option from my service and i must go to edit manually everytime.. can you leave original ombi.service on update?
To Reproduce insert option --host http://*:5002 in Exec= in ombi.service and run sudo apt upgrade (if availble)
Expected behavior ombi.service leave untouch
Screenshots If applicable, add screenshots to help explain your problem.
Logs (Logs directory where Ombi is located) If applicable, a snippet of the logs that seems relevant to the bug if present.
Desktop (please complete the following information):
- OS: [e.g. iOS]
Ombi Version (please complete the following information):
- Version [e.g. 4.0.958]
- Media Server [e.g. Plex]
- Database Type: SQLite (Please change if using MySQL)
Additional context thanx
I'm getting the same problem when updating Ombi on Linux (ARM64) using the "developer" Azure Pipeline package. I followed all of the instructions on the official documentation, which looks straight forward, but after replacing all files on /opt/Ombi/ with the new ones, the Ombi systemd service fails to start, and looking at the service status, it fails on the following line: ExecStart=/opt/Ombi/Ombi --storage /etc/Ombi/ (code=exited, status=203/EXEC)
The problem is I have no idea how the service side works. If it's failing to start I can help, I just need the stdout from ombi
Sorry for the delayed response, these are the all of the logs that I was able to find from the ombi.service:
May 20 08:10:22 localhost systemd[1]: Started Ombi - PMS Requests System. May 20 08:10:22 localhost systemd[246812]: ombi.service: Failed to execute command: Exec format error May 20 08:10:22 localhost systemd[246812]: ombi.service: Failed at step EXEC spawning /opt/Ombi/Ombi: Exec format error May 20 08:10:22 localhost systemd[1]: ombi.service: Main process exited, code=exited, status=203/EXEC May 20 08:10:22 localhost systemd[1]: ombi.service: Failed with result 'exit-code'. May 20 08:10:27 localhost systemd[1]: ombi.service: Scheduled restart job, restart counter is at 26. May 20 08:10:27 localhost systemd[1]: Stopped Ombi - PMS Requests System. May 20 08:10:27 localhost systemd[1]: Started Ombi - PMS Requests System. May 20 08:10:27 localhost systemd[246816]: ombi.service: Failed to execute command: Exec format error May 20 08:10:27 localhost systemd[246816]: ombi.service: Failed at step EXEC spawning /opt/Ombi/Ombi: Exec format error May 20 08:10:27 localhost systemd[1]: ombi.service: Main process exited, code=exited, status=203/EXEC May 20 08:10:27 localhost systemd[1]: ombi.service: Failed with result 'exit-code'. May 20 08:10:33 localhost systemd[1]: ombi.service: Scheduled restart job, restart counter is at 27. May 20 08:10:33 localhost systemd[1]: Stopped Ombi - PMS Requests System. May 20 08:10:33 localhost systemd[1]: Started Ombi - PMS Requests System. May 20 08:10:33 localhost systemd[246818]: ombi.service: Failed to execute command: Exec format error May 20 08:10:33 localhost systemd[246818]: ombi.service: Failed at step EXEC spawning /opt/Ombi/Ombi: Exec format error May 20 08:10:33 localhost systemd[1]: ombi.service: Main process exited, code=exited, status=203/EXEC May 20 08:10:33 localhost systemd[1]: ombi.service: Failed with result 'exit-code'. May 20 08:10:38 localhost systemd[1]: ombi.service: Scheduled restart job, restart counter is at 28. May 20 08:10:38 localhost systemd[1]: Stopped Ombi - PMS Requests System. May 20 08:10:38 localhost systemd[1]: Started Ombi - PMS Requests System. May 20 08:10:38 localhost systemd[246821]: ombi.service: Failed to execute command: Exec format error May 20 08:10:38 localhost systemd[246821]: ombi.service: Failed at step EXEC spawning /opt/Ombi/Ombi: Exec format error May 20 08:10:38 localhost systemd[1]: ombi.service: Main process exited, code=exited, status=203/EXEC
If obmi is executed manually it outputs the same error:
bash: /opt/Ombi/Ombi: cannot execute binary file: Exec format error
Can you post the output of starting ombi manually with passing the same parameters as your service is?
The 2 lines in the end of my last reply contain the output of ombi when stating manually with the same parameters as the service.
This this the command with the same parameters as the service:
$ /opt/Ombi/Ombi --storage /etc/Ombi/bash: /opt/Ombi/Ombi: cannot execute binary file: Exec format error
@tidusjar I think the problem here lies in the apt-get / apt-upgrade. Since we define in the apt package how the service should be executed (calling the program Ombi), it will overwrite any custom inserted code when the app gets updated to the default call to Ombi.
@twanariens @tidusjar What is happening, at least on the Debian, side, is that the systemd service file is getting overwritten for each update. Instead of overwriting the file, you should either prompt about it, or at the very least make a backup of the old file before overwriting it. If you want help with this, let me know ill fork and fix it. Would help if you tell me where the code is tho, so I don't gotta go digging.
That is to say, general when you build deb packages etc, there is a 'control' file that is what handles alot of what happens when you install a Deb package. In any case, I have a lot of experience building and automation of debian and redhat packages, as well as with creating update and delivery pipelines(I am literally a Build and Release Engineer). So I would be happy to help, but I will want someone who know how YOU have been doing it, to show me what you have so far, and then I will work on fixing it up all fancy for you.
Ok, I looked at this, and how systemd works a bit closer. It seems you guys aren't actually doing anything wrong. BUT, I added a disclaimer/comment in the service file explaining the proper way that users should be overriding it. I also added a small change to use an Environment file(/etc/default/ombi.conf) to allow users to set startup options there as well. The Gist of it is: Don't edit the /lib/systemd/system/ombi.service file. Instead, copy that service file to /etc/systemd/system/ombi.service and edit it there. Or you can always make a new file in /etc/systemd/system/ombi.service.d/local.conf and simply override the parts you want to change, and the rest will be defaulted to whats in the 'global' service file.