-
-
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
NZBGet 20240115-30 can neither start nor repair #6020
Comments
@Safihre, @hgy59, I've reported the above on behalf of a Discord user. Any thoughts on what may be causing this? I was looking at a seemingly similar #5979 (comment) but I'm not sure what was the root cause. EDIT: I was not able to replicate this on my own system (DS916+ running DSM 7.1.1-42962 Update 4). My install log file looks fairly generic. Install log
|
Can he try to install the Testing version? They might have fixed something upstream already. |
I have the exact same issue here on my DS420+. After the upgrade NZBGet won't start, even after repair. EDIT: Installing latest beta doesn't change the situation. Full uninstall and reinstall made it work again until I configured RSS feeds. |
nzbget works fine after a fresh install until you try to make changes in the config file. After that it started failing. |
This looks like a problem with the old config and/or feeds config with nzbget linux version. We have tested our package specifically on DS420+ and were unable to reproduce the problem. In our tracker there is a similar problem (nzbgetcom/nzbget#168), which we also could not reproduce. It would be very helpful for us to provide nzbget.conf (without sensitive information - logins/passwords) from @mreid-tt and @muldereric to reproduce problem and fix it. |
Is this a new Bug?
Package Name
NZBGet
Package Version
20240115-30
Device Model
DS1513+
Device Architecture
x86_64
Firmware Version
DSM 7.1.1-42962 Update 6
What happened?
Previously ran version 20220406-29 which was running slow with 1700 orders in the queue. Upgraded to the current version and the package would not start or repair. (Reported on behalf of Discord user @mart_in_08382)
Reproduction steps
Install Log
Older Install Log
Upgrade Logs
Downgrade Log
Service Log
No response
Other Logs
No response
The text was updated successfully, but these errors were encountered: