-
-
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
Subliminal (0.6.0-2) package stops running when set cron time is reached. #133
Comments
I have the same issue. |
Paste logs here please or on Pastebin |
Would live to do that, but what log files? Nothing is being logged by the package other then what I already posted. Can you tell me what I could do to give you the info you need? |
You said "Then tried to use the CLI, but gives back a lot of errors.", Add |
Here it is:
|
That's because you don't have a proper cache directory. Use |
Running the CLI now works. But still having troubles running it with cron in the package. Just got on update, 0.6.1-3, but it doesn't show the serviceselector, even after a fresh install. Strange. What I can I do to give you more info? |
Browser issue, try another one or refresh browser cache. |
Also check the directories paths to see if they exist. |
Fixed anyway, if subliminal exists on error, the error will be put in the logs and the process will continue |
Subliminal (0.6.0-2) package stops running when set cron time is reached. Log files shows:
06/19/2012 09:31:00:DEBUG:root:Task {u'enable': True, u'age': 7, u'hour': 9, u'minute': 31}
06/19/2012 09:31:00:INFO:root:Running scan
Then the Package says "status is stopped".
Also when "Scan" button is pressed within the Synology interface nothing happens. Can't find any logging either.
Is there a way to check if subliminal would even run?
Then tried to use the CLI, but gives back a lot of errors. Maybe due to all the configuration depen's within the package?
Using only SynoCommunity as SPK source and have their latest Python running (2.7.3-2)
Thanks!
The text was updated successfully, but these errors were encountered: