Lionel_Debroux has quit [Ping timeout: 276 seconds]
aldeka_limechat has quit [Remote host closed the connection]
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Client Quit]
mnutt has joined #sandstorm
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Client Quit]
jadewang has quit [Remote host closed the connection]
isd has quit [Quit: Leaving.]
dwrensha has quit [Remote host closed the connection]
dwrensha has joined #sandstorm
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Client Quit]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 276 seconds]
azirbel has quit [Quit: Connection closed for inactivity]
DX1 has quit [Read error: Connection reset by peer]
DX1 has joined #sandstorm
mnutt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 244 seconds]
jadewang has joined #sandstorm
larjona_ has joined #sandstorm
jadewang has quit [Remote host closed the connection]
Isla_de_Muerte has joined #sandstorm
NwS has quit [Ping timeout: 272 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 272 seconds]
Telesight has joined #sandstorm
citruspi has quit [Ping timeout: 244 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 250 seconds]
kxra has quit [Ping timeout: 276 seconds]
kxra has joined #sandstorm
<afuentes>
my sandcats cert is going to expire in less than 24h and the renewal hasnt triggered yet. Is there a way to manually trigger it?
reisi has joined #sandstorm
<reisi>
hope no-one has attempted to help me while i was away; after a number of repeatable "ssd shuts down, kernel is unable to restart it and recover" panics while building sandstorm i went out and bought a new ssd, hopefully i can now complete the build :)
<reisi>
not sure why the crashes were repeatable, seemed to happen near the end of building sandstorm ui
<afuentes>
reisi, i have been up, nobody replied to you :)
<reisi>
there might be an interesting bug to be found on my old intel 520 ssd's firmware, if there was some command sequence that always stopped it
<reisi>
afuentes: thanks :D
Telesight has quit [Quit: Leaving.]
digitalcircuit has quit [Ping timeout: 250 seconds]
digitalcircuit_ has joined #sandstorm
digitalcircuit_ is now known as digitalcircuit
<reisi>
no system crash yet, just wont build the frontend; EACESS in ecmascript compiler ... I wonder if this could be NFS related
citruspi has joined #sandstorm
<reisi>
probably was, building in a non-share directory works instantly... now, let's just forget why i was trying to that in the beginning :)
<asheesh>
Howdy reisi
<asheesh>
Yeah, I was going to say - smart to build in /home/vagrant
<asheesh>
Also good morning
<asheesh>
afuentes: Wow, the autorenewal hasn't triggered? hmm.
<asheesh>
afuentes: How can you tell? But yes, you can trigger auto-renew by removing the current certs, if you really want to do that.
<asheesh>
Also I'll be boarding an airplane w/o wifi in ~20 min; apologies about the very sporadic availability.
<asheesh>
reisi: The Vagrantfile is 50% for people hacking on Sandstorm, in which case wanting to share files into the VM is nice, and 50% for people trying out Sandstorm without building it from source, in which case, no need to share files.
<afuentes>
asheesh, i can tell because of the date of the current cert is -rw------- 1 sandstorm sandstorm 5.3K Jun 29 18:05 0.response-json
<afuentes>
and the current cert says: notAfter=Jul 9 07:59:59 2016 GMT
<afuentes>
update-log says udpate successfull, but it has no date
<asheesh>
That's weird that it didn't trigger the restart though.
<afuentes>
the date of the file is the same as the cert file tho
<asheesh>
I mean, re-issuance
<asheesh>
Are there any other *.response-json files?
<afuentes>
yeah, i can dig further if you want
<afuentes>
no
<asheesh>
I have only 10-20 min but it would be very useful.
<asheesh>
Interesting.
<asheesh>
Let me see what my server logs.
<asheesh>
So fwiw on my server, I see /opt/sandstorm/var/log/sandstorm.log lines like:
<asheesh>
Since Thu Jul 07 2016 20:07:21 GMT+0000 (UTC) is more than three days away from Thu Jul 14 2016 07:59:59 GMT+0000 (UTC) not renewing HTTPS cert yet.
<asheesh>
every 1h or so
<reisi>
asheesh: good morning to you too; i was actually working off an old non-merged pull request by diracdelta but yeah, i should've tried to build in home dir earlier
<asheesh>
Yes, well, it's not like we told you to do that, so I'm sorry that you had all these troubles.
<asheesh>
afuentes: Do you have any 'is more than three days away' log lines in that file?
<asheesh>
afuentes: Your Sandstorm server is currently running, yes? The Sandcats renewal code does rely on Sandstorm itself being running.
<afuentes>
asheesh, my last is more than 3 days away line is from the same date as the cert
<afuentes>
asheesh, well, yes it is running, but that cert is never accessed
<asheesh>
What does "that cert is never accessed" mean?
<reisi>
"make test" seems to require a firefox, but I've seen some unit test looking like c++ files, are those executed as part of plain "make" or how to run those?
<afuentes>
i parse the 0.json-response and output the certs for my apache reverse proxy
<asheesh>
afuentes: Wow!
<asheesh>
OK then! : D
<asheesh>
So then... is there a HTTPS_PORT line in sandstorm.conf?
<asheesh>
No HTTPS_PORT will mean disabling the sandcats HTTPS code.
<asheesh>
which probably (?) means disabling the autorenewal stuff too.
<afuentes>
there is no line indeed... (i have it commented it)
<asheesh>
Honestly I am very excited for you and your setup, but that's probably the reason.
<asheesh>
You're much smarter than the users I built this for, which is fine, but therefore you're going to have some random issues like this. I'm happy you're here so we can work them out!
<asheesh>
s/smarter than/more experienced in system administration/
<afuentes>
yeah, sure, i dont mind dealing with issues
<asheesh>
It's a little bit of a mess, because if you do add that, then the HTTP ports will redirect to HTTPS
<asheesh>
But your Apache reverse proxy will want to speak to the HTTP ports of Sandstorm.
<asheesh>
But if not, then you could enable that line, restart Sandstorm, wait 60 sec for new certs, and then disable that line.
<afuentes>
yeah, i read about that... i dont remember what issue i had with sniproxy
<afuentes>
i thinkn it was because it was not packaged in debian ^^
<asheesh>
I'd like to give you a more useful bit of advice but that's what I can tell you before boarding this plane at least. (-:
<asheesh>
Yeah, it's too bad it's not packaged.
<afuentes>
and well, i already have an apache running in that server for other stuff
<asheesh>
Any chance you want to package it? I'd sponsor an upload into Debian and presumably sponsor a backports upload too. (-:
<asheesh>
(and then honestly I'd use it on my own server, at that point)
<afuentes>
as much as id like to, im in too many wars already u.u
<asheesh>
Hah (-: OK
<asheesh>
Anyway now you have all the info you need.
<asheesh>
reisi: BTW (a) I'm glad you're building from source, and (b) wow, nearly no one does that! I'm quite curious why you're motivated to do that!
<asheesh>
As for running the C++ stuff without Firefox...
<afuentes>
right... probably restarting with the https_port uncommented and then dissabling it again will trigger the renewal
<asheesh>
reisi: I think the C++ has no unit tests of its own, but relies on the Firefox/Selenium testing system to verify it.
<asheesh>
afuentes: Yeah - watch for messages on sandstorm.log and you'll see it happen.
<afuentes>
this is turning more hackier than id like xD
<afuentes>
i will automate it somehow
<asheesh>
Yeah afuentes - consider filing a bug to request something more useful to your use-case
<afuentes>
thanks asheesh !
<asheesh>
You're very welcome!
<reisi>
asheesh: i'm trying to work on issue #2160 and as i've only played around with oasis the first instict is to go read the test cases :)
<reisi>
asheesh: ok i'll start on those then, thanks
<asheesh>
I think you will find that the Sandstorm C++ has no unit tests to speak of (though if false, then someone should correct me), but those issues have relevant discussion that might help anyway.
<asheesh>
The Sandstorm C++ does have integration tests but they are a bit heavy to run.
<reisi>
asheesh: are those integration tests documented somewhere or do you mean the ones executed by "make test"?
decipherstatic has quit [Quit: Leaving]
<asheesh>
Yeah, I mean the ones via 'make test'
<asheesh>
One other note -- I think the usual make, aka ekam, process does execute some C++ test binaries:
<asheesh>
$ git ls-files | grep test | grep c++
<asheesh>
Those are built and executed as part of the build process, as I understand things.
<asheesh>
So there's no separate 'make test' required for those.
<reisi>
asheesh: ok good to know, thanks
<asheesh>
You're welcome! BTW I hope you'll confirm my beliefs by watching the ekam/make build output; I'm not 100% sure of what I'm saying.
<reisi>
asheesh: yes, i remember seeing lines like TEST: "somec++file" but was not sure
<asheesh>
Feel free to modify those C++ files so they assert false things, and make sure they fail (-:
Isla_de_Muerte is now known as NwS
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 258 seconds]
larjona_ has quit [Quit: Konversation terminated!]
frigginglorious has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
Telesight has joined #sandstorm
rustyrazorblade has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
jemc has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 276 seconds]
frigginglorious has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
rustyrazorblade has quit [Read error: Connection reset by peer]