-
-
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
No Such File or directory - when trying to start SAB #2744
Comments
Thanks for your info, I'll take a further look into this tomorrow for you and, once fixed, will republish with build 2.0.0-25 |
Excellent. Thank you for the time and review. If you need any additional
details please let me know.
I attempted a reinstall from scratch and had the same issue. Just an FYI.
Thanks once again for all the support and excellent work on the project.
…On Apr 18, 2017 5:17 PM, "Stuart Foulds-Duncan" ***@***.***> wrote:
Thanks for your info, I'll take a further look into this tomorrow for you
and, once fixed, will republish with build 2.0.0-25
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2744 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Aac3Y-J5IW9XLmI3Uw60CkSyla8ffzhJks5rxTZhgaJpZM4NApR2>
.
|
Currently testing
|
I've looked into this further and it is, unfortunately, all down to #2216 Take a look in that thread for workarounds (I use one of them, and have an "apps" user that I run all my apps as - involves editing start-stop-status scripts every time I upgrade and chown'ing to apps:users) as a short-ish term fix. We are working on a full solution and we do have a DSM6 branch - we hope to have a full solution soon. |
After further searching i found this link to a ticket here: I am on 6.1-15047 Update 2. Thanks |
Setup
_Package Name: SABNZB 2.0.0.24
_Package Version: 2.0.0-24
_NAS Model: 1812+
_DSM version: DSM 6.1-15047 Update 2
Expected behavior
Clicking 'Run' for the SAB package would start the application and leave it in a running state - accessible through a web gui on the configured port etc.
Actual behavior
When trying to start the SAB application from the package area of DSM i get the following error message:
'Failed to run the package Service'
When i log into the NAS via the CLI with my administer account and sudo to root, and run the following command i get the following:
ash-4.3# ./start-stop-status start
Starting SABnzbd ...
env: /usr/local/sabnzbd/env/bin/python: No such file or directory
I have read else where that the issue is because of a missing 'env' directory in the '/var/packages/sabnzbd' directory ... I have no such 'env' directory in that location.
I recently (today) updated the package to the version listed above (this was before i noticed the lack of downloads). So i can't say the new update fixed OR caused the initial issue. According to the logs for SAB, the app has been running and accepting API calls up to this morning when i performed the latest update... so the latest update seems to be the reason for this issue...as API calls couldn't be accepted if the web service was down/unavailable like it is now. So it seems when SAB was updated then attempted to be restarted, it failed to restart correctly due to the above errror.
If you guys could help me troubleshoot this that would be excellent - reviewing forums online i cannot find anything all that similar ... and workarounds for the 'env' directory (such as copying from another directory like sickbeard of headphones etc) doesn't work for me because I do not have that directory anywhere in those package directories (again, this may not be a valid fix, but just trying to say i've tried to see other solutions elsewhere!).
If i can supply you with any pertinent data please let me know. Thanks in advance.
** Update
ash-4.3# ./start-stop-status start
Starting SABnzbd ...
The Python module Cheetah is required
I would rather not go too far down the rabbit hole - so I will just stop here for now. Thanks again
The text was updated successfully, but these errors were encountered: