00:04:10  * evanlucasquit (Remote host closed the connection)
00:07:10  * node-ghjoined
00:07:10  * node-ghpart
00:11:56  * evanlucasjoined
00:13:09  * evanlucasquit (Remote host closed the connection)
00:33:36  <jbergstroem>michael___: done
00:33:48  <jbergstroem>michael___: guessing that the second bot is named something else
01:43:00  <michael___>jbergstroem: sorry had a typo in the first ip, its missing a 1. The ip is 140.211.168.4
01:43:06  <jbergstroem>michael___: ok
01:43:50  <jbergstroem>michael___: and the second name?
01:44:15  <michael___>no I se what you mean
01:44:21  <michael___>its the first one as well
01:44:41  <michael___>its test-osuosl-ubuntu14-ppc64_be-2
01:45:22  <jbergstroem>oh, test - not release. ok
01:46:15  <michael___>right the first one is the 2nd test machine and the second one is the release machine
01:51:38  <michael___>jbergstroem: In terms of the release machine, I configured it through ansible but did not add the test key obivoulsy
01:52:02  <jbergstroem>michael___: i'll ssh and add the jenkins key as well as add the machine
01:52:19  <michael___>strangely I could add it to the release ci
01:52:25  <michael___>so it should have the right key
01:52:39  <michael___>https://ci-release.nodejs.org/computer/release-osuosl-ubuntu14-ppc64_be-1/
01:52:50  <jbergstroem>ah i forget, you're in the jenkins admins group
01:53:11  <michael___>I left it off line until you did whatever remaining was needed for it though
01:55:31  <jbergstroem>it's at least in the firewall rules now
01:55:46  <michael___>I could enable it to make sure that part is working
01:55:54  <michael___>let me do that temporaritly
01:58:17  <michael___>ah it has the wrong ci
01:58:41  <michael___>do you manually update that or is there a different ansible config ?
02:01:41  <michael___>ok with that fixed up it connected. I'll put it back off line and you can do whatever's needed before bringing it back on line
02:03:23  * node-ghjoined
02:03:23  * node-ghpart
02:07:56  * node-ghjoined
02:07:56  * node-ghpart
02:11:25  * node-ghjoined
02:11:26  * node-ghpart
02:15:58  * node-ghjoined
02:15:58  * node-ghpart
02:22:53  * node-ghjoined
02:22:54  * node-ghpart
02:23:02  <jbergstroem>michael___: see priv plez
02:34:33  * node-ghjoined
02:34:33  * node-ghpart
02:37:24  * node-ghjoined
02:37:24  * node-ghpart
02:49:23  * node-ghjoined
02:49:23  * node-ghpart
02:52:58  * node-ghjoined
02:52:58  * node-ghpart
02:56:05  * node-ghjoined
02:56:05  * node-ghpart
03:01:57  * node-ghjoined
03:01:57  * node-ghpart
03:16:02  * node-ghjoined
03:16:02  * node-ghpart
03:20:13  * node-ghjoined
03:20:14  * node-ghpart
05:12:56  * stefanbujoined
05:12:56  * stefanbuchanged nick to stefanmb
05:14:35  * stefanmbquit (Remote host closed the connection)
10:27:27  * thealphanerdquit (Quit: farewell for now)
10:27:57  * thealphanerdjoined
14:05:12  * Fishrock123joined
14:23:18  <jbergstroem>just had a look at our daily backup
14:23:35  <jbergstroem>we have a growth rate of ~600-1G/day
14:23:56  <jbergstroem>a full restore (excluding workspaces) would today be around ~60G
14:24:09  <jbergstroem>(this is ci.nodejs.org)
14:26:50  <Fishrock123>jbergstroem: is that also for binaries?
14:27:01  <jbergstroem>Fishrock123: all artefacts yes
14:27:14  <Fishrock123>what if you sip it? a lot of the bainaries would have overlapping info
14:27:16  <Fishrock123>zip*
14:27:28  <jbergstroem>not quite sure i understand what you mean
14:27:45  <jbergstroem>we use rsnapshot (rsync) that rotates by hardlinking files
14:27:51  <Fishrock123>they should compress reasonably well I think, which would cut down on the storage
14:28:14  <Fishrock123>I'm not actually sure what that is
14:28:22  <Fishrock123>(i'm probably making blind suggestion)
14:28:26  * Fishrock123floats away
14:29:14  <jbergstroem>imagine you're rsyncing a full tree
14:30:00  <jbergstroem>so, next time you want to 'snapshot' you hardlink new/ to old/ - meaning the tree structure is the same but they're inode links instead of real file
14:30:00  <jbergstroem>s
14:30:08  <jbergstroem>then rsync just overwrites/deletes what's changed
14:31:03  <jbergstroem>Fishrock123: info here https://github.com/nodejs/build/tree/master/backup
14:32:57  <Fishrock123>I actually have no idea what rsync is
14:33:58  <jbergstroem>Fishrock123: https://gist.github.com/jbergstroem/4ac1709047768eb345fa65ef0ead7f2d
14:34:20  <jbergstroem>Fishrock123: rsync is the answer to most file transfer problems :)
14:34:28  <Fishrock123>ooooookay
14:34:39  <jbergstroem>million times faster than scp and helps you keep large trees in sync
14:35:35  <jbergstroem>rsync -avz path user@host:path is the quickest way for you to backup something 1:1
14:36:02  <jbergstroem>[or just run it locally]
14:37:23  <jbergstroem>some algorithms rsync use is still magic
14:39:06  <jbergstroem>dropbox and most other similar tools uses rsync in some way. anyway. </rant>
14:39:28  <jbergstroem>actually i think dropbox wrote their own version of it
15:25:15  * evanlucasjoined
15:32:53  * chorrelljoined
15:52:25  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
15:52:39  * chorrelljoined
16:01:29  * rmgjoined
16:02:37  * chorrell_joined
16:02:47  * chorrellquit (Read error: Connection reset by peer)
17:03:09  * chorrell_quit (Read error: Connection reset by peer)
17:03:15  * chorrelljoined
17:42:04  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
18:15:50  * Fishrock123quit (Remote host closed the connection)
18:34:21  * chorrelljoined
19:17:04  * Fishrock123joined
19:17:17  <thealphanerd>looks like ci-release on pi is borked
19:17:18  <thealphanerd>:(
19:17:18  <thealphanerd>https://ci-release.nodejs.org/job/iojs+release/505/nodes=pi1-raspbian-wheezy/console
19:17:23  <thealphanerd>ping jbergstroem rvagg
19:19:40  <rvagg>thealphanerd: run it again, I don't know what this error is about specifically but I know the second slave will work if you get it by random draw
19:20:09  <thealphanerd>just did it again... now failures on windows :(
19:20:10  <thealphanerd>https://ci-release.nodejs.org/job/iojs+release/506/nodes=win2008r2-release-ia32/console
19:21:48  * Fishrock123quit (Ping timeout: 246 seconds)
19:22:32  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
19:30:00  <thealphanerd>rvagg it also looks like armv7 is down
19:31:03  <thealphanerd>also looks like the centos5-x64 slave is down
19:56:01  * Fishrock123joined
20:01:26  * node-ghjoined
20:01:26  * node-ghpart
20:27:59  <jbergstroem>i can look at centos5
20:29:39  <jbergstroem>up
20:31:05  <jbergstroem>so the centos5 release slaves seems to oom
20:31:10  <jbergstroem>not sure why just release slaves
20:31:16  <jbergstroem>i will add a swap volume to avoid for now
20:36:18  <rvagg>thealphanerd: I'm driving to the airport so won't be able to look at anything for a few hours. Can you hold off if jbergstroem can't deal?
20:36:40  <jbergstroem>rvagg: just trying to find which host it is
20:37:37  <jbergstroem>ok think i have it
20:38:08  <jbergstroem>hm
20:38:17  <jbergstroem>kernel oops again. monit is not restarting the jobs
20:39:59  <jbergstroem>i'll see what i can do
20:40:03  <jbergstroem>need to fix swap first
21:31:36  * node-ghjoined
21:31:37  * node-ghpart
21:32:09  * node-ghjoined
21:32:09  * node-ghpart
21:34:21  * node-ghjoined
21:34:22  * node-ghpart
21:37:20  * node-ghjoined
21:37:21  * node-ghpart
21:39:25  * node-ghjoined
21:39:25  * node-ghpart
21:40:19  * node-ghjoined
21:40:20  * node-ghpart
23:43:01  * jenkins-monitorquit (Remote host closed the connection)
23:43:12  * jenkins-monitorjoined
23:43:17  * jenkins-monitor1quit (Remote host closed the connection)
23:43:26  * jenkins-monitor1joined
23:51:47  * Fishrock123quit (Quit: Leaving...)