Install Issues about security_monkey HOT 7 CLOSED

Hey Skavenger0,

Make sure you are using Chrome. There is an open issue with other browsers.

What comes up when you add /login to the URL?

I also pushed a big update recently and the QuickStart guide has been
modified.
On Thu, Nov 6, 2014 at 7:07 AM Skavenger0 [email protected] wrote:

Hi,
Hopefully someone can help me with this as I have tried everything and
cannot get Security Monkey to work properly. I originally followed the
guide a few weeks ago and it was all working but then it stopped on its
own. Since then I have tried to re-install and I keep hitting the same
issue.

Security_monkey-deploy.log is empty.

Supervisor will not start the program.

root@ip-172-30-0-254:/home/ubuntu# supervisorctl
securitymonkey FATAL Exited too quickly (process log may have details)
securitymonkeyscheduler FATAL Exited too quickly (process log may have
details)
supervisor> restart all
securitymonkey: ERROR (abnormal termination)
securitymonkeyscheduler: ERROR (abnormal termination)
supervisor> status
securitymonkey BACKOFF Exited too quickly (process log may have details)
securitymonkeyscheduler BACKOFF Exited too quickly (process log may have
details)
supervisor> status
securitymonkey FATAL Exited too quickly (process log may have details)
securitymonkeyscheduler FATAL Exited too quickly (process log may have
details)
supervisor>

I can get the website up but it does not present the Logon page. It looks
like its logged in as Anonymous.

I'm completely stuck

—
Reply to this email directly or view it on GitHub
#61.

from security_monkey.

A few DB tables have been added lately.

export SECURITY_MONKEY_SETTINGS=/usr/local/src/security_monkey/env-config/config-deploy.py
cd /usr/local/src/security_monkey/
python manage.py db upgrade

That will cause Flask-Migrate (Alembic) to update your DB to have the tables for the IgnoreList and the Network Whitelist.

from security_monkey.

I am using Chrome
If I add /login I get 502 bad gateway.

I followed the revised guide today and still had the same issue.

Ran those commands above and nothing changed.

from security_monkey.

You said that your security_monkey-deploy.log is empty, so take a look at the supervisor logs in /var/log/supervisor/

Most likely you're running into a permissions issue. Make sure the www-data user has a home directory (/var/www) and that it has permissions to write to the logfiles in /var/log/security_monkey/

from security_monkey.

Thanks for your time.

/var/www exists and www-data is the owner.
drwxr-xr-x 3 www-data root 4096 Nov 6 14:18 www
ubuntu@ip-172-30-0-254:/var$

Same goes for /var/log/security_monkey

drwxr-xr-x 2 www-data root 4096 Nov 6 14:04 security_monkey
ubuntu@ip-172-30-0-254:/var/log$

/var/log/supervisord.log

2014-11-06 14:06:22,329 CRIT Supervisor running as root (no user in config file)
2014-11-06 14:06:22,348 INFO RPC interface 'supervisor' initialized
2014-11-06 14:06:22,348 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-11-06 14:06:22,350 INFO daemonizing the supervisord process
2014-11-06 14:06:22,350 INFO supervisord started with pid 18998
2014-11-06 14:18:41,055 WARN received SIGTERM indicating exit request
2014-11-06 14:18:46,826 CRIT Supervisor running as root (no user in config file)
2014-11-06 14:18:46,826 WARN Included extra file "/etc/supervisor/conf.d/security_monkey.conf" during parsing
2014-11-06 14:18:46,874 INFO RPC interface 'supervisor' initialized
2014-11-06 14:18:46,874 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-11-06 14:18:46,876 INFO daemonizing the supervisord process
2014-11-06 14:18:46,876 INFO supervisord started with pid 19877
2014-11-06 14:18:47,879 INFO spawned: 'securitymonkeyscheduler' with pid 19878
2014-11-06 14:18:47,880 INFO spawned: 'securitymonkey' with pid 19879
2014-11-06 14:18:48,423 INFO exited: securitymonkey (exit status 1; not expected)
2014-11-06 14:18:48,423 INFO exited: securitymonkeyscheduler (exit status 1; not expected)
2014-11-06 14:18:49,425 INFO spawned: 'securitymonkeyscheduler' with pid 19884
2014-11-06 14:18:49,427 INFO spawned: 'securitymonkey' with pid 19885
2014-11-06 14:18:50,044 INFO exited: securitymonkey (exit status 1; not expected)
2014-11-06 14:18:50,045 INFO exited: securitymonkeyscheduler (exit status 1; not expected)
2014-11-06 14:18:52,057 INFO spawned: 'securitymonkeyscheduler' with pid 19892
2014-11-06 14:18:52,078 INFO spawned: 'securitymonkey' with pid 19893
2014-11-06 14:18:52,556 INFO exited: securitymonkeyscheduler (exit status 1; not expected)
2014-11-06 14:18:52,578 INFO exited: securitymonkey (exit status 1; not expected)
2014-11-06 14:18:55,583 INFO spawned: 'securitymonkeyscheduler' with pid 19898
2014-11-06 14:18:55,584 INFO spawned: 'securitymonkey' with pid 19899
2014-11-06 14:18:56,108 INFO exited: securitymonkeyscheduler (exit status 1; not expected)
2014-11-06 14:18:56,108 INFO gave up: securitymonkeyscheduler entered FATAL state, too many start retries too quickly
2014-11-06 14:18:56,108 INFO exited: securitymonkey (exit status 1; not expected)
2014-11-06 14:18:57,110 INFO gave up: securitymonkey entered FATAL state, too many start retries too quickly

I found a permissions error with the scheduler unable to write to /usr/local/src/security_monkey/securitymonkey-deploy.log

Changed permissions and that file is now populating but it just says scheduler found no jobs stopping.

In /var/log/supervisor there are stderr logs available:
Scheduler just says that it stopped.

Security Monkey stderr looks like this:

Traceback (most recent call last):
File "/usr/local/src/security_monkey/manage.py", line 17, in
from security_monkey import app, db
File "/usr/local/src/security_monkey/security_monkey/init.py", line 40, in
handler = RotatingFileHandler(app.config.get('LOG_FILE'), maxBytes=10000000, backupCount=100)
File "/usr/lib/python2.7/logging/handlers.py", line 117, in init
BaseRotatingHandler.init(self, filename, mode, encoding, delay)
File "/usr/lib/python2.7/logging/handlers.py", line 64, in init
logging.FileHandler.init(self, filename, mode, encoding, delay)
File "/usr/lib/python2.7/logging/init.py", line 903, in init
StreamHandler.init(self, self._open())
File "/usr/lib/python2.7/logging/init.py", line 928, in _open
stream = open(self.baseFilename, self.mode)
IOError: [Errno 13] Permission denied: '/security_monkey-deploy.log'

I've done chmod 777 on /var/log/security_monkey and both security_monkey-deploy.log files and still get the Errno 13 above. I'm not sure where that is trying to write.

Tried restarting services and scheduler programs after doing all this and still it wont start.

/var/log/security_monkey/security_money-deploy.log is still empty
/var/log/security_monkey/security_monkey.error.log contains the following:

2014/11/06 14:23:02 [error] 19954#0: *10 open() "/usr/local/src/security_monkey/security_monkey/static/main.dart" failed (2: No such file or directory), cli$
2014/11/06 14:26:00 [error] 1076#0: *1 open() "/usr/local/src/security_monkey/security_monkey/static/main.dart" failed (2: No such file or directory), clien$
2014/11/06 14:50:55 [error] 1075#0: *10 open() "/usr/local/src/security_monkey/security_monkey/static/assets/ico/favicon.ico" failed (2: No such file or dir$
2014/11/06 14:50:56 [error] 1075#0: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 194.83.179.133, server: , request: $
2014/11/06 16:33:51 [error] 1074#0: *27 connect() failed (111: Connection refused) while connecting to upstream, client: 194.83.179.133, server: , request: $
2014/11/06 16:34:11 [error] 1074#0: *32 connect() failed (111: Connection refused) while connecting to upstream, client: 194.83.179.133, server: , request: $
2014/11/06 16:34:11 [error] 1074#0: *32 open() "/usr/local/src/security_monkey/security_monkey/static/favicon.ico" failed (2: No such file or directory), cl$

from security_monkey.

What do you have in your config-deploy.py for your LOG_FILE?

IOError: [Errno 13] Permission denied: '/security_monkey-deploy.log'

Should be this:

LOG_FILE = "/var/log/security_monkey/security_monkey-deploy.log"

The Scheduler will not start because there are no accounts for it to monitor yet. You'll need to get the web UI up and running so you can add an account, and then restart the scheduler. (Issue #54)

from security_monkey.

Sorry, not been in work.

The LOG_FILE variable was not as above. Changed it and now the "Security_Monkey" service is running.

Got the web page up although it doesn't seem overly stable. Still no login page. Navigated to /login
Created an account. It just hangs on register. Forced navigation to the homepage and its logged in as myself.

Tried to start the scheduler and it still stops.

If I go into the Settings menu, there are no accounts visible.
Clicked the + button and created my account.

Restarted Services. Now it looks like its working.

Just waiting for the first round of checks to kick in after 15mins now. Thanks very much for your help.

from security_monkey.