asheesh changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Channel glossary: "i,i" means "I have no point, I just want to say". b == thumbs up. | Public logs at https://botbot.me/freenode/sandstorm/ & http://logbot.g0v.tw/channel/sandstorm/today
mnutt_ has joined #sandstorm
BigShip has quit [Quit: Leaving]
bb010g has quit [Quit: Connection closed for inactivity]
zeroish has quit [Remote host closed the connection]
jadewang has quit [Remote host closed the connection]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
bb010g has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
neynah has joined #sandstorm
jemc has joined #sandstorm
powderedtoast has joined #sandstorm
<powderedtoast> hello, sorry, dumb question... if i want to create an app for a team, do they have to log in with being sent an email every time to access it... or can they create an actual account?
neynah has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
jadewang has joined #sandstorm
jemc has quit [Ping timeout: 250 seconds]
neynah has joined #sandstorm
neynah has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
<asheesh> Hi powderedtoast
<asheesh> If you make an app for a team, then the best thing to ask them to do is:
<asheesh> (1) Log into your Sandstorm instance, using an email token, or Google/GitHub or whatever login provider that you have enabled that they like
<asheesh> (2) Get a "sharing link" to the grain (aka app) from you
<asheesh> (3) Notice that now, when they're logged in, the grain appears in their "Grains" list.
<asheesh> So in that sense, they can get an account and not having to have you share it freshly with them. Hope that helps.
neynah has joined #sandstorm
<powderedtoast> okay
<powderedtoast> thanks
<powderedtoast> and so each user is using a grain?
<powderedtoast> like if i have 5 grains, then 5 concurrent users max?
<dlitz> digitalcircuit: It's a Nexus 7 (flo) tablet running Android 6. I'm running GrooveBasin on Chrome, plugged into a USB power supply, with the development option turned on that prevents the screen from sleeping.
<dlitz> digitalcircuit: so yeah, I'm just keeping the screen on, and then controlling it from another device.
neynah has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
jadewang has quit [Remote host closed the connection]
pdurbin has quit [Ping timeout: 268 seconds]
pdurbin has joined #sandstorm
ragesoss has quit [Ping timeout: 250 seconds]
bemasc_ has joined #sandstorm
ragesoss has joined #sandstorm
bemasc has quit [Ping timeout: 268 seconds]
powderedtoast has quit []
neynah has joined #sandstorm
neynah has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
neynah has joined #sandstorm
neynah has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
<dlitz> digitalcircuit: Hm, it seems to continue working when I turn off the screen, as well.
Rym has quit [Quit: Connection closed for inactivity]
<dlitz> Well, it stops eventually if I stop playback---after a little while, it won't continue unless I turn the screen back on.
NwS has joined #sandstorm
amyers has joined #sandstorm
eternaleye has quit [Remote host closed the connection]
M-hrjet has quit [Remote host closed the connection]
M-eternaleye has joined #sandstorm
M-hrjet has joined #sandstorm
ecloud has quit [Ping timeout: 250 seconds]
decipherstatic has quit [Quit: Leaving]
frigginglorious has joined #sandstorm
jemc has joined #sandstorm
gkoz has quit [Ping timeout: 244 seconds]
gkoz has joined #sandstorm
asmyers has joined #sandstorm
asmyers has quit [Read error: Connection reset by peer]
asmyers has joined #sandstorm
amyers has quit [Ping timeout: 260 seconds]
NOTevil has joined #sandstorm
mnutt_ has joined #sandstorm
ecloud has joined #sandstorm
asmyers has quit [Remote host closed the connection]
asmyers has joined #sandstorm
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mnutt_ has joined #sandstorm
dwrensha has quit [Ping timeout: 244 seconds]
dwrensha has joined #sandstorm
larjona has quit [Remote host closed the connection]
larjona has joined #sandstorm
NOTevil has quit [Quit: Leaving]
Guest71645 has quit [Changing host]
Guest71645 has joined #sandstorm
Guest71645 is now known as preilly
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
neynah has joined #sandstorm
<digitalcircuit> dlitz: Alright, that sounds similar to my experience (Nexus 6 shamu, CM 13 nightlies, Firefox mobile). Roughly ~30 minutes of screen-off and playback stops, which is much longer than the ~4.5 minutes if no other device has Groove Basin open in order to send Sandstorm the keepalives.
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
M-eternaleye has quit [Changing host]
M-eternaleye has joined #sandstorm
M-eternaleye is now known as eternaleye
xet7_ has joined #sandstorm
xet7_ has quit [Client Quit]
xet7_ has joined #sandstorm
jadewang has joined #sandstorm
mnutt_ has joined #sandstorm
<pod> anyone had issues with the iPython notebook app not working on a fresh install?
<pod> I see the following when trying to create a new grain w/ it http://paste.debian.net/423894/
<dwrensha> pod: does refreshing the page help?
<pod> dwrensha: unfortunately not
<dwrensha> pod: anything interesting in the debug log?
<pod> where would one find said debug log ? :)
<pod> huh it seems like all grains are failing to start.
<dwrensha> eek
<dwrensha> Grain debug logs can be viewed through the Sandstorm topbar, by clicking on the computer screen icon.
<dwrensha> The server log can be view in the admin area, at "admin/log"
<pod> "...*** couldn't connect to grain (Error: remote exception: expected result >= minBytes; Premature EOF) ***" for the grains
<dwrensha> but I recommend looking at /opt/sandstorm/var/log/sandstorm.log
<dwrensha> for the full server log
<pod> would pasting it in here be advisable or are there things I should first redact?
<dwrensha> there shouldn't be any secrets in the log
jemc has left #sandstorm ["WeeChat 1.4"]
jadewang has quit [Remote host closed the connection]
frigginglorious has quit [Quit: frigginglorious]
<dwrensha> pod: hm. Perhaps it is a filesystem permissions issue
frigginglorious has joined #sandstorm
<dwrensha> pod: what is the result of `ls -l /opt/sandstorm/var/sandstorm/socket/` ?
<pod> there's two files devmode, backend both owner root group sandstorm
<dwrensha> that sounds right
<dwrensha> does restarting server change anything? `sudo sandstorm restart`
<pod> nope :/
<pod> is there a bug tracker that I should open an issue against?
<asheesh> github.com/sandstorm-io/sandstorm/issues aka yes
<pod> ok. i'm happy to keep this VM alive as a diagnostic place for said issue
<pod> if I run the installer elsewhere with the same sandcats subdomain will that be ok?
<asheesh> "elsewhere" == on another VM? Yup, that'll work fine.
<asheesh> It'll step you through switching sandcats to trust that new VM.
<pod> ah ok. great. :)
<kentonv> pod: how much RAM does your server have?
<pod> 2GB IIRC
<pod> yep it's 2GB
<kentonv> can you find /opt/sandstorm/var/sandstorm/grains/<grainId>/log for one of your grains that isn't working and see if there are any interesting error messages?
<pod> sure :)
<dwrensha> it looks to me like every RPC call to the backend is failing
<pod> issue with seccomp_load
<dwrensha> whoa!
<zarvox> Do you have a custom kernel that disables seccomp?
<kentonv> I think we saw this recently with someone else
<kentonv> what's your hosting provider?
<pod> scaleway.com
<kentonv> that's the one
<asheesh> (I have no point I just want to say) http://imgfave-chat-herokuapp-com.global.ssl.fastly.net/image_cache/1392792698913387.jpg "This cat is pushing a watermelon out of a lake. Your argument is invalid."
<pod> uname -r returns 4.4.4-std-3
<kentonv> you have to choose their "docker" kernel
<kentonv> their other kernels are configured with seccomp disabled
<asheesh> Needs more selftest + FAQ or something.l
<pod> really? that's so very :( and computer
<dwrensha> I guess "invalid argument" is what prctl() returns when seccomp is disabled.
<kentonv> yep
<kentonv> scalaway is the only place we've ever seen this happen
<kentonv> I don't know why someone would build a kernel with seccomp disabled
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<dwrensha> I guess the kernel API would need to be saner for the more sensible result ENOSYS to make sense.
<asheesh> pod: Can I get you to file a bug, so that I can point scaleway.com at it?
<asheesh> First with your symptoms, and then I can chime in with what the fix seems to be.
<kentonv> there is actually a dedicated seccomp() syscall these days, though for compatibility reasons we probably can't switch to it
<pod> asheesh: yep I can do that
<asheesh> Super rad, thank you!
asmyers has quit [Ping timeout: 248 seconds]
<asheesh> Hey XgF, do you happen to know people who work at Scaleway?
<asheesh> pod: Thanks! I might also ping you to ask you to file a support request with them.
<pod> that I can do also
<dwrensha> maybe we should write a variant of https://github.com/sandstorm-io/check-for-unprivileged-userns that checks for seccomp support
<asheesh> Yeah, though kentonv thinks I should try "just" fixing scaleway.com instead for now to use a kernel that doesn't even require such a check!
<dwrensha> yeah, it's wacko that that's their default kernel
frigginglorious has quit [Quit: frigginglorious]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 252 seconds]
jadewang has joined #sandstorm
frigginglorious has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
neynah has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
mnutt_ has joined #sandstorm
frigginglorious has joined #sandstorm
<maurer> dwrensha: btw, just read through that rust code, there's a bug in the case of resource exhaustion
<dwrensha> which rust code?
<maurer> dwrensha: but it's probably a non-issue given that the installer won't be running under a resource exhaustion scenario
<maurer> setuid can also fail in the case where memory or process ids are out
<maurer> so if run as root, it can fail to setuid to nobody, and then succeed in unsharing incorrectly
<dwrensha> oh, so the failure doesn't cause a panic?
<maurer> but I doubt the sandstorm installer needs to be robust against that, so vov
<maurer> setuid just uses syscall!
<maurer> there's an error code, but it's not checked
<maurer> (the last place I saw this was the rage-against-the-cage android exploit)
<dwrensha> I think I remember you talking about that. It's interesting to see that pattern pop up again!
frigginglorious has quit [Quit: frigginglorious]
<zarvox> I guess the assembly one is also possibly wrong under the same circumstances
<asheesh> : D
<asheesh> This is amazing.
<zarvox> Wow, the setuid(2) man page warns "it is a grave security error to omit checking for a failure return from setuid()"
<asheesh> Oh oops.
<asheesh> I guess I can do that. (-: It's gonna bloat the bytes though!!! (kidding; it's fine with me for it to bloat the byte count.)
frigginglorious has joined #sandstorm
<maurer> asheesh: Also it's not going to be a grave security error -t he worst it's going to do is to try to use userns when it's not enabled, and even that would require the user's machine to be under fux when sandstorm was installed ;P
<maurer> asheesh: The particular case to look at in the setuid() man page are the entries for EAGAIN
<ocdtrekkie> Did you guys see mailtrain.org on HN?
jadewang has quit [Remote host closed the connection]
BigShip has joined #sandstorm
BigShip has quit [Max SendQ exceeded]
<zarvox> ocdtrekkie: yeah, it seemed pretty clean! I'm not entirely sure how to map a mailinglist to capabilities.
BigShip has joined #sandstorm
BigShip has quit [Changing host]
BigShip has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
<mrdomino> so omniauth wants uid to not be nil, which it is if you're anonymous. i'm going to set it to a randomly generated string for now i guess.
frigginglorious has joined #sandstorm
frigginglorious has quit [Client Quit]
jadewang has joined #sandstorm
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
asmyers has joined #sandstorm
frigginglorious has joined #sandstorm
asmyers has quit [Ping timeout: 276 seconds]
frigginglorious1 has joined #sandstorm