=== wgrant changed the topic of #launchpad to: Launchpad temporarily offline due to a network issue | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [00:42] aha! that's what's been going on... :) [00:42] wxl: do you have access to https://twitter.com/launchpadstatus ? [00:43] whoops [00:43] I'm getting there. [00:43] Lots of other things to do. [00:43] meant wgrant :) [00:43] alright :) [00:43] hey, is something going on with Launchpad? [00:43] wxl: sorry, accident :) [00:43] c_smith: topic :) [00:43] ah, I see. didn't notice. XD [00:44] and wxl is here, eh? nice to see some fellow Oregonians here. [00:44] lol yeah I'm pretty good friends with him FWIW :) [00:44] don't know him all that well myself, only real contact I've had with him is through the LoCo [00:45] I see :) [00:46] now if only I could figure out why cairo dock flat out refuses to load the notification area in Arch... === wgrant changed the topic of #launchpad to: Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad === Guest76865 is now known as gkadam === pavlushka is now known as pavlushka- === pavlushka- is now known as pavlushka === gkadam is now known as Guest70234 === Guest70234 is now known as gkadam [19:49] Hello, is there a snap package builder status page to know when to avoid requesting builds? [19:50] https://launchpad.net/builders ? [19:52] PErfect, thanks dobey :) [19:54] And where do we report issues? [19:55] When pulling a dependency: EOF occurred in violation of protocol (_ssl.c:645) [19:57] for snappy builds? i presume bugs against launchpad itself (https://launchpad.net/launchpad) [19:57] Thanks you dobey [20:00] https://bugs.launchpad.net/launchpad/+bug/1569023 [20:00] Launchpad bug 1569023 in Launchpad itself "Snap builder fails to pull files (violation of protocol)" [Undecided,New] [20:15] oparoz: Is this repeatable? [20:15] It looks potentially transient to me [20:16] cjwatson: yes. Sometimes it fails elsewhere, when doing a git clone [20:16] cjwatson: This new build seems stuck: https://code.launchpad.net/~olivier-interfasys/+snap/owncloud-snap/+build/535 [20:17] OK, I've heard others muttering about the snap proxy being not totally reliable, so perhaps the former problem is that [20:17] cjwatson: Looksl ike some networking issue, but the dashboard shows everything as green [20:17] NTP> wtf [20:17] /builders won't tell you about this sort of thing [20:18] oparoz: I would suggest cancelling that one and re-requesting [20:19] we might get a more complete log after cancellation [20:19] let me try cancelling it, in fact [20:20] cjwatson: OK, I'll let you do it [20:20] mm, this isn't cancelling very quickly, so I suspect that the VM crashed early on [20:22] So, I 've tried 4 build and it used 3 different VMs, all failed at some point because of the network [20:22] I think you've misdiagnosed the last one as a network issue [20:23] looks much more like catastrophic guest crash to me [20:23] yeah, after cancellation we didn't get a build log out of it, that generally indicates that the VM was toast [20:23] try once more for luck? [20:24] the builder name basically doesn't matter, it's a fresh VM every time [20:24] so you actually got 4 different VMs [20:25] https://launchpadlibrarian.net/253330034/buildlog_snap_ubuntu_xenial_armhf_owncloud-snap_BUILDING.txt.gz is your problem to fix, not a network problem [20:25] you are not permitted network access after the pull phase has completed [20:25] hm, wait, no [20:25] ignore that last :) [20:26] cjwatson: :) [20:26] two of them seem likely to be proxy bugs [20:27] Is it all from the same machine or do these hosts belong to a cluster? [20:27] cluster [20:27] or rather, a private cloud [20:27] it's an openstack cloud running on a pile of HP Proliant m400 cartridges plugged into a single chassis [20:28] Nice pile ;) [20:28] The new build failed again, since it all fails at the same step, I suspect a proxy problem bwtween that cloud and Sourceforge [20:28] the git.l.n resolution failure is odd, I would suspect that of being a problem with the infrastructure since there's some slightly exotic stuff going on in this cloud region to avoid long-fat-pipe latency problems [20:29] oparoz: what's the URL it's trying to pull there? [20:29] The URL given as a source is HTTP, maybe it doesn't like that [20:29] source: http://sourceforge.net/projects/boost/files/boost/1.59.0/boost_1_59_0.tar.gz [20:29] HTTP should work [20:30] SF redirects it to HTTPS anyway [20:30] When I tried to get the file using wget, I do get lots of redirections [20:30] 301, 302, 302, 302, 200 [20:42] I really must arrange to get access to the production squid logs, this is difficult to debug otherwise [20:45] * cjwatson adds a card for that [20:45] cjwatson: I've launched a new build with another URL to see if it helps. Seems stuck, but maybe it's still downloading the 80MB file [20:47] Silly question but have you tried it locally? [20:47] cjwatson: Not recently. I was afraid it would rebuild MySQL... [20:47] I'm trying it here but my ADSL is very slow [20:47] But I will if it fails with the new URL [20:50] cjwatson: Just tried and no problem to pull the file [20:54] oparoz: OK. I walked five miles this morning carrying a cat back and forward to the vet so I'm pretty tired, I'll pick this up again tomorrow if none of my colleagues beat me to it [20:55] No worries, thank you cjwatson [20:58] and that one got 504 (gateway timeout). definitely need to have a look at squid logs [20:59] hmm [21:00] from a staging instance: http://paste.ubuntu.com/15767707/ [21:01] cjwatson: Locally it bounces to a non-SSL URL [21:01] With --debug I see it bouncing around a bit and then hanging [21:02] or sometimes just failing earlier [21:10] oparoz: looks like network-level trouble, I've punted to sysadmin [21:10] Thank you cjwatson! === JanC_ is now known as JanC [23:04] o/ ... login.launchpad.net is still up/down ... can't use my launchpad openid today. Anybody else experiencing that? [23:18] SpamapS: Can you explain the problem? [23:21] wgrant: I'm using openid from launchpad, and from time to time login.launchpad.net times out. [23:21] wgrant: it has also worked a few times today, so it's not 100% down. [23:21] wgrant: also o/ [23:22] SpamapS: So the problem you're seeing is a TCP connection timeout? [23:23] wgrant: I can't 100% say for sure. My browser never shows login.launchpad.net, it just shows me the openid consumer's redirect page. [23:23] wgrant: but then a refresh sometimes does work. [23:25] "The server at login.launchpad.net is taking too long to respond." [23:26] wgrant: it is working perfectly now.. so it's entirely possible the problem was internet storms. ;) [23:27] Right, but it's a network-level timeout, not an application-level one. [23:27] Thanks. [23:46] SpamapS: Which network are you connecting from? [23:46] We're seeing weird packet loss to particular external networks, so Internet storms seem reasonable. [23:56] wgrant: http://paste.ubuntu.com/15769308/ [23:58] SpamapS: Thanks. Any additional data is valuable, as everything's quite confusing.