[15:30:13] <paravoid>	 someone working on netbox?
[15:30:27] <paravoid>	 volans|off, chaomodus?
[15:30:56] <cdanis>	 paravoid: are you having issues accessing it?
[15:31:06] <paravoid>	 so
[15:31:13] <paravoid>	 short answer is yes, but
[15:31:23] <paravoid>	 I've been having these connection interrupted issues for a long time
[15:31:36] <cdanis>	 yes, I remember ;)
[15:31:43] <paravoid>	 now I got a couple of these again, but this time I also got
[15:31:48] <paravoid>	 Static Media Failure
[15:31:49] <paravoid>	 The following static media file failed to load: css/base.css
[15:31:49] <paravoid>	 Check the following:
[15:31:49] <paravoid>	 manage.py collectstatic was run during the most recent upgrade. This installs the most recent iteration of each static file into the static root path.
[15:31:56] <paravoid>	     The HTTP service (e.g. nginx or Apache) is configured to serve files from the STATIC_ROOT path. Refer to the installation documentation for further guidance.
[15:31:59] <paravoid>	         STATIC_ROOT: /srv/deployment/netbox/deploy-cache/revs/03cc2ddd9f99b70dfc0efb9eeb69d846d8047225/src/netbox/static
[15:32:02] <paravoid>	         STATIC_URL: /static/
[15:32:04] <paravoid>	     The file css/base.css exists in the static root directory and is readable by the HTTP process.
[15:32:07] <paravoid>	 Click here to attempt loading NetBox again.
[15:32:09] <paravoid>	 i.e. got redirected to this page: https://netbox.wikimedia.org/media-failure/?filename=css/base.css
[15:32:18] <paravoid>	 this after a quick refresh after an interrupted connection
[15:51:28] * volans|off not at all
[16:04:46] <chaomodus>	 interesting
[16:04:58] <chaomodus>	 not worknig on it no but I have a suspicion
[16:06:19] <volans|off>	 chaomodus: double check scap logs to see if collectstatic run correctly in the last deploy
[16:06:32] <chaomodus>	 it did on netbox1001 at least
[16:06:37] <chaomodus>	 but i suspect netbox2001 is the culprit
[16:06:55] <volans|off>	 scap deploy-log --verbose
[16:09:14] <chaomodus>	 hrmph 
[16:09:21] <volans|off>	 you can pass a specific file
[16:09:22] <volans|off>	 from the log dir
[16:12:47] <chaomodus>	 which log dir
[16:13:45] <chaomodus>	 n/m
[16:13:52] <paravoid>	 volans|off: go off :P
[16:16:08] <chaomodus>	 paravoid: the error page didn't happen to say which instance was serving it did it?
[16:18:26] <paravoid>	 no
[16:18:33] <chaomodus>	 okay very cool
[16:45:26] <paravoid>	 chaomodus: what was your suspicion?
[16:45:42] <chaomodus>	 I suspected that netbox2001 is broken in some way
[16:45:52] <chaomodus>	 it does not appear to be the case *now*
[16:46:01] <chaomodus>	 and also i don't readily see how traffic gets directed to it
[16:47:12] <chaomodus>	 hm
[16:47:55] <chaomodus>	 however when api stuff emanates from nb2001 it seems to have similar problems accessing the 1001 frontend as you do, like connection interrupts
[16:55:10] <paravoid>	 so the fact that a connection was interrupted and then immediately after I got the "media failure" page
[16:55:22] <paravoid>	 suggests to me that maybe this is a periodic reload/restart or something like that
[16:55:33] <paravoid>	 without having ssh'ed or anything, purely from the perspective of a user
[17:03:25] <chaomodus>	 yes
[17:03:40] <chaomodus>	 there isn't an auto-restart to my knowledge, although the uwsgi workers only live for so long