[02:00:50] <wm-bot>	 !log anticomposite@tools-sgebastion-10 tools.stewardbots ./stewardbots/StewardBot/manage.sh restart # RC reader not reading RC
[02:00:52] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[09:46:00] <wm-bot>	 !log taavi@tools-sgebastion-11 tools.wikibugs toolforge jobs restart redis2irc
[09:46:03] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wikibugs/SAL
[10:08:46] <wm-bot>	 !log lucaswerkmeister@tools-sgebastion-10 tools.bridgebot Double IRC messages to other bridges
[10:08:49] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.bridgebot/SAL
[11:57:05] <wm-bot>	 !log taavi@tools-sgebastion-11 tools.wikibugs toolforge jobs restart redis2irc
[11:57:08] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wikibugs/SAL
[14:08:15] <taavi>	 !log cloudinfra update cloudinfra-idp-1 to java 17 to fix CAS class loading errors on idp.wmcloud.org T357749
[14:08:19] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Cloudinfra/SAL
[14:08:19] <stashbot>	 T357749: Move CAS to Java 17 - https://phabricator.wikimedia.org/T357749
[14:54:51] <wm-bb>	 <Yetkin> how to stop a toolforge jobs still running?
[15:23:27] <wm-bb>	 <Yetkin> @albertoleoncio
[16:07:01] <Rook>	 !log paws increase prometheus retention T357786
[16:07:05] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL
[16:07:05] <stashbot>	 T357786: Increase prometheus retention time - https://phabricator.wikimedia.org/T357786
[16:07:16] <bd808>	 @Yetkin: it would depending on where the job is running and how it is started, but broadly: `qdel $ID` for the grid engine, `toolforge jobs delete $name` for the Kubernetes job service, and `webservice stop` for a webservice (grid or kubernetes)
[16:30:05] <wm-bb>	 <Yetkin> @bd808 toolforge delete "deletes" the job. I would like to kill the active instance only
[16:34:02] <bd808>	 @Yetkin: I think the current way to do that is with direct use of `kubectl` to talk to Kubernetes. `kubectl get pods` should should you a list of things that are running and then `kubectl delete pod $podname` would stop a particular job's container
[16:34:15] <bd808>	 *should show you
[16:35:02] <bd808>	 this is very similar to the grid engine `qstat` followed by `qdel` workflow
[16:55:22] <wm-bb>	 <Yetkin> @bd808 hmm, kubectl delete pod "x" terminates the current pod but starts a new isntance of the related job. Is there a way to terminate the pod without restarting the job?
[16:57:23] <bd808>	 Hmmm... does it restart jobs that are not setup to retry on failure? I wouldn't expect a ReplicaSet to exist to trigger a restart like would happen for something managed by `toolforge webservice`.
[16:57:47] <bd808>	 Maybe there is a better way. What is your concrete use case?
[17:01:41] <JJMC89>	 assuming this is for a cronjob, `kubectl get jobs` will show individual jobs created by the cronjob, then `kubectl delete job $jobname`
[17:09:24] <wm-bot>	 !log anticomposite@tools-sgebastion-10 tools.stewardbots ./stewardbots/StewardBot/manage.sh restart # RC reader not reading RC
[17:09:26] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[17:09:28] <wm-bot>	 !log anticomposite@tools-sgebastion-10 tools.stewardbots SULWatcher/manage.sh restart # SULWatchers disconnected
[17:09:30] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[17:11:33] <wm-bb>	 <Yetkin> yes, this is exactly what I am looking for. Thanks! (re @wmtelegram_bot: <JJMC89> assuming this is for a cronjob, `kubectl get jobs` will show individual jobs created by the cronjob, then `kubectl dele...)
[19:24:38] <wm-bot>	 !log lucaswerkmeister@tools-sgebastion-10 tools.wd-shex-infer deployed 8074aaeeef (mounts optional in config, T320140)
[19:24:42] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-shex-infer/SAL
[20:30:57] <Guest35>	 Is there any chance of being unblocked for a sockpuppet?
[20:31:21] <wm-bot>	 !log lucaswerkmeister@tools-sgebastion-10 tools.wd-shex-infer deployed f5f0149b33 (don’t set TOOL_DATA_DIR explicitly, T320140)
[20:31:26] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-shex-infer/SAL
[20:32:51] <Guest35>	 I don't know what to do......
[20:33:24] <Guest35>	 I dont able to use my talk page also..... so..... how can i....