[01:51:48] eddiegp: Are you an admin on StackOverflow? I provided the "more" correct answer a month later https://stackoverflow.com/questions/40231135/return-all-pages-which-redirect-to-a-page-in-wikipedia (backlinks does work, unless the redirect page has templates) [06:59:57] Dispenser: No, I'm not, sorry. [13:42:35] Hello, any one can help on delete page with revision more than 5,000? [13:42:51] ehh... [13:42:54] dont now. [13:42:58] now doing SWAT.. [13:43:21] :D [13:43:28] Alaa: most people request that on steward request / Miscellanious [13:43:38] It's there :D [13:44:00] Alaa is a steward. [13:44:07] needs a system admin to check everything goes well [13:44:09] I need a confirmation from (WMF's Operations Team) [13:44:22] sure [13:44:42] Alaa: for sysadmins, you mostly find them in -operations [13:44:48] but now doing SWAT deploy. I'm not good time for that... [13:45:32] SWAT is mostly done, in a few minutes it should be finished [13:53:46] Hello, Stryn, how can I assist you? [13:54:24] Hello Dereckson [13:54:26] Dereckson: I don't need any help, was just talking about the same subject as rxy and alaa [13:54:44] Dereckson: and that conversation was spread to -operations as well [13:54:56] * Dereckson checks *-operations [14:05:44] Thanks all :D [18:46:08] Hey for some reason, https://en.wikipedia.org/wiki/File:Kiidc_logo.png doesn't render on my device. [18:46:15] but others say it does? [18:47:47] This is what I see https://usercontent.irccloud-cdn.com/file/AvAqEe8k/Screen%20Shot%202018-04-09%20at%2011.46.33%20AM.png [18:49:12] Resolved by purging never mind [18:49:13] cam11598: have you tried clearing the cache? [18:49:16] yeah :) [18:49:24] Purging the page -.- [18:49:31] points to NotASpy for that one [18:50:05] * NotASpy bows [22:20:17] bd808: here good? [22:20:28] sure :) [22:20:44] so mediawiki-vagrant is fighting with you? [22:20:51] So, I had troubles with it for a couple of months of it just crapping out -- so now I am starting from scratch. I backed up the old vagrant folder, but deleted the machine -- and then re'cloned mw-vagrant, ran the ./setup.sh file, increased the RAM to 8gb, and went "vagrant up". Failure after trying to start up NFS. So I cancelled nfs_share. Failure with SSH. [22:21:22] I'm perfectly good wtih starting completely over again, if needed [22:21:36] I've already basically started over anyways [22:21:41] what's you host OS and `vagrant --version`? [22:21:49] *your [22:22:04] Ubuntu 17.10 [22:22:14] Vagrant 2.0.2 [22:23:42] ok. Are you using Virtualbox or LXC as your container host? [22:24:13] Virtualbox [22:24:25] any idea what version it is? [22:24:57] `VBoxManage --version` might tell you [22:25:01] Version 5.2.6 r120293 (Qt5.9.1) for the UI [22:25:11] let me see if I can get the virtualbox version [22:25:13] cool. so fairly recent [22:25:23] My omputer is fairly new'ish [22:25:33] About 6ish months old, I reinstalled it all [22:26:32] last boring question (maybe) mooeypoo: are you using the master branch or one of the compat branches of MediaWiki-Vagrant? [22:26:44] I just cloned it, but I can pull again? [22:27:01] (nothing to pull on master, as suspected) [22:27:14] there's no 'mediawiki' folder yet [22:27:20] It kept crashing for the first provisioning [22:27:27] either 'vagrant up' or 'vagrant provision' [22:28:27] That's why I'm saying I don't mind starting from scratch again if needed. So far, I cloned it, changed RAM, changed NFS to 'no', ran the install shell script, and did 'vagrant up' which failed (weird error after NFS) and then vagrant provision which failed, twice, each time for SSH, then I restrted -- because "did you try turning it off and on again" and tried 'vagrant provision' again and AGAIN "ssh" issue [22:29:02] ok. I had hoped the nasty ssh hang/crash stuff had died when we switched to Stretch, but maybe you have the 'luck' of proving that wrong [22:29:48] The funny thing (for a certain definition of "funny") is that I am doing this because Vagrant kept crashing in the background and would refuse to provision correctly (would crash/stall during provisions) but NOT for an SSH error [22:29:49] mooeypoo: are you getting into Puppet running at all or is it failing before the VM is fully created? [22:29:54] so I guess switching errors is ... progress? [22:30:05] I think it's after puppet [22:30:09] How can I check? [22:30:26] if it was after puppet you would have the mediawiki git clone for sure [22:30:44] This is latest failure: https://pastebin.com/hQ2USaw2 [22:31:07] I think it's after puppet. I also ssh'ed into vagrant and ran "top" to see what's up [22:31:17] oohhh... that's very early. but after the VM is up [22:31:32] it had puppet installing at some point, and then stopped, and then died [22:31:41] but it died for the SSH reason :\ [22:31:47] There was another weird failure, hang on [22:31:49] that shell provisioner tries to install Puppet into the base vm [22:32:25] let's do the "whole lot of output" debugging method. [22:32:41] https://pastebin.com/xkDkUpS2 [22:32:56] err [22:32:58] https://pastebin.com/xkDkUpS2 [22:33:23] There. This was a failure right after "NFS" was being set up, so I canceled NFS in config [22:33:26] mooeypoo: does the machine have a network connection? [22:33:48] that's a good question, because both failures could be caused by that [22:33:56] Yes, though in the above failure it MAY have had an interference -- Volker_E was complaining he has no internet... but I was chatting on hangouts, and had slow web (at the office) [22:34:06] I am, however, chatting with y'all on the machine [22:34:19] so unless I'm WiFiPsychic, it has internet :D [22:34:54] mooeypoo: let's get some noisy logs out of this -- `vagrant destroy -f; VAGRANT_LOG=debug PUPPET_DEBUG=1 vagrant up 2>&1 | tee up.log` [22:34:55] the VM may have been created with no network [22:35:01] This is a good point thought, there might be a connection issue at the office :\ there were a couple of complaints... but my internet IS working [22:35:05] hmmm [22:35:08] or it may need to go through a proxy [22:35:23] which the VM known nothing about [22:35:38] woah a lot is happening on my terminal now, bd808 [22:35:50] that command I pasted will get rid of your current VM and then start a new one with Vagrant and Puppet both yelling at you about all that they do [22:35:52] yeah, though it did work before without a proxy, but gods know [22:36:02] yeah I recognize "vagrant destroy -f" [22:36:06] We are best buddies [22:36:52] ok we're at the stage where it always crashes [22:37:06] DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh [22:37:14] I have bunch of [22:37:15] DEBUG ssh: Sending SSH keep-alive... [22:37:41] yeah, it will do that a bunch [22:37:47] bd808: want me to 'vagrant ssh' and look at the processes? It's the trick I used last time to try and figure out wtf is failng, but it may also affect some ssh stuff [22:38:07] The first time I did that through the new vagrant clone it hung there [22:38:20] mooeypoo: that's fair to try. It should be using apt to install Puppet's packages right now [22:38:26] ... but I will be positive [22:38:36] ok let's see [22:39:45] ah! apt-get in 'top' [22:40:28] mooeypoo: while you are there, maybe check to see if networking is working with `ping google.com` or something similar [22:41:04] I almost wrote "ping google.com or something similar" [22:41:05] hee [22:41:30] hm [22:41:36] https://www.irccloud.com/pastebin/zxQ22sGX/ [22:41:53] that's going to be a problem :) [22:42:00] Ha [22:42:03] OK, how did that happen [22:42:17] I am being told the office network has some issues [22:42:25] though in my host 'ping google.com' gets resolved [22:42:28] what does `cat /etc/resolv.conf` tell you? [22:42:32] could this have been JUST as I created the vm? [22:42:37] like, an intermediate issue? [22:42:51] https://www.irccloud.com/pastebin/dp1nEQx2/ [22:43:39] that /etc/resolv.conf is what I would expect. it may be the host<->guest bridge network failing somehow though [22:43:57] Should I redo the machine setup now that internet is (supposedly) working? [22:44:12] we tell the Vagrant managed guest to use the host os for dns resolution. [22:44:26] well, you just did a destroy [22:44:33] so that should all be fresh [22:44:45] hm, true, but, knowing vagrant, it has skeletons in its folders [22:47:31] hmmm... why do we enable both --natdnshostresolver1 and --natdnsproxy1? The answer is probably lost to the sands of time [22:48:27] O.O [22:50:21] mooeypoo: I think we are at least on the track of your problem. If DNS isn't working from inside the VM then things are not going to go well at all [22:50:55] hmm [22:50:59] Indeed [22:53:17] we know that there is a route from your host to the vm because ssh is working... [22:53:48] * bd808 googles "Temporary failure in name resolution" [22:55:08] Sounds like something you'd look for in webMD [22:56:24] mooeypoo: let's try a nasty hack -- echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf [22:56:30] inside the VM [22:56:37] and then -- ping google.com [22:57:03] boom! that works [22:57:30] Meanwhile, in the Host, Vagrant is still sending SSH Keep-alive's [22:57:39] ok. so we have a narrow focus of finding out why VirtualBox proxied DNS lookups are failing [22:57:55] is the apt-get process still running? [22:58:07] * bd808 would have expected it to timeout by now [22:58:16] It was up and then gone and then up again, let me see [22:58:25] I don't see it [22:58:30] there's some kworkers and 'top' [22:58:45] systemd and such.... no apt [22:59:35] should I stop and redo the earlier command, destroy -f with debugging + log ? [23:00:15] well, until we have some idea on how to fix the DNS problem that's just going to use up electricity [23:00:56] Oh, right, that would go away if I destroy [23:01:01] try removing those --natdns… parameters? [23:01:17] I could just try to reprovision [23:01:31] we can put a hack into the Vagrantfile too, as a hack attempt [23:04:07] * mooeypoo awaits instructions [23:04:28] mooeypoo: let's try turning off the fancy dns stuff that the Vagrantfile sets up just to see what happens like Platonides suggested [23:05:22] edit the Vagrantfile and comment out lines ... 178 & 179 where it does "vb.customize ['modifyvm', :id, ..." stuff [23:05:40] then do the destroy and up with loud logging thing again [23:08:11] 178 & 179 are already comments; vb.customize ['modifyvm', :id stuff is all the way from 173 to 185 [23:08:17] are we only talking about the DNS stuff? [23:08:20] thoe are 2 line [23:08:37] lines*, they're at 184/5 for me [23:08:44] mooeypoo: oh! I bet I'm looking at a version on an old branch. Trust your eyes, not my line numbers [23:08:56] * mooeypoo nods [23:09:04] comment out just the dns related stuff, though, right? [23:09:13] yeah, the 2 lines after "# Speed up dns resolution in some cases" [23:09:17] Done [23:09:55] kill the vagrant up if its still running and then start over [23:10:17] It is, indeed, persistently running [23:10:32] SSH Keep-alives.... it clings on [23:10:42] WAIT [23:10:44] it died [23:10:56] ok, whatever, I'll restart [23:11:43] whoosh [23:12:18] DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh [23:12:18] DEBUG ssh: Sending SSH keep-alive... [23:12:22] We're at this point now [23:12:50] mooeypoo: do your ssh in from the side and check the ping google.com again [23:13:10] apt-get appeared and disappeared from 'top' ... appeared again... hopefully that's a good sign [23:13:22] it's pinging google.com [23:13:31] progress! [23:13:34] \o/ [23:14:21] is the yells so much at you log saying different things yet? [23:15:16] No, keep alive still [23:16:17] in ssh, 'top' is mostly on top of the services, but apt-get occasionally makes an appearance [23:16:21] so I assume things are working [23:19:31] mooeypoo: ok. I need to go AFK for a while, but feel free to yell at me if you get stuck again I guess. [23:24:01] Will do [23:24:02] Thanks! [23:24:07] I'll let it run for a while [23:25:02] oh [23:25:04] it crashed [23:25:29] https://www.irccloud.com/pastebin/4Hr0hvkR/ [23:25:38] [23:26:06] bd808: This is actually weird, since I'm still in vagrant ssh, watching "top" [23:27:37] mooeypoo: that error means that whatever Vagrant was trying to run (maybe the support/puppet-bootstrap.sh script?) ended with an error [23:28:34] If you skip over the zillion "ssh keep-alive" log entries is there anything that actually tells you something interesting? [23:28:56] ugh. I think I remember that the support/puppet-bootstrap.sh script is silent [23:29:48] yeah, it's got " >/dev/null 2>&1" all over inside it :/ [23:30:31] mooeypoo: in your interactive session, maybe try `sudo apt-get install puppet` to see if that works or not [23:31:22] mooeypoo: I really am going AFK now for a couple of hours. sorry :/ [23:32:59] it's installing puppet [23:34:55] bd808: Err:1 http://cdn-fastly.deb.debian.org/debian stretch/main amd64 fonts-lato all 2.0-1 [23:34:55] Temporary failure resolving 'cdn-fastly.deb.debian.org' [23:35:07] You know... I'm going to stop and just redo the command from my home wifi [23:35:16] apparently there's a known issue at the office right now [23:35:30] mooeypoo: ok. I hope that works better for you [23:35:39] Me too! [23:35:41] Thanks :) [23:35:54] I have only seen this much network trouble on University networks with lots of proxy restrictions