[14:46:32] @nemoralis: the proxy mapping will be deleted, and you'll need to re-create it in Horizon pointing to the new correct VM [16:12:51] !log lucaswerkmeister@tools-bastion-15 tools.codex-playground deployed e497ed5121 (Codex 2.3.2) [16:12:53] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.codex-playground/SAL [16:15:22] !log lucaswerkmeister@tools-bastion-15 tools.codex-playground deployed 3301f8c943 (add upload.wikimedia.org to CSP media-src) [16:15:23] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.codex-playground/SAL [16:20:27] !log lucaswerkmeister@tools-bastion-15 tools.codex-playground deployed f2a7f11362 (move CSP for upload.wikimedia.org to img-src) [16:20:29] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.codex-playground/SAL [19:52:49] Is there a reason `pubpeer` is an invalid tool name? It doesn't seem to be taken [19:54:27] Huh, error went away. Alright [19:54:39] Maybe it was some substring triggering the error [20:15:32] Also, user DBs aren't readable by other users unless suffixed with `_p`, correct? [20:25:27] AFAIK yes [20:25:44] (unless you requested more granular access controls perhaps, which IIRC the docs say you can do) [21:29:21] While I'm here, I have this interesting case of a cloud VM that, as far as I can tell, doesn't actually do anything. But when I shut it down, I get an error from one of my tools that goes away once I boot it back up. [21:30:09] `wikicite-refsdb-proc-1` in the `wikicite` project [21:31:45] `credbot-daily` (from the `vaccinesafety` project) is the job that errored. The `logs` directory of that tool is empty, I guess because I didn't request logging. [21:36:04] there is no such cloud vps project as 'vaccinesafety'? [21:39:13] (from the vaccinesafety *tool, edited on the telegram side) [21:40:57] yes [21:41:33] and which exact error are you getting? [21:44:18] https://pastebin.com/qZRu6v5f [21:44:39] As mentioned before, the `logs` directory from the `vaccinesafety` tool is empty [21:47:47] $HOME/credbot-daily.{err,out} are where the logs go [21:48:40] Of course... [21:48:52] I guess that's still the case even after the end of crontab [21:49:19] `toolforge jobs show credbot-daily` shows how you configured things [22:52:42] There's nothing in my tool suggesting it's calling out to that VM (it *is* calling out to Tools-DB). To rule out red herrings I've shut down the VM again to see if I can trigger the error again. [22:53:04] If the only tool you have is a fishing rod, every error looks like a red herring [23:03:12] !bash If the only tool you have is a fishing rod, every error looks like a red herring [23:03:13] bd808: Stored quip at https://bash.toolforge.org/quip/7G6zmpsB8tZ8Ohr0LoGX