Discodowntime redux
-
I swear it wasn't me!
well at least not intentionally.
why the site go away so suddenly?
-
it wasn't you ... I did a rebuild, @PJH started an update but I saw a white screen and pre-empted a rebuild.
In retrospect it was not needed.
I made a schema change which was not compatible with the old site so a white screen during
/admin/update
was expected, but its late here and I was worried.
-
oh.
good. it wasn't me or my horde of bots.
glad to know, and thanks for working to get us back online!
-
Half the bots didn't seem to be online after last night's restart anyway
-
Half the bots didn't seem to be online after last night's restart anyway
i had to restart all of mine.
and i would be surprised if @pjh didn't have to restart @shadowmod
-
Yet again, for reasons, @codinghorrorbot survived and didn't need restarting but the others died.
-
-
-
He's not getting the notifications.
-
He's not getting the notifications.
have you tried turning it off and on again?
if that doesn't woprk ping me in bot testing and i'll see what i can do to get you sorted out.
-
-
@loopback0 Is Doing It Wrongâ„¢
-
-
-
@loopback0 - Days Since Last Discourse Bug: -1
-
That'll do pig, that'll do.
-
and i would be surprised if @pjh didn't have to restart @shadowmod
Didn't touch it. I do have the invocation in a
while true
loop however...
-
Didn't touch it. I do have the invocation in a while true loop however...
nice.
FWIW i do recommend putting a
sleep 60s
in the mix there, otherwise it's possibly you'll start getting 429s if the bot restarts too frequently
-
git pull -vu; while true; do node SockBot.js pjh.json ; sleep 60; done
-
you already thought of it then! excellent!