Flexget: Daemon hangs on apscheduler error
Daemon appears to sometimes hang on apscheduler error:
2016-02-01 13:03 WARNING apscheduler.scheduler Execution of job "scan* (trigger: interval[0:05:00], next run at: 2016-02-01 13:03:50 IST)" skipped: maximum number of running instances reached (1)
Even weirder, when running daemon in the foreground and hitting any key on that error, daemon operation seems to pick up again.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 17 (8 by maintainers)
+1