-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update fails when trying to stop Ombi #25
Comments
What happens when you (as root) run |
Same, it says |
That sounds more like a systemd problem than a script problem. Should systemctl ever be returning |
Per https://bugzilla.redhat.com/show_bug.cgi?id=1264727, this may be caused by not rebooting after a systemd upgrade. |
@didyouexpectthat Can you also tell me the output of |
Hi,
I believe this happened after I tried to decommission this server. I used
And the upgrade was okay.
So this is still systemd weirdness. the |
Has this problem recurred since then? |
No, I haven't seen this one come back. I'll close this now. |
First Checks:
Replace the check box for each line with a ☑ or 'x' after confirming.
x I am running the most recent version of the script.
x I have followed the setup instructions correctly.
x I have set the appropriate file permissions and modes.
x I am running the script as the correct user.
Update Script Version
1.1.02
Ombi Version:
3.0.2973
Operating System:
Linux 4.9.0-0.bpo.5-amd64 #1 SMP Debian 4.9.65-3+deb9u2~bpo8+1 (2017-01-05) x86_64 GNU/Linux
Custom Configuration: (
update_ombi.conf
)Update Script Applicable Logs: (
/var/log/ombiupdater.log
by default)Problem Description:
When running update_ombi, it goes to shut down Ombi via systemd then says an unknown error and bailing.
Initial Troubleshooting:
Not sure why systemd returning unknown here.
Reproduction Steps:
Simply run update_ombi with Ombi started.
Additional Detail:
systemd version 215-17+deb8u7
The text was updated successfully, but these errors were encountered: