Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Daemon hangs on apscheduler error
See original GitHub issueDaemon 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.
Issue Analytics
- State:
- Created 8 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
python - APScheduler not starting? - Stack Overflow
The correct solution would be to tell the scheduler to not run as a daemon: sched = Scheduler() sched.daemonic = False.
Read more >User guide — APScheduler 3.9.1 documentation
If you schedule jobs in a persistent job store during your application's initialization, you MUST define an explicit ID for the job and...
Read more >How to debug APScheduler when callback functions don't run
I've got a couple of mysterious issues with APScheduler 2.1.0. I've created an application running as a daemon that reads jobs from a...
Read more >APScheduler - PyPI
Please note, however, that APScheduler is not a daemon or service itself, nor does it come with any command line tools. It is...
Read more >APScheduler - Python Package Health Analysis - Snyk
While scanning the latest version of APScheduler, we found that a security review is needed. A total of 1 vulnerabilities or license issues...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
+1
Any update solution for this problem.
Error submitting job "* (trigger: interval[0:20:00], next run at: 2021-03-03 02:37:31 UTC)" to executor "default"