[01:31] <cossovich> good morning folks... wondering if anyone knows what's up with au.archive.ubuntu.com? seems like it's been down for a while.
[01:43] <jea> hi cossovich 
[01:44] <jea> what ISP are you with?
[01:44] <cossovich> hey... a couple of different ones (depending on where I'm using my laptop)
[01:45] <jea> I have no issues with updating
[01:45] <jea> can you access it in a browser?
[01:45] <cossovich> I've plugged in the aarnet sources for now
[01:45] <jea> If not, can you try accessing http://mirror.aarnet.edu.au?
[01:45] <cossovich> oh really.
[01:45] <jea> au.archive.ubuntu.org is just a redirect to mirror.aarnet.edu.au
[01:46] <jea> so you can just keep using aarnet if you want
[01:46] <cossovich> yeah, that's what I'm using now... I just wanted to know if anyone else had au.archive.ubuntu.com issues or if it was just my machine.
[01:46] <jea> There have been a couple of people with problems
[01:46] <jea> you are probably the third I have seen in the last 2-3 months
[01:47] <jea> Every time someone asks, I do an update to check, and it works fine for me
[01:47] <cossovich> hmmmm
[01:47] <cossovich> ok
[01:47] <jea> can you access it in a browser?
[01:47] <jea> as in, http://au.archive.ubuntu.com ?
[01:51] <cossovich> yep
[01:52] <cossovich> although, weirdly enough it looks like the aarnet mirror site.
[01:52] <jea> yep, it should do. it is just an alias
[01:52] <cossovich> ahhhh
[01:52] <cossovich> perhaps I have a  local DNS issue.
[01:52] <jea> if you can connect there, then i would have thought updating would be alright
[01:52] <jea> what error do you get?
[01:54] <cossovich> can't remember exactly... something "unavailable" blah yada yada. I'll just leave the aarnet source if the au.archive is just an alias
[01:54] <jea> yeah, it is just an alias
[01:55] <jea> it has been pointing to aarnet for at least 5 years now I think, if not longer
[02:05] <cossovich> jea: right, well thanks for clearing that up for me :)
[02:06] <jea> no worries :)
[04:57] <jared> Wonder if that is worth a bug report if au.archive is a default somewhere
[05:00] <jea> au.archive is the default for all new installations that have an Australian city selected during install, afaik
[05:00] <jea> but from what I can tell, everyone has had local DNS issues for it
[05:01] <jea> because every time it was fine for me to do updates
[05:01] <jea> so i am not entirely sure on the issue
[05:12] <jared> If you go to it in a browser it's a littl e odd
[06:39] <bradm> whats up with au.archive?
[06:39] <bradm> I can poke someone there if we need, or remove it from rotation
[06:40] <bradm> seems ok to me though
[07:45] <jea> bradm: There have been a few people who have come in here asking if au.archive was down. However, each time this happened, I checked on my machine, and there was no issue at all. Two of them ended up being local DNS issues (we expect), but the other one I am not sure what the reason was. For at least one of them, they were able to access au.archive in a browser, but the update manager could not download packages (though nobody has given me the exact error m
[07:46] <jea> I suspect the errors have been on their end, but I guess it is possible that au.archive momentarily goes down or something like that
[07:47] <jea> mirror.aarnet seems to work for them each time, and seeing as au.archive is just an alias for mirror.aarnet, I can't see what the issue would be apart from DNS somewhere
[07:48] <bradm> jea: interesting.  sure sounds like a dns problem to me, if au.archive doesn't work, but mirror.aarnet does
[07:49] <bradm> ah, typical user error report - "This is broken!" "Whats the error message?" "Oh, something blah blah, I didn't read it."
[07:50] <jea> Yep, that is always the issue. like from earlier:
[07:50] <jea> 11:52 < jea> what error do you get?
[07:50] <jea> 11:54 < cossovich> can't remember exactly... something "unavailable" blah yada  yada. I'll just leave the aarnet source if the au.archive is  just an alias
[07:50] <jea> that was very useful to solve the issue
[07:51] <bradm> yeah.  its hard to be motivated to dig too hard if they can't even provide an error message
[07:52] <jea> I wouldn't worry about it at the moment. If someone eventually gives a decent error, then I will pass it on to you / launchpad
[07:53] <bradm> great, thanks.
[08:43] <gggs> oh hey, I had an issue like that last week
[08:45] <gggs> went away though, wasn't a very descriptive error but it could've been an IPv6 issue, since it returned something something "::CAFE:BEEF"
[08:50] <gggs> can't find it anywhere in /var/log, I guess apt/aptitude doesn't keep a log when it's updating
[08:54] <jea> bradm: maybe IPv6 could be something to look at. I hadn't considered that
[09:05] <bradm> gggs: the ipv6 address for mirror.aarnet.edu.au is 2001:388:30bc:cafe::beef, so thats entirely possible.
[09:07] <bradm> jea: doesn't really explain why au.archive doesn't work and mirror.aarnet does though, since its just a cname
[09:08] <gggs> is it signed by IP or cname?
[09:09] <gggs> I have no idea know how apt sources are signed
[09:10] <bradm> they're not signed by anything like that, otherwise every single mirror would need to modify it
[09:13] <gggs> I've had SSL errors in the past with an old version of OpenSSL, because the key was for domain.com and not sub.domain.com
[09:17] <bradm> oh, you mean https?  hrm, I guess
[09:17] <bradm> mirror.aarnet.edu.au doesn't do https anyway, so the point is moot.
[09:18] <bradm> doing https on an archive mirror doesn't seem overly useful
[09:20] <gggs> I just looked it up, and it turns out each mirror is signed with a gpg key, so that rules out that theory
[09:25] <bradm> well, no, the releases file is signed with a gpg key, not each mirror
[09:26] <gggs> that's what I meant, only issue I could think of was if mirror updates weren't atomic and the release file was updated before/after the rest of the mirror
[09:27] <bradm> without the error message its all guess work though
[09:29] <gggs> yea and no error now anyway
[09:42] <gggs> damn, I had 35+ days uptime on my RasPi- I just put something in the USB hub and it killed power
[09:49] <gggs> that being said, my old Debian 2.2 machine got to 496+ days before looping back to zero
[09:58] <jea> bradm: mm, if it is just a CNAME, then that doesn't explain it. oh well hopefully it comes up eventually