n00b question. How do I restart the scheduler?

[netflix]

n00b question. How do I restart the scheduler?

[scriptsrc]

Like so:

$ cd security_monkey/supervisor
$ sudo supervisorctl -c security_monkey.ini
> restart securitymonkeyscheduler

Run status a few times to make sure it has started correctly

> status

[JaguarSecurity]

Getting unix:///tmp/supervisor.sock; no such file with the cloudformation template

[scriptsrc]

Hey Jaguar,

I've noticed this as well. Under some circumstances, supervisor seems to die off, even if security_monkey continues to run. (Root cause currently unknown)

lucab has provided a pull request ( #47 ) to switch to the system supervisor. That may (or may not) stop this from happening. That has been merged into develop but not yet pushed to master.

In the mean time, try this:

$ sudo pkill -9 python

Kills all python processes to make sure security_monkey is shut down before we launch another instance of supervisor.

$ sudo supervisord -c security_monkey.ini
$ sudo supervisorctl -c security_monkey.ini

Launching supervisord again should make sure there is a file in /tmp/supervisor.sock

[JaguarSecurity]

The steps above did not work. Any other ideas?

[scriptsrc]

Give me some more information. What happened when you launched supervisord?

$ sudo supervisord -c security_monkey.ini

Any output? Is supervisorctl still returning the same error?

[JaguarSecurity]

FATAL Excited too quickly (process log may have details)

[scriptsrc]

My guess is that your pkill command didn't kill security_monkey processes correctly so when supervisor tries to start a new instance of security monkey, the port that it is listening on is already taken.

$ ps agux | grep python
$ sudo pkill -9 python
$ ps agux | grep python

Use these commands to make sure security_monkey is shut down before trying to start supervisor again.