[13:44:46] is it me or is the login bastion SLOW [13:48:21] a simple qstat command is taking over a minute to return a result [13:49:25] probably means someone is running stuff there that they shouldn't be [13:55:56] someone running convert.. [13:57:24] And two or three other processes [13:59:41] !log tools.rotbot kill `php rotbot.php` on tools-sgebastion-07 [13:59:43] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.rotbot/SAL [14:02:49] !log tools.template-inclusions kill `mono Wikipedia.exe all` [14:02:50] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.template-inclusions/SAL [14:03:01] Betacommand: Load is back under 1 now [14:19:02] thanks [14:27:03] HMMM JPEGTRAN returns Killed. Strange. [14:27:31] Is there a new cpu limit or so? [14:28:37] Reedy: well, that was me debugging stuff. sorry. :> [14:32:55] heh [18:18:03] matanya: re adoption request: my.cnf for db creds are fine, but check if the tool stores any sensitive info in db (unlikely). by "the tool secrets" you mean the secrets like k8s tokens that are local to toolforge infra right? [18:20:42] I think the general concern is if a tool has secrets to anything outside of toolforge (bot passwords / oauth tokens), or stores potentially sensitive data (like passwords in the case of TUSC in the old days, but these should be eliminated with OAuth) [18:21:42] or like it contains privileged data (say, admin bot) [22:07:12] !log tools.quickcategories deployed f10c62ced1 (new export mode) [22:07:15] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.quickcategories/SAL