[06:57:36] <kaldari>	 The Tool Forge tool creation interface is giving a 404: https://toolsadmin.wikimedia.org/tools/create/
[07:00:17] <kaldari>	 is there any other way to create a new Tool Forge tool?
[08:11:27] <arturo>	 kaldari: i think the right url is https://toolsadmin.wikimedia.org/register/
[08:11:42] <arturo>	 oh I misread
[08:11:52] <arturo>	 you mean tool creation
[08:11:59] <kaldari>	 no worries :) Thanks
[08:12:25] <Amir1>	 !log ores f63fddf going staging
[08:12:26] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Ores/SAL
[08:14:11] <arturo>	 I see that 404 only if I'm not logged into the web app?
[08:14:27] <arturo>	 kaldari: ^^^
[08:15:08] <kaldari>	 I get a 404 while logged in as well
[08:15:44] <kaldari>	 I wonder if it depends on whether your Tool Forge account is connected to your Phabricator account
[08:15:57] <arturo>	 let me check in other device
[08:16:20] <arturo>	 https://usercontent.irccloud-cdn.com/file/7qFT1Hd6/Screenshot_20190415-101604.png
[08:17:00] <kaldari>	 hmmm, lemme check in a different browser.
[08:17:53] <kaldari>	 I still get 404
[08:19:00] <kaldari>	 "No handler found for the requested URI /tools/create/."
[08:19:24] <kaldari>	 If I remove the slash it works!
[08:19:39] <kaldari>	 someone needs to change the link on the main Tool Forge page
[08:20:18] <kaldari>	 Try clicking "Create a new Tool" from https://tools.wmflabs.org/
[08:21:09] <arturo>	 you are right kaldari, would you please file a bug report?
[08:21:23] <kaldari>	 I guess I should just find the code and fix it...
[08:21:36] <arturo>	 or that :-)
[08:26:30] <kaldari>	 Looks like I don't have any rights in the repo, though :(
[08:26:39] <kaldari>	 The error is in https://phabricator.wikimedia.org/F28662008
[08:26:50] <kaldari>	 line 33
[08:28:03] <kaldari>	 and I have no idea how to use Phabricator to do pull requests
[08:28:39] <kaldari>	 Guess I'll file a bug
[08:32:27] <kaldari>	 Done: https://phabricator.wikimedia.org/T220947
[09:00:11] <arturo>	 thanks kaldari 
[10:57:19] <ASammour>	 I need help with moving my java jobs to stretch grid engine. All my jobs has stopped since 25 Mar. I notice a few days ago this link: https://wikitech.wikimedia.org/wiki/News/Toolforge_Trusty_deprecation
[10:58:24] <ASammour>	 And I follow every step, but with no success. Each time I run a job I get this error from java.out: "Error occurred during initialization of VM"
[10:58:36] <ASammour>	 Also: "Could not allocate metaspace: 1073741824 bytes"
[10:59:20] <ASammour>	 And: "Could not reserve enough space for code cache"
[11:00:45] <ASammour>	 I use java written tool. I used to work with older version of java (java 7), to match the java version in toolforge.
[11:05:06] <ASammour>	 I always struggle dealing with java tools in toolforge :)
[11:11:49] <arturo>	 ASammour: perhaps you can simply allocate more memory https://wikitech.wikimedia.org/wiki/Help:Toolforge/Grid#Allocating_additional_memory
[11:17:21] <ASammour>	 arturo: This is my command for example:
[11:17:23] <ASammour>	  jsub -mem 4000m /usr/bin/java -jar /data/project/sammour/setHijri/dist/setHijri.jar
[11:17:39] <ASammour>	 The same error appears in java.out
[11:18:20] <ASammour>	 I allocate 350m first, then raise it to 4000m
[11:18:25] <chicocvenancio>	 More memory
[11:19:50] <ASammour>	 chicocvenancio: 4000m is not enough :) ?
[11:20:21] <chicocvenancio>	 The error kept repeating right? 
[11:20:25] <chicocvenancio>	 So, no. 
[11:21:21] <chicocvenancio>	 Grid is very bad at calculating used memory 
[11:26:24] <ASammour>	 I raise it to 40000m But now there is no errors appears in java.out, or java.err. And the task stay in the queue.
[11:27:00] <ASammour>	 I prompt "qstat" to query about the status of the job
[11:27:26] <chicocvenancio>	  Huh, I'm not sure if 40g will get scheduled, but if it does the error should be gone
[11:27:48] <chicocvenancio>	 8gb, or 10gb is a better bet to have it start sooner
[11:29:55] <ASammour>	 Hell!. Now it works with 9000m :)
[11:30:36] <chicocvenancio>	 :) 
[11:31:08] <ASammour>	 Thanks a lot chicocvenancio. So it's all about the memory issue?
[11:31:15] <ASammour>	 I have to update it here: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Java
[11:32:59] <chicocvenancio>	 Yes. That is common with languages that use large preloaded libraries. Java, .net
[13:08:35] <arturo>	 !log admin T219626 add DB grants for keystone/nova/nova_api to clouddb2001-dev (codfw1dev)
[13:08:38] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL
[13:08:38] <stashbot>	 T219626: codfw1dev: bootstrap cloudcontrol servers in mitaka/stretch - https://phabricator.wikimedia.org/T219626
[15:01:20] <andrewbogott>	 !log tools moving tools-redis-1001 to eqiad1-r
[15:01:34] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[15:27:20] <bd808>	 !log tools.admin Updated to 26c7d0a "Fix URL to tool creation form" (T220947)
[15:27:23] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.admin/SAL
[15:27:24] <stashbot>	 T220947: Link to create a new Tool Forge tool is broken - https://phabricator.wikimedia.org/T220947
[16:10:14] <Krenair>	 !log bastion Changed bastion-restricted* hieradata to account for https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/500640/ T220990
[16:10:17] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Bastion/SAL
[16:10:17] <stashbot>	 T220990: wmcs cumin broken - https://phabricator.wikimedia.org/T220990
[18:50:43] <andrewbogott>	 !log tools moving tools-elastic-01 to cloudvirt1008 to make spreadcheck happy
[18:50:45] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL