#hypothes.is

<robertknight> Morning :)

<robertknight> Alice and me are taking a look at a coworking space (WeWork) this morning so we'll miss the standup

<seanh> No one hanging out today? It's the only one I've made it to all week!

<robertknight> Morning seanh

<nick> Hi all!

<nick> I'm going to be taking down the site for a few minutes to run some security upgrades.

<nick> one done

<nick> one more to go

<nick> although that *might* not require a reboot

<nick> we'll see

<nick> okay, all set with the database server

<nick> I'm going to reboot everything else now -- none of which should affect the site

<nick> hmm... looks like connections to rabbit are sporadically failing

<nick> that's not good

<nick> this is super weird -- it looks like the server is just resetting the TCP connection from the clients (the webservers)

<nick> but not all the time

<nick> going ahead and rebooting app-1 and app-2 in turn because it's unlikely to make this problem worse, and might even shake out whatever the issue is...

<nick> and now I can't reproduce the earlier networking errors...

<nick> which is good, but odd.

<nick> @chdorner: https://serverfault.com/questions/563281/how-ca...

<nick> So @chdorner and I are doing some analysis of the postgres migration script and the data it's put in the database.

<nick> I'm keeping some notes, and will send them round when we're done, but everything is looking pretty good so far

<lenazun> :+1::skin-tone-4:

<nick> @robertknight: even just pulling out some of these individual commits into their own PRs if it's possible to do that without breaking stuff would be good

<robertknight> @nick: Will do. I need to do a little reworking of the commits such that the client is in a working state after each one, or after a small group of changes. I'll get on with that.

<nick> thank you very much -- I do trust you that this is a great set of changes, but I do also want to be able to verify that myself :)

<robertknight> Meh, it compiles. What more could you possibly want ;)