-
-
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
Python won't run on Synology #376
Comments
Edit |
Thanks - I'll give it a try. I currently have Synology's Python package installed, and it's in use by a backup job, so I'll have to wait until it's finished. Will post back if I still have problems. |
I had the same issue with the 4.2 beta and this change fixed the problem. Thanks! |
Confirmed that this solved the issue for me too! |
Worked here too |
Had the same problem on DS213+ DSM 4.2-3160 BETA |
Can someone report this to Synology? |
@Diaoul Maybe you've already noticed, but Synology is actually using the same approach in their own non-startable packages, e.g. the new Java and Perl packages, so it seems to be correct.
|
Yes, but our Python SPK doesn't "run" that's nonsense. |
Perl doesn't either...I been looking around a bit to see what the idea was, seems exit 0 is succes based on file existance and/or running service (not all packages have been updated, I guess). 0 happens to show as 'Running' in the package center. Exit 1 is 'Stopped' (and blocks dependant packages as a result), exit 150 is 'Broken'. Entered a request ID: #1142, let's see. |
YES is works!!! (exit 0) now i can installl SasNZB and sickbeard!! thanks a million! |
hi. I am having the same issue. Noob Q. I telnet into synology box. I use vi to edit the file. I think I am in read only mode for the file as I make changes and I am unable to save. How can I change properties on file from read only to write? I logged in as admin. Thanks |
You have to be logged in as Root (same pass as admin). In vinyou have to save the file using :wq after this check the file again. |
Diehrdmking- Thanks for your reply, that did the job. Much appreciated. |
Received a response to my request: So that's good. I did some suggestions when I put in the request, but no details on on what kind of fix is being developed: I'll be interested to see it. |
Hi, Noob question. How do I do these steps to get sabnzbd working on my NAS? I've tried to find the way, but I simple don't find the package to be able to edit. I have installed the Python from synocommunity. Thank you! |
Hello, What you also can try is work with a lower version of sasnzb bij using http://synopkg.superzebulon.org/spkrepo/packages |
thanks for your reply dieharddmking, but these older versions of sabnzbd will run on my NAS? because i forgot to tell that I have installed the last beta version of DSM (4.2-3160). Can you point me some webpage that I can read to understand how to do this kind of things? thank you! |
Sorry for the Noob question, but how do I |
log into your NAS using ssh and something like "putty" (google it) |
ok so logged into NAS via Putty, as user "root" edit the file, changes stop 1 to "stop 0", but now don't know how to save and exit the file ??? I press :wq and that's what is typed on the screen . sorry I've never edited files in Putty. Where must the cursor be to type ":wq" ? help |
You need to press "ESC" to get out of editing mode |
If you are not familiar with Putty (I'm not!), I suggest you install the programme WinSCP (google it) instead. This gives you an explorer view of the file structure on the NAS and you can right-click on files to edit them in your favourite text-editor (I use Notepad++). Once you have edited the file, you just save the changes, and WinSCP will automatically transfer the edited file to the NAS. |
@Omerton: "You need to press to get out of editing mode". Press ? It took me a while to figure out that I needed to press "Escape" to get out of Insert Mode. I noticed the "I" in the last row changed once I pressed "ESC" the ":wq" and "enter". Sorry this was the first time I'd used Putty. @Pokersut - next time I'll use WinSCP Saved the file went back and to my Python package and its running. ALL GOOD - THANKS GUYS |
@fixmynas Sorry, seems the < and > were replaced. Press the Escape key |
Hi |
DS712+ with DSM 4.2-3161. This still isn't working for me.
The error seems to persist. I noticed after editing in "vi", and doing the whole ":wq" step, it says "file is read only". but the file still seems to be changed? Anyone got any ideas? |
Thanks Dr-Bean, I saw that one too, that's how I was lead here. But I was under the impression that performing this fix would not require the other script to be stopped (for whatever it's used for, I'm not sure... that's why I wanted to leave it alone). I'll try that now, and report back. UPDATE: Ok.. So why can't I write to these files? I'm using the administrator account (system default user) for the editing in VIM and it's saying "read only"... is there something I'm missing? I am using OSX Terminal to complete these tasks. UPDATE 2: Nnnnnnevermind! I used root/admin to telnet into the box instead of my System default user- which I had thought I did the first time around. But I must have used root/admin that time as well (did it a week ago, was still having this issue)... Thanks! UPDATE 3: wooooooooo! it worked. should have done that one earlier. Thanks Dr-Bean. 👍 💯 |
Hi, I have the same problem with the released version of DSM 4.2. Thank you for advice! |
Thanks, this worked! |
@bjbe70 Are you sure you only changed line 19? |
Will fix this today as DSM 4.2 final didn't solve it... |
I also have DSM 4.2-3202. |
I edited the "/var/packages/python/scripts/start-stop-status" with WinSCP-Editor and saved it with it remote. Is that a problem? Or do i need to use the vi? |
That sounds good, Diaoul! Thank you for your support! |
I used WinSCP to edit mine, and it worked fine. I did uninstall/reinstall all the packages, though, but I'm not sure that was necessary - but it worked! |
Pokersut, you uninstalled all the packages manually after update to DMS 4.2-3202? |
When I updated to 3202, all the packages remained, but SabNZB wouldn't Anyway, I reinstalled the Python package, edited the start-stop file bjbe70 skrev den 2013-03-06 13:40:
|
Hi, Reason: I used the internal editor of WinSCP instead of an external. The internal editor converted all "LF" to "LF+CR" ... |
That's fixed with 7cc7015 |
Sorry to raise this again, I am hoping someone can help as I have got pretty far using the insutrctions above but I am struggling myself with the error when trying to install Sickbeard, Couch Potato Server and SABnzbd on a Synology DS212J running DSM 4.2-3202 When I try and install any of them I get the following error
Obviously it's already installed and I've used the Synology package version 2.7.3-011 . So using the instructions here I have installed WinSCP, Enabled the SFTP service, switched on SSH in my NAS and then navigated through to
but when I get there my file looks different in notepad to everyone elses, I have an else statement of somekind and despite changing the second exit option within status to 0 it still doesn't fix the problem. Any ideas from anyone?
|
Use SynoCommunity's Python SPK, not Synology's. |
Wow, that simple huh!? Works fine now, thanks Diaoul 👍 |
Hey guys, somehow i don't seem to be able to make it. what am I doing wrong?? any suggestions? |
hey guys, Ik have succesfully installed python in my synology nas but i can't find how to add libraries for python. can anyone help me? |
@cognopatrick: Use virtualenv to create yourself an isolated environment to work with. On your NAS, virtualenv is located at |
On my DS-413 with DSM 4.2-3160, I cannot run the Python package from SynoCommunity.
It seems to install successfully, but when I try to install other packages that require Python (e.g. Sickbeard), I get the message "Please run Python before installing this package".
Since there is no "Run" command for the Python package, I don't know what to do. I have tried installing Synology's own Python package (v. 2.7.3-011), and it installs and runs without problems - but Sickbeard will not install under with version.
I had the same problem last time I upgraded the firmware, but then I could fix the problem by uninstalling, rebooting and re-installing Python - but this hasn't worked this time.
Any ideas?
The text was updated successfully, but these errors were encountered: