-
-
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 error after update to DSM 4.2 beta #373
Comments
Where do you get this error? I don't see anything related to SABnzbd or Python in this path. |
I get it in SABnzbd as a warning, Screenshot: https://www.dropbox.com/s/yjmvuej72ooq6df/saberror.jpg |
Could you report this to Synology? It seems it's due to their Synology High Availability library |
Seeing the same issue, same error message after updating to 4.2. I was able to fix/workaround the problem by editing
Was tipped in the right direction by this. I will also be reporting this as a bug to Synology, hopefully they will know the actual problem and have a remedy for the 4.2 release. |
I reported it also as a bug to Synology. |
Synology send me this: We are aware of this issue, and we are currently working on a fix for it. We assure this issue will be fixed by the time the final version of the firmware is released. |
@peelman Thanks for the pointer. Worked for me too |
@peelman I have verified that the temporary fix works on my DiskStation 412+ with DSM 4.2 Beta... Thanks for the info! |
@peelman confirmed working (also on DS412+ on 4.2BETA) |
fix worked for me! woooooooo, thanx 👍 remember to use your root user and password to save changes in VIM, system default user account doesn't work. |
Working on DS411+II. Please await a fix from Synology before closing this issue. |
Fixed with 7cc7015 |
I receive the following error:
ERROR: ld.so: object '/usr/syno/synoha/lib/libsynoha.so.4' from /etc/ld.so.preload cannot be preloaded: ignored.
Downloading is no problem, but unpacking is. Every download I tried says it failed while trying to unpack.
There is however an outputfile...so it seems it does unpack.
The text was updated successfully, but these errors were encountered: