[10:42:23] !log toolsbeta create new ingress node toolsbeta-k8s-ingress-3 T264221 [10:42:28] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [10:42:28] T264221: Upgrade the nginx ingress controller in Toolforge (and likely PAWS) - https://phabricator.wikimedia.org/T264221 [10:57:44] !log tools import docker image k8s.gcr.io/ingress-nginx/controller:v0.46.0 to local registry as docker-registry.tools.wmflabs.org/nginx-ingress-controller:v0.46.0 T264221 [10:57:48] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [10:57:49] T264221: Upgrade the nginx ingress controller in Toolforge (and likely PAWS) - https://phabricator.wikimedia.org/T264221 [17:18:16] has anyone used pm2 on toolforge? [17:29:59] sd0001: what are you trying to do with it? I'd imagine it would just run everything on the bastion, which would cause issues [17:34:46] just heard some nice things like it being able to allow code update with zero-downtime. What I did was put the npm start script as "pm2 start server.js" instead of the usual "node server.js". But on opening a shell in the k8s instance and running "pm2 list" (which should list active processes) it comes out empty, though the webservice is actually running. [17:35:59] `webservice shell` launches a separate container, it doesn't attach to the existing one [17:36:58] oh, is there a way to get a shell inside the instance on which the webservice is actually running? [17:37:36] i had tried `kubectl exec --stdin --tty MYPOD -- /bin/bash` where MYPOD is from the output `kubectl get pods` [17:37:37] you should be able to do that with kubectl exec (re @wmtelegram_bot: oh, is there a way to get a shell inside the instance on which the webservice is actually running?) [17:38:24] that's what I would suggest, does it work? [17:38:47] no it seems to be a different instance [17:40:03] sd0001: could you be more specific? Why do you think it is a different instance? What did you type? What was the result? [17:40:56] the "pm2 list" command doesn't list the active pm2 process [17:42:10] that is not at all specific [17:43:16] do you mind if I take a look at it with my admin rights? which tool, `sdzerobot`? [17:44:05] chicovenancio: sorry. I mean the webservice was initialised with "pm2 start server.js" command. So running "pm2 list" (which should list active processes) should list that process. But it doesn't. [17:44:12] Majavah: yep [17:48:29] sd0001: I see `node server.js` running on the container, and that's in www/js/package.json as well, so unless I'm not seeing something obvious it's not even trying to use pm2 [17:52:53] Majavah: damn, i did change that on the host through vim, but it looks like my IDE overwrote it as it was configured to keep the remote files in sync [17:54:12] sd0001: as a side note, I haven't heard anyone else use pm2 in toolforge, so please let us know about its up/downsides, we're interested in hearing how different tooling works there / what we can improve on the infrastructure side [17:55:16] ok, will do!