[08:33:36] That sounds static to me. (re @Hugo_Lz: NP, I'm mostly the coordinator on this project so not sure for that technical aspect. We have a single page Vuejs front which qu...) [08:35:38] https://phabricator.wikimedia.org/T376267#10655764 Page https://idm.wikimedia.org/wikimedia/login/?next=/keymanagement/ says username gryllida already exists, but when I request password reset I don't get an email. I'd like to access my toolforge apps for maintenance. [09:18:47] cc bd808 [09:27:58] gry: you got some feedback on the ticket [10:27:56] arturo: BTW, I've noticed this yesterday https://gerrit.wikimedia.org/r/c/operations/puppet/+/1129786 while working on my designate credentials issue [10:34:17] vgutierrez: thanks, please merge [10:37:01] done [10:39:20] thanks! [11:04:57] Hello. On Toolforge, what is the preferred way to study the public dumps? They are in .7z and .bz2 files, but there seem to be no command line tools (e.g. 7zcat) to view them or run their contents through a pipeline. [11:10:27] Blahma: so if your tool uses the build services and wants to access the files, and the container runtime doesn't have the tooling, you could try installing the corresponding additional deb packages https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images#Installing_Apt_packages [11:19:22] arturo: Thank you. I'm not building a tool right now, just trying do some research on the dumps without having to download them to my machine. Building a container sounds complicated, I thought there would be a way to inspect those files from the command line, just like I can query the SQL replicas. But maybe there's not? [11:27:16] you request is fair, and maybe the obvious thing to do is to install the 7z tooling in the bastions [11:27:56] but folks decompressing large files, or copying large files into their home directories from the bastions wont be sustainable [11:29:21] one thing you could try is with `webservice shell` from the bastion [11:29:55] from there you can do for example: [11:29:56] tools.arturo-test-tool@shell-1742470113:~$ zcat /public/dumps/public/zuwiki/latest/zuwiki-latest-wbc_entity_usage.sql.gz [11:31:21] tools.arturo-test-tool@shell-1742470113:~$ bzcat /public/dumps/incr/enwiki/20250319/enwiki-20250319-pages-meta-hist-incr.xml.bz2 | head [11:40:24] Thank you, I will give it a try! [12:04:42] I just created this page explaining the different shells available in Toolforge: https://wikitech.wikimedia.org/wiki/Help:Toolforge/shell [15:43:53] Hi WMCS folks! I need assistance with https://phabricator.wikimedia.org/T389495. I have a VM that seems to be unable to acquire an IP address. Also, when I visit the "Interfaces" tab for the instance in Horizon, no information is ever shown. There's a corresponding hidden 500 error when accessing https://horizon.wikimedia.org/project/instances/270b6533-dc99-4e5d-a642-c61138b11891/?tab=instance_details__interfaces (which seems to be an [15:43:53] existing problem described in https://phabricator.wikimedia.org/T380531) [15:47:56] Hi dancy, I'll take a look. Regarding the interfaces tab; I'm working on fixing it but tbh you should never need to see that tab unless you're doing something truly arcane. [15:48:44] Thanks Andrew! [15:49:40] per the grafana alert, the instance seems down since 2025-02-06 22:20:58 [15:50:37] I'm curious about what happened to the VM, but is there a reason you can't delete and recreate it? Is there bespoke data/config there? [15:51:41] There's nothing bespoke in the VM. I could try deleting [15:52:11] I want to fuss with it for a bit but if you need the capacity in the meantime you should probably go ahead and create a new VM (with a new number) [15:52:13] unless you're over quota [15:52:30] I'm in no rush. Just happened to notice it today. [15:52:48] I'm curious to know what happened too [15:57:12] dancy: try now? [15:57:46] Back online! [15:58:06] I migrated it to a new hypervisor which causes the network attachment to be rebuilt. [15:58:21] After that it came up but had a very out-of-date resolv.conf which I updated [15:58:42] I'm not sure which was the cause and which was the effect; likely it got interrupted during a host migration sometime in the past. [15:59:00] Nod. The disconnect seems to be around the time of a migration. [15:59:11] Thanks! [15:59:24] If it had cinder volumes attached you might need to recheck that (and possible detach/reattach) [16:42:17] gry: Please take a look at T389496. I think the first problem is likely confusion about what the name of your Developer account is (it was not renamed; we do not rename Developer accounts). There may be other problems as well, but I think this is the first thing to clear up. [16:42:17] T389496: Password reset not working as expected for Gryllida's Developer account - https://phabricator.wikimedia.org/T389496 [16:48:37] dancy: just checking back because I vanished into a meeting... you're unblocked and set for now? [16:48:45] Yep! Thank you very much! [16:49:08] great! [18:33:16] bd808: thanks, i was able to login as you told me the wmdev accounts are not renamed. there is no section in idm, however, to add ssh keys. where can i do that, please? [18:39:22] see https://wikitech.wikimedia.org/wiki/IDM#Modifying_account_settings [20:03:12] Hey all! I'm developing a Vue JS app with node.js and Vite on Toolforge. I'm interested in running later versions of node than what's currently available (node18). I'm familiar with nvm but I'm unsure how to follow the instructions detailed here: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Node.js#Using_other_versions_of_node [20:16:04] gry: on the "hamburger menu" that drops down from the top left corner of the idm UI, there is a link titled "SSH key management" that will take you to https://idm.wikimedia.org/keymanagement/. [20:19:11] ppenloglou: rather than the dated "install your own with nvm" instructions, I would suggest you look at https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images and https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images/My_first_static_tool_using_Node.js [20:26:45] !log lucaswerkmeister@tools-bastion-13 tools.ranker deployed b1be7f07fa (l10n updates: ru) [20:26:47] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.ranker/SAL [20:54:38] !log tools.request added tools.toolforge-standards-committee to maintainers so non-root TFSC members are still able to process the request at T389540 [20:54:42] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.request/SAL [20:54:43] T389540: Adoption request for "request" tool - https://phabricator.wikimedia.org/T389540 [21:43:05] I wonder if we should auto-approve toolforge membership requests for wiki users with large numbers of edit counts [21:43:07] example: https://toolsadmin.wikimedia.org/tools/membership/status/1905 [22:49:42] bd808: /keymanagement/ loads. It's a confusing system. I deactivated two keys, added one new key and activated it, but it shows the first two as active, and the new one as not active. I tried 'ssh gryllida@login.toolforge.org' from a system with the new key. It hangs and does nothing for more than 10 seconds. [22:56:01] gry: You might try the UI for managing the same ssh keys at https://toolsadmin.wikimedia.org/profile/settings/ssh-keys/. I agree that the idm system can be a bit flaky and definitely could have nicer UI. [22:56:22] :~$ ssh gryllida@login.toolforge.org [22:56:22] ssh: connect to host login.toolforge.org port 22: Connection timed out [22:56:28] is there some solution to it? [22:56:55] * bd808 tries [22:57:26] works for me, but you could also try `ssh dev.toolforge.org` [22:58:17] if that doesn't work then we are in the "what's wrong between your laptop and the WMCS cloud" territory [22:58:25] which is pretty much https://wikitech.wikimedia.org/wiki/Reporting_a_connectivity_issue [23:00:15] same for dev.; it's a binarylane vps as client [23:01:15] gry: to rule out DNS you could also try `ssh gryllida@185.15.56.62`. These bastions shouldn't be behind the CDN edge so I don't think there are any IP origin blocks... [23:01:19] traceroute: https://dpaste.com/4RDSA3MHM.txt [23:01:25] * bd808 looks [23:02:14] huh. your trace is getting to the end. instance-tools-bastion-13.tools.wmcloud.org == login.toolforge.org [23:02:38] yea yet `ssh gryllida@185.15.56.62` also connection times out(?), been there for 10 secs and still hanging [23:02:54] let me take a peek at the auth.log [23:03:03] back in 30min, i have a meeting [23:03:17] you can privmsg me if there is some private infos, otherwise i'll check in channel when i'm back [23:05:50] gry: output of `ssh -vvv gryllida@login.toolforge.org` might be the next thing to try. I'm not seeing your username in /var/log/auth.log so I don't think things are getting all the way to the ssh handshake. [23:06:47] bd808: ok doing it now [23:07:09] bd808: https://dpaste.com/2QXGENST7.txt [23:07:16] then it's stuck [23:08:45] the next expected line would be `debug1: Connection established.` which would be the lowest level tcp socket [23:09:18] any outbound firewall stuff that might be messing with port 22 outbound?