[19:55] <evul18> Are there any known issues with the repos atm?
[20:03] <cjwatson> evul18: Would probably help a lot if you could narrow down what your actual problem is
[20:03] <cjwatson> I don't know of any known issues
[20:10] <evul37> cjwatson I'm seeing RST from 91.189.91.39 when using APT, but have no trouble accessing through curl or wget. Just covering my bases.
[20:14] <cjwatson> evul37: Not something I've seen reported; you could try passing -o Debug::Acquire::http=true to apt to see if that provides any more useful information
[20:20] <evul37> cjwatson this is what I'm seeing in the client, which doesn't really say anything to me: https://paste.debian.net/hidden/9ad6bea3/
[20:21] <evul37> I'm a network engineer, and nothing here really pops out at me. Connection failed with an IP and port is a pretty nondescript error lol.
[20:25] <cjwatson> evul18: I'd be at least suspecting something on the path between you and there ... tried wireshark etc., or other clients in nearby bits of your network?
[20:25] <cjwatson> or mtr for packet loss / routing oddities
[20:26] <cjwatson> IDK though, I'm technically finished work for the year :)
[20:27] <evul18> cjwatson these are the RST's I'm referring to. Problem is this is a customers network, so trying to come up with whatever I can before telling them "it works with curl and wget but not apt" which doesn't really indicate a network issue:P
[20:27] <evul18> https://i.imgur.com/MdFXdJh.png
[20:27] <cjwatson> have you forced curl to use particular addresses using --resolve to avoid round-robin DNS confounding matters?
[20:28] <evul18> That is interesting
[20:30] <evul18> Did not know that existed, however, just tried it and still the same thing. It provides the expected output.
[20:30] <cjwatson> Any firewalls on the customer network that might be doing DPI and interfering?
[20:31] <cjwatson> I'll have to defer to actual Canonical sysadmins who might be on the channel though - I have no direct access to the target machines in this case.  You can email rt@ubuntu.com if you need to raise a ticket
[20:31] <cjwatson> (It's not really a mirrors thing IMO, since the target machines in this case are on Canonical's network)
[20:32] <evul18> That's what I'm leaning towards, but why would it work with curl / wget and not the native apt or apt-get?
[21:06] <axino> (for next time, grep -ri acquire /etc/apt might help)
[21:25] <tomreyn> you mean proxy? supposedly, there was none
[21:26] <axino> tomreyn: or anything else, I don't know
[21:27] <axino> apt failing on 3 different IPs in 2 different datacenters and curl working on the same domain names indicate a problem somewhere in apt
[21:28] <tomreyn> that was evul's conclusion, too
[21:31] <axino> then the next step is "strace -fv -e network apt update" with the appropriate tcpdump running
[22:02] <tomreyn> sounds good, but they're gone.
[22:13] <axino> yup.
[22:16] <cjwatson> the wireshark screenshot didn't seem to indicate an explicit proxy FWIW, but yeah
[22:23] <axino> ah I hadn't seen it