-
Notifications
You must be signed in to change notification settings - Fork 798
Remove the requirement to restart the sceduler after adding a new account. #54
Comments
Thanks! |
Starting work on this today |
Any updates on the status of this issue? |
Just waiting on the go ahead to publish it 👍 |
Awesome! Does that mean you have an existing branch that I can take a look at and you're waiting to submit a PR? Or, you're waiting for approval to push to the public? |
Any updates on this issue? |
Any updates on this issue via Web UI? |
Hi Alan, The issue is that the watcher collects all the jobs to be run at startup, rather than dynamically checking what needs to be run. The underlying cause of all of that is the APScheduler implementation, specifically limitations of the old version of APScheduler. The UI calls the API, so yes API and UI are in parity on this. |
@ollytheninja Thank you so much for your quick reply with details. |
This will still be relevant. We'll need to consider using something that is able to hot-modify the scheduler in the message broker. |
will it be right if we write a script to automatically restart the supervisorctl whenever a new account is being added to the database or we encounter such thing in the logs? |
I have configured security monkey and started supervisor for all UI, scheduler, and worker, Scheduler and UI is started running but worker went to FATAL state and its not starting if i try to start.
Can you please help me to fix this. |
@ollytheninja any update about the fix, is this issue fixed? I have Redis and celery also security monkey scheduler is in a running state. I use the 1.1.3 version |
Hello @rohammosalli: In the full interest of transparency, we are actively working on Security Monkey's replacement, and are only supporting Security Monkey in a very limited fashion at this time. |
After adding a new AWS account in the web UI, users must restart the scheduler with supervisorctl.
It would be better if this was not required.
The text was updated successfully, but these errors were encountered: