[05:15:18] Hey folks, I've got an old gridengine web API (weeklypedia) used to power https://weekly.hatnote.com/ that fell over last week. The task seems to be unable to start due to missing MySQL/MariaDB client libraries: "ImportError: libmariadbclient.so.18: cannot open shared object file:" [05:15:43] Seems it's not the first time: https://phabricator.wikimedia.org/T213646 [05:16:11] Any chance of getting a quick fix on this before the next newsletter goes out? (~24 hours) [05:57:10] Timing seems to line up with the Buster migration, and this ticket seems to parallel the issue: https://phabricator.wikimedia.org/T276605 [05:57:26] Also, I switched to kubernetes and I'm getting the same error. [07:13:54] I ended up porting the application from oursql to PyMySQL, which is pure-python and does not have mysql client library dependencies. [08:51:59] @telemoud: if it's a Python app, have you re-created the virtualenv on a buster machine? [08:53:44] I believe so, I definitely recreated the venv when I migrated from gridengine to k8s. [14:18:21] !log metricsinfra add 'gitlab-runners' project to list of scraped projects [14:18:22] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Metricsinfra/SAL [15:31:00] I love that there's an OurSQL now [15:31:03] Sounds like one of those memes [16:21:09] Hi. I'm wondering if there's any particular reason that toolforge is running ancient npm version, and not-that-ancient-but-still-unsupported node? [16:22:44] szczot3k: that's what stable Debian releases ship with :-) [16:24:44] although I'd be willing to ship a node16 image with nodesource repos on a bullseye base, since https://tracker.debian.org/news/1335131/accepted-nodejs-1830dfsg-1-source-amd64-all-into-experimental-experimental/ suggests we wouldn't be stuck with it once bookworm (bullseye+1) releases [16:25:32] patches welcome [16:26:50] taavi, according to debian packages - current versions in debian's stable repos are: npm 7.x and node 12.x, not npm 5.x, and node 10.x (it's still kinda old tho) [16:28:25] szczot3k: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Kubernetes has node 12.x / npm 7.x images available, the grid engine and the bastions are running an older debian release as usual [16:35:01] Yeah. That makes sense now [16:35:02] Thanks [16:36:03] By the way, does node see any usage on toolforge? I wonder is I'm just "the odd one" [16:36:23] if I'm just* [16:37:34] it definitely does, but I don't have any actual stats handy [16:44:24] https://k8s-status.toolforge.org - is down (502). I'm not sure if it's supposed to be down [17:15:08] szczot3k: that service is pretty slow to run, so a lot of times (specially when not check in a while), if you retry it might work [17:16:22] fwiw I filed T310821 for providing node 16 images [17:16:23] T310821: toolforge: Provide a node 16 image - https://phabricator.wikimedia.org/T310821 [17:24:28] * dcaro off [17:33:03] taavi, thanks! Node 16 is a lot lot better than node 10 (or node 12) [21:13:26] !log quarry 806271: Prettify User not found page | https://gerrit.wikimedia.org/r/c/analytics/quarry/web/+/806271 8002e6f06c64568441d7fc5ddc70ea2525a4c6fb [21:13:28] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Quarry/SAL [21:16:14] !log tools.lexeme-forms deployed 466976ba49 (l10n updates) [21:16:15] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL [21:19:10] Thanks Rook [21:20:58] 👍