Logbot | #sandstorm

#sandstorm

AUTO⬇

03:50:03 fkautz is automatic sandstorm updates already enabled? or do i need to do anything special to update over time?
03:51:28 dwrensha fkautz: updates are configured through the UPDATE_CHANNEL variable in sandstorm.conf
03:52:08 dwrensha "UPDATE_CHANNEL=dev" would give automatic updates
03:52:19 dwrensha "UPDATE_CHANNEL=none" would give none
03:52:21 fkautz dwrensha: thanks
03:53:47 fkautz is there a location to list changes on a given channel?
03:54:10 fkautz if not, here's a nice example: https://coreos.com/releases/
03:54:25 dwrensha https://dl.sandstorm.io/
03:54:33 dwrensha https://github.com/sandstorm-io/sandstorm/releases
05:09:55 isd Hey -- I just set up sandstorm on a local vm, went through the whole rigmarole to get a wildcard dns entry pointed at it, went the URL for the admin token, and it just sits there saying "Loading..." forever. Any thoughts?
05:11:33 dwrensha does it successfully show the splash screen if you just go to the root URL?
05:12:04 dwrensha it should look the same as https://alpha.sandstorm.io/
05:12:35 isd dwrensha: it does.
05:14:34 dwrensha does the browser console display any errors?
05:15:01 dwrensha Are there any interesting errors in /opt/sandstorm/var/log/sandstorm.log ?
05:17:37 isd both, actually
05:18:34 isd firefox has: Firefox can't establish a connection to the server at wss://<my-sandstorm>/sockjs/644/poocglvl/websocket
05:19:14 isd the log has a few instances of Error: EACCES, permission denied '/var/sandstorm/adminToken', with a stack trace
05:19:21 dwrensha ah, so websockets aren't working
05:19:28 dwrensha are you going through nginx?
05:20:24 isd I am
05:20:32 isd here's the exception: http://pastie.org/private/raoyn5gvnlfrkjeccy3g
05:20:42 dwrensha what version is your nginx?
05:20:45 isd I gather I have to do something special for that?
05:21:02 isd whatever's current on ubuntu 14.04, let me check
05:21:19 dwrensha did you set up forwarding of websockets, as in https://github.com/sandstorm-io/sandstorm/blob/master/nginx-example.conf
05:21:21 dwrensha ?
05:21:31 isd 1.4.6
05:21:44 isd I didn't. I'll try that.
05:30:58 isd Got rid of the console error, but the behavior is the same. The other error (I'm guessing) is because I last ran 'sandstorm admin-token' as root -- is just chowing the whole of /opt/sandstorm/var/sandstorm the right/safe thing to do?
05:32:53 isd or is there a smaller part of the filesystem that's appropriate? it looks like at least the immediate parent directory for the token isn't writable either.
05:33:07 isd don't know enough about the internals to know exactly what it expects.
05:44:04 dwrensha I'm puzzled by the EACCESS error
05:44:49 isd the adminToken file is owned by root and mod 640. I'm assuming that's the problem, I just not exactly sure what all the bits should be
05:44:59 isd *mode
05:45:45 dwrensha I think it ought to be mode 644
05:46:06 dwrensha or at least, when I just tried making an admin token, that's what I got
05:46:39 dwrensha does it work if you let anyone read the adminToken?
05:46:46 isd let me check.
05:51:14 isd That gets me as far as it telling me there's no valid admin token. It's surely expired by now. Having more permissions problems getting it to generate a new one.
05:52:07 isd got it.
05:52:40 isd changed /opt/sandstorm/var/sandstorm to 770, root:sandstorm and deleted the old token file, it worked after that.
05:52:52 isd (the mode is consistent with everything else in the dir)
05:53:19 dwrensha sorry -- I've got to run right now...
05:53:36 dwrensha I'm happy that it seems to be working somewhat more for you now
05:57:27 isd dwrensha: no worries. thanks a bunch