-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Sabnzbd won't start after being stuck #6386
Comments
hey @depeter, I'm on a very similar platform (DS916+, DSM 7.2.2-72806 Update 2) but this is a new one for me. Given the strangeness with the application log ( For the repair package function you mentioned, was this the repair button in the Package Center? If so, the installation log should have shown the package being reinstalled (usually) but I don't see any evidence of this in the logs you shared. Alternately, my recommendation would be to uninstall the package and reinstall it. However, as you pointed out you are running DSM 7.1.1-42962 Update 7 which has a known bug as documented in #6337. Until Synology fixes this I don't think there is a reliable way to do this via command line (you can try to explore the conversation in #3403 which may have some insights). Finally, you can try upgrading to DSM 7.2. |
hey @depeter, someone more familiar with the inner workings of sabnzbd will have to validate this but these errors are interesting:
I wonder if this could be some sort of file locking that the app does to manage the partial downloads and decompressed files. If so, another option you could try (assuming you have nothing critical in your queue) is to temporarily move your entire downloads folder (in particular the incomplete sub-folder) to another location and try starting it up again. The theory I have is that if it does scan for locks on startup, the locks may not be present if you move the downloads folder. There may also be files in |
Thanks for the feedback @mreid-tt.
Yes the repair in the package center. I tried many things afterwards too which could explain the logs being filled with other things? I already did the uninstall and reinstall several times using synopkg but to no avail. The same issue keeps happening. I am indeed also experiencing the issue that everything is empty on the package details screen: 6337. I cleaned up the incomplete folder as you suggested. No files there anymore but still no dice after running another repair:
After uninstalling and then installing again through the Package Center the result is unfortunately the same
I'l try updating to DSM 7.2 now |
Ok, so uninstalling through the package center. Thereby deleting all files (so I have to set it up again). Thanks for the suggestion @mreid-tt. Must have been a stuck lock file or a corrupt config file or what have you... I'm just glad it's solved. |
Is this a new Bug?
Package Name
SABnzbd
Package Version
4.4.1-72
Device Model
DS916+
Device Architecture
x86_64
Firmware Version
DSM 7.1.1-42962 Update 7
What happened?
I have been downloading quite a lot (1.5TB) yesterday and after a whole day of downloading, sabnzbd suddenly became unresponsive. After restarting the entire NAS I could no longer start sabnzbd.
I then tried to repair the installation but I keep getting "Failed to run the package service".
Also when opening the details of the package, none of the information is filled in except for developer and publisher. Uninstalling from the UI is therefore not possible.
Reproduction steps
Install Log
Service Log
Other Logs
The text was updated successfully, but these errors were encountered: