-
Notifications
You must be signed in to change notification settings - Fork 797
Install Issues #61
Comments
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
|
A few DB tables have been added lately.
That will cause Flask-Migrate (Alembic) to update your DB to have the tables for the IgnoreList and the Network Whitelist. |
I am using Chrome I followed the revised guide today and still had the same issue. Ran those commands above and nothing changed. |
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/ |
Thanks for your time. /var/www exists and www-data is the owner. Same goes for /var/log/security_monkey drwxr-xr-x 2 www-data root 4096 Nov 6 14:04 security_monkey /var/log/supervisord.log 2014-11-06 14:06:22,329 CRIT Supervisor running as root (no user in config file) 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: Security Monkey stderr looks like this: Traceback (most recent call last): 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 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$ |
What do you have in your config-deploy.py for your LOG_FILE?
Should be this:
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) |
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 Tried to start the scheduler and it still stops. If I go into the Settings menu, there are no accounts visible. 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. |
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
The text was updated successfully, but these errors were encountered: