[01:43:20] Coren: a mysterious file? [01:59:31] I don't know. Maybe it's an omen or something. [02:08:24] Unfortunately no obvious mysterious instances :-). [02:10:51] They're not accessible yet, annoyingly enough. Annoying because that is, literally, the only thing missing. [02:11:32] If you could connect, you could query. [02:16:31] I think I will be able to wait a few hours :-) (or days? Is tomorrow a holiday in the US?). [02:16:44] i wonder if the DYK in the banner (on login) rotates [02:16:53] > Did you know that your home isn't protected by default? [02:16:55] * Coren has little knowledge of USian holidays. [02:17:18] jeremyb: It does, though I think Petan's list is shortish. [02:17:28] i think it's not a holiday... [02:17:33] it's versioned? [02:17:41] Tomorrow is memorial day. [02:17:57] A holiday that means nothing to me. [02:18:01] Memorial day is May 27, not tomorrow. [02:18:08] tomorrow is not a US holiday [02:18:22] it's not memorial day [02:18:26] Coren: en.usa#holiday@group.v.calendar.google.com [02:18:35] Crap. I thought today was next week already. [02:18:39] Oops. [02:18:56] I don't know whether tomorrow is a holiday, but if it is it's not one that WMF US staff get off. [02:19:44] US staff are certainly off on memorial day. which ain't tomorrow [02:19:46] * Cyberpower678 is dumb. [02:20:21] Der [02:20:32] Durr [02:20:33] For example, May 17 was "National Defense Transportation Day". But I don't think anyone had it off for that reason. [02:24:46] To correct myself: I meant *today* :-) (at least in UTC; May 20th, "Whit Monday" this year). [02:27:39] what's that day? [02:28:29] jeremyb: http://en.wikipedia.org/wiki/Pentecost [02:29:30] http://en.wikipedia.org/wiki/Pentecost#Public_holiday suggests no holiday in the US. [02:29:48] (Or Canada :-).) [02:44:14] So yeah. Those credentials will be useful once the network actually lets the labs talk to the databases. :-) [02:45:56] Coren: And what's (who's) that hinging on? [02:46:47] Leslie, mostly. Technically, I have all the bits to go fiddle on her networking gear. In practice, especially since she's going to be within arm's reach in a few days, doing so would be profoundly unwise. :-) [02:50:10] Well, so long as Tools still has to be properly puppetized, I think you would have some protection, but as I think you worked on this very intensely over the past few days it's a good idea to let someone else with enough sleep handle the scissors :-). [03:02:57] Coren: so what hostnames will we use in labs? [03:03:47] (for DBs) [03:04:48] scfc_de: also, there's the juniper vs. cisco issue [03:05:58] i see the mysterious file now! [03:06:43] Coren: i think you need to prepend a line on that file. '[mysql]' [03:06:53] or '[client]' is even better [03:06:57] iirc [03:07:09] It's not meant to be used directly, actually, although I might as well. [03:09:47] jeremyb: I dunno yet; we have an extra complication that we have varying ports. LIke I said, I might actually fiddle something with NAT to simplify. [03:10:35] Coren: could have different bind-addresses [03:10:54] in my.cnf [03:11:14] I'll figure something out. :-) [03:11:20] i'm sure :) [03:12:51] !ping [03:12:51] pong [03:12:57] wow, you slow [03:13:04] You are root identified by name .*@wikimedia/jeremyb [03:41:05] BBL [07:56:01] jeremyb after restart the bot is always slow... at least first 2 minutes [07:56:09] freenode is spamming it with lot of information to parse [08:04:02] jeremyb why did you restart it btw? :o [08:21:37] !log deployment-prep removing thumbnails from the Gluster shared directory: cd /data/project/upload7 && find -maxdepth 3 -wholename '*/thumb'|xargs -n1 -P4 rm -v -fR [08:21:41] Logged the message, Master [09:20:31] !rq test [09:20:32] https://wikitech.wikimedia.org/wiki/Shell_Request/test?action=edit https://wikitech.wikimedia.org/wiki/User_talk:test?action=edit§ion=new&preload=Template:ShellGranted https://wikitech.wikimedia.org/wiki/Special:UserRights/test [10:37:33] Warning: There is 1 user waiting for shell: Gilfriedman (waiting 0 minutes) [10:51:02] Warning: There is 1 user waiting for shell: Gilfriedman (waiting 13 minutes) [11:04:32] Warning: There is 1 user waiting for shell: Gilfriedman (waiting 27 minutes) [11:18:06] Warning: There is 1 user waiting for shell: Gilfriedman (waiting 40 minutes) [11:31:31] Warning: There are 2 users waiting for shell, displaying last 2: Gilfriedman (waiting 54 minutes) אור שפירא (waiting 5 minutes) [11:45:01] Warning: There are 2 users waiting for shell, displaying last 2: Gilfriedman (waiting 67 minutes) אור שפירא (waiting 18 minutes) [11:58:30] Warning: There are 2 users waiting for shell, displaying last 2: Gilfriedman (waiting 81 minutes) אור שפירא (waiting 32 minutes) [12:11:56] Warning: There are 2 users waiting for shell, displaying last 2: Gilfriedman (waiting 94 minutes) אור שפירא (waiting 45 minutes) [12:25:17] Warning: There are 2 users waiting for shell, displaying last 2: Gilfriedman (waiting 107 minutes) אור שפירא (waiting 58 minutes) [12:33:34] Moo! [12:34:26] Coren: I think I have found the problem with jsub and in-script resource demands - command line parameters to qsub have a higher priority than the in-script ones, and qsub thus overwrites some of them [12:34:54] Wait, what problem with jsub? [12:35:16] Nobody told me about problems. [12:35:17] Coren: jsub ignores, for example, #$ -l v_hmem = 500MB [12:35:21] in a script file [12:35:25] Aha! [12:36:13] Well, actually, if you use -continuous, any such would be ignored entirely -- it's not invoking the script directly but wrapping it. That's not a bug, it's by design. [12:36:40] Honestly, if you use #$ in a qsub script, you're no newbie and can cope with qsub directly. :-) [12:36:58] But I see how that could be seen to be confusing. [12:36:59] Coren: not really. #$ was the suggested way of doing things on the toolserver [12:37:11] Oh, it was? [12:37:13] 'use #$ and qcronsub