SynoCommunity / spksrc

Cross compilation framework to create native packages for the Synology's NAS
https://synocommunity.com
Other
3.03k stars 1.23k forks source link

SabNZBD cannot be started after upgrade #282

Closed lleblanc51 closed 12 years ago

lleblanc51 commented 12 years ago

Hi!

I just upgrade Python Package from Synocommunity and SabNZBD to latest version 0.7.5-2 and Sab don't want to start.

I try to uninstall Python Package and SabNZBD and reinstall with no change...

Python package Version 2.7.3-3 SabNZBD 0.7.5-2

I try this and got a n error message WHS> /var/packages/sabnzbd/scripts/start-stop-status start Starting SABnzbd ... -sh: /usr/local/sabnzbd/env/bin/python: not found WHS>

What's wrong ?

Thanks for your help.

mormerod commented 12 years ago

The SAB install never gets that far...

A1rwav3 commented 12 years ago

This is what I have at the end of the logfile "message", just after a failed install of sabnzbd:

Nov 5 16:53:46 PkgSynoMan.cgi: pkgtool.cpp:2016 Failed to run preinst script for sabnzbd Nov 5 16:53:48 PkgMan.cgi: pkgtool.cpp:2448 No script for python Nov 5 16:54:16 PkgMan.cgi: pkgtool.cpp:2448 No script for python Nov 5 16:54:19 PkgMan.cgi: pkgtool.cpp:2448 No script for python Nov 5 16:54:30 PkgMan.cgi: pkgtool.cpp:2448 No script for python

Is it useful to you?

And by the way, this is not the folder definition problem, the install crashes just after getting 98% downloading. It never shows any dialog box... Just the error message.

upmg commented 12 years ago

I'd like to cross check with my logs but cant find the above logfile "message" in my Synology logging UI. Where exactly is that from A1rwav3 ?

Might be helpful to the devs if other people can confirm or add extra error logs.

A1rwav3 commented 12 years ago

It does not come from the interface directly. I found it via the console in

"/var/log/messages"

daede commented 12 years ago

nzbget won't install too "Failed to install the package"... Everything else seems to be working

upmg commented 12 years ago

My error msg from "messages" in "/var/log/ is as follow immediately after attempting SABnzbd install.

Nov 5 16:44:15 PkgSynoMan.cgi: pkgtool.cpp:2016 Failed to run preinst script for sabnzbd

secavia commented 12 years ago

same message error on DS1511+, with Python installed from new link

Nov 5 16:44:15 PkgSynoMan.cgi: pkgtool.cpp:2016 Failed to run preinst script for sabnzbd

rosenkrieger commented 12 years ago

I a little scared to upgrade to the newest SABnzbd after I had trouble the last time and had to do a fresh install and config.

Is there a way (I am SSH newbie) way to save the config of SABnzbd and simply back it up and put it back later?

codeyy commented 12 years ago

I'm also unable to reinstall SABnzbd (same pkgtool error as above). And when I want to uninstall my Python to revert back to an older version, it says that I should uninstall CouchPotato, Headphones and SickBeard. I don't mind a reinstall of SABnzbd, but reinstalling and configing everything again will cost me a lot of more time...

mormerod commented 12 years ago

Just out of interest, is it not possible to change the packages so they utilize the Synology Python package rather than requiring another version to be installed. Seems a waste to require two versions be installed.

Emmanuel147 commented 12 years ago

Same error on a DS411+II. I have done a uninstal of Python + other packeges before I found this issue. Now I can't get it back in working order. Installed python_x86_2.7.3-2.spk with no problem but SabNZB gives a error "can't install". No question for a download dir in the setup. Is SabNZB updated to? Can't we do a rollback?

codeyy commented 12 years ago

I looked up how to backup the configs of all the linked tools, made those backups, uninstalled everything, reinstalled Python (2.7.3-2), but I still can't get sabnzbd installed.

In /var/log/messages I find : PkgSynoMan.cgi: PkgSynoMan.cpp:893 Failed to mkdir pkglist.tmp, File exists PkgSynoMan.cgi: pkgtool.cpp:2016 Failed to run preinst script for sabnzbd

upmg commented 12 years ago

Looks like we're all in the same boat here and will have to wait for Diaoul to give us an updated SABnzbd package or Python. Hope its soon :)

Diaoul commented 12 years ago

That should be fixed.

Sorry for the inconvenience

mormerod commented 12 years ago

If I removed Python altogether can I now use the version in the Package Center?

Diaoul commented 12 years ago

Yes

secavia commented 12 years ago

on DS1511+ Python 2.7.3-2 installed from package center, Sabnzbd 0.7.5-2 from package center. error : "Echec lors du lancement de la réparation du paquet" :( no log in Python, no log in Sabnzbd

in var log message : Nov 5 22:03:17 PkgMan.cgi: pkgtool.cpp:2597 Failed to start package sabnzbd

:(

mormerod commented 12 years ago

Fixed. Awesome, Thanks

CB4STI3N commented 12 years ago

Fixed for me :

Uninstall all programs using python (after making a backup configurations) Uninstalling python 2.7.3-3 Installing python 2.7.3-2 from the package center Install sabnzbd 0.7.5-2 Install other program using python and finally copy the configuration files for each program.

Everything is ok Thanks Diaoul and others.

secavia commented 12 years ago

on DS1511+ not fixed for me

Uninstall Python, reboot Inslall python 2.7.3.-2 for package center Install sanzbd 0.7.5-2 for package center

Error : Echec lors de la réparation du paquet

Help me please

ytsejam1138 commented 12 years ago

I'm still have a problem running SABnzbd, I have a DS212.

Uninstall Python, reboot Inslall python 2.7.3.-2 for package center Install sanzbd 0.7.5-2 for package center

It still fails to run. Everything else works fine, it's just SABnzbd I have the same download directory I have always had /volume1/video/

I have also noticed that when installing a package I now have to hit install twice. Once to download the SPK and once to actually install the SPK.

metryann commented 12 years ago

Hello,

@secavia and @ytsejam1138 : I had exactly the same problem. I resolved it by deleting manually some remaining SABnzbd folders.

1) Uninstall SABnzbd 2) Search SABnzbd remaining folders : find / -name sabnzbd 3) Delete folders found 4) Try reinstalling SABnzbd

That fixed the problem for me, I could install and run SABnzbd.

However, I also have to click "Install" twice. If anyone knows why, thank you for help.

Thanks

Diaoul commented 12 years ago

Yes, that's a bug in the Package Center. First click actually download the package, second click installs.

ytsejam1138 commented 12 years ago

@mertyann

Thank you so much!! That worked. I needed to delete the folllowing directories:

/usr/local/sabnzbd /usr/local/sabnzbd/sabnzbd /usr/syno/etc/packages/sabnzbd /tmp/@synopackage/sabnzbd

Diaoul commented 12 years ago

FYI, I recompiled Python 2.7.3-3 and I'm uploading to the private beta repository. After a first check, everything seems fine, I think that parallel make must have break something the first time.

bigblackvenom commented 12 years ago

Thanks a bunch metryann and ytsejam1138,

It solved the issue after delete some remaining sabnzbd folders.

DS411 DSM 4.1-2647

secavia commented 12 years ago

Thanks a bunch metryann and ytsejam1138,

It solved the issue after delete some remaining sabnzbd folders.

DS1511+

A1rwav3 commented 12 years ago

Don't be sorry, Thanks a lot for your work!

Diaoul commented 12 years ago

Any issues with the Python in private beta? I'll deploy the it soon

Diaoul commented 12 years ago

You are faster to report issues than to contribute...

ytsejam1138 commented 12 years ago

How can we report on the Python 2.7.3-3 if it's a Private BETA? It doesn't show up in Package Center.

Diaoul commented 12 years ago

Send me an email so I can give you access to the private beta repository. You can find my email here.

ruinit commented 12 years ago

Could someone help me out I am a terrible newb. I tried this listed above to fix my sab install but it gives me and error. rsync -av /volume1/@appstore/sickbeard/env /volume1/@appstore/sabnzbd/ chown -R sabnzbd /volume1/@appstore/sabnzbd/env

ERROR: module is read only rsync error: syntax or usage error (code 1) at main.c(1034) [Receiver=3.0.8] rsync error: rsync service is no running (code 43) at io.c(653) [sender=3.0.8]

I really have no idea how to backup my sab config files to do a reinstall so any help would be great

ytsejam1138 commented 12 years ago

Running Python 2.7.3-3 now in conjunction with SABnzbd, CouchPotato, and SickBeard with no problems

mutovkin commented 11 years ago

The way I fix the issue is that I ssh into the box and edit /var/packages/sabnzbd/scripts/start-stop-status

There I just need to fix python path to be: PYTHON="${PYTHON_DIR}/bin/python"

and now everything works, no need to re-install anything or perform any other reboot, restart, reinstall magic.

Diaoul commented 11 years ago

As I already said, this solution isn't recomended.

alwyatt commented 10 years ago

Hey there, I've got the same issue. I've tried lots of these suggestions above and here: https://github.com/SynoCommunity/spksrc/issues/63, but can't actually use sabnzbd

Sabnzbd: 0.7.18-10 Python: 2.7.8-10 Synology: DS412+ DSM: 5.0-4493 Update 5

I've tried uninstalling both sabnzbd & python, deleting any sabnzb folders, restarting and then reinstalling both and then restarting again before running.

I've been able to run the wizard and NOT enable https, but as soon as I try to launch localhost:8080 , 127.0.0.1:8080 or 192.168.1.100:8080 I get "web page not available"

According to the package center sabnzb is running and if I run "/var/packages/sabnzbd/scripts/start-stop-status start" it returns that sabnzbd is already running.

Can anyone help?

I have read in the log that there is an error about changing permissions in the /volume1/downloads/incomplete folder , but I don't understand how this would stop the package from running

Dr-Bean commented 10 years ago

@alwyatt Can I suggest to open a new issue? Adding on to a two year old closed issue might not be the best approach...

When you open a new issue, add the sabnzbd logs (either via GUI, or via /usr/local/sabnzbd/var/logs). If the logs contain more than, say, 10 lines, upload them to gist.github.com or pastebin, and provide a link in the new issue instead of pasting them directly into the issue.

While you're at it, check if the firewall on the NAS allows port 8080 (or allow all traffic for testing purposes), and in your browser, do http://ip-of-your-NAS:8080. Both localhost and 127.0.0.1 cannot be used, because those link to the device you're working on.

alwyatt commented 10 years ago

@Dr-Bean thanks and posted here https://github.com/SynoCommunity/spksrc/issues/1286