nginx "504 Gateway Time-out" error for dashboard/attacks pages about mhn HOT 10 CLOSED

Please update to the latest code. I believe this is due to an error in how we were geo locating IPs (and causing timeouts if the IP was rfc1918). This was just fixed yesterday and merged this morning (https://github.com/threatstream/mhn/pull/30). If that works please close this issue.

from mhn.

No it hasn't been fixed even after updating to the latest code.

from mhn.

Do be sure, can you try this?

cd /opt/mhn
sudo git stash  # if this errors out then u may need to set some git config options and try again
sudo git pull
sudo git stash pop
sudo supervisorctl restart all

Reload the webapp in your browser.

If it still fails, can you provide the last 20 lines of your mhn.log file as well as the the output of this: git log | head run from your /opt/mhn dir?

from mhn.

It still fails.

sudo git log | head
commit 0adced4
Merge: f51b7fc 3684eff
Author: Jason Trost [email protected]
Date: Fri Jul 18 13:14:42 2014 -0400
Merge pull request #33 from threatstream/better-snort-logging
added year and UTC conversion to snort logging
commit f51b7fc

mhn.log:
2014-07-18 16:47:05,611 - /opt/mhn/server/mhn/tasks/rules.py - Fetching sources from 1 sources.
2014-07-18 16:47:05,612 - /opt/mhn/server/mhn/tasks/rules.py - Downloading from "http://rules.emergingthreats.net/open/snort-2.9.0/emerging-all.rules".
2014-07-18 16:48:03,262 - /opt/mhn/server/mhn/tasks/rules.py - Bulk importing 13856 rules.
2014-07-18 16:50:21,545 - /opt/mhn/server/mhn/tasks/rules.py - Rendering rules.
2014-07-18 16:51:35,271 - /opt/mhn/server/mhn/tasks/rules.py - Finished rendering rules.
2014-07-18 17:00:00,215 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D (public IP)
2014-07-18 17:02:07,446 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D
2014-07-18 17:17:10,743 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D
2014-07-18 17:19:18,123 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D
2014-07-18 17:32:44,588 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D
2014-07-18 17:34:51,820 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D
2014-07-18 17:36:59,180 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D
2014-07-18 22:48:28,332 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D
2014-07-18 22:52:27,308 - ./mhn/ui/utils.py - Could not determine flag for ip: A.B.C.D

from mhn.

Okay, but it does seems like a problem with flag fetching still.

from mhn.

@ch40s try: https://geospray.threatstream.com/ip/A.B.C.D on your browser, and let us know the response.

from mhn.

@serpulga geolocation works fine. I just noticed the geo_api in utils.py, the server is behind a web proxy so as soon as I specified the proxy in utils.py everything works fine. :)
I was hoping that the variables from /etc/environment would be used, but seems that they don't.

from mhn.

Can be closed if there is nothing to be done to prevent this behavior.

from mhn.

Thanks for explaining the issue. Hopefully this conversation will help others with the same problems.

from mhn.

@ch40s thank you for finding solution! Can you please give an example code utils.py with proxy? I dont understand where i need to specified it 👍

from mhn.