Still getting the error; filed a bug.

Bug 8127

maemo.org repository

http://repository.maemo.org/extras/d...le/release.gpg
Could not connect to repository.maemo.org:80 (80.258.164.237), connection timed out.

i am disappoint...

With the maemo 5 push to have all apps moved to maemo repos it is imperative that the repos be reliable. It doesn't work to ask us to put all our apps on a central repo and then have that repo be unreliable. There should be a back-up repo or mirrors. Changing servers isn't a good excuse; especially just before a weekend. Maemo guys, please ask your ISP to provide location redundancy and more than one machine at each location. Even my own web page has this redundancy. If not, then please drop the request that developers abandon their own repositories for maemo extras.

I am still getting timeout at least from these pages:

http://maemo.org/packages/package_in...0.8.1-3maemo1/
http://maemo.org/packages/package_in...allpaper/1.0-3
http://maemo.org/packages/package_in...catorise/0.0.5

To those providing detailed info on errors, offering useful suggestions and filing bugs: thank YOU! very helpful.

To anyone that chooses to simply complain: this is a normal consequence of growth and change. The maemo.org team has been bending over backwards, putting in incredible hours to minimize the impact and ultimately improve your experience here.

To all: your patience and consideration are appreciated, and will be rewarded by a better infrastructure.

The server is still down here.
Ping it and got back bad address.

$ ping http://repository.maemo.org/extras/
ping: bad port spec 'http://repository.maemo.org/extras/'
~ $ ping repository.maemo.org
ping: bad address 'repository.maemo.org'

You can use my mirror in the interim:

http://espejo.freemoe.org/

It doesn't mirror the Nokia binaries, just the Free Software in Extras, Extras-testing, etc.

I really appreciate the effort that is put in behind the scenes to make the service work. I've done those sort of "oh ****" very long days myself. Thanks guys!

Nonetheless, it is important infrastructure and it's funded. Akamai isn't cheap. Isn't having everything depend on one server machine a bit... inappropriate?

They have excellent geographic replication in the form of Akamai, (although that caused a problem by being a bit too clever... hopefully solved now).

Unfortunately it sounds like despite the replication, there is still a single point of failure which brings the whole tumbling down when it fails.

I am quite surprised they moved repository.maemo.org to the new system all at once, instead of a gradual cut-over over a few weeks to limit the impact of faults. (Last time I moved a server I had old and new running in tandem for a couple of months, moving parts of the service one at a time.)

Also in retrospect perhaps Monday is a better day to cut-over to a new system and give it real load for the first time

+1 interesting.

If it can happen now, it can happen again. Having seen this happen today, and been unable to do a couple of things myself today because of needing some apps I couldn't install, I think if I publish anything of note for Maemo, especially if it's commercial, I'll be looking at hosting a copy outside maemo.org as well as inside, and providing instructions for both ways of getting it.

~$ host repository.maemo.org

returns NXDOMAIN. Looks a DNS problem to me.

Still down.

$ dig repository.maemo.org
[snip]
;; ANSWER SECTION:
repository.maemo.org. 12392 IN A 80.248.164.237


We should probably expect instability for a while once it's back since everybody will be hitting the host at once. I hope you're using something lightweight like nginx or lighttpd
Anyway, good luck getting it back!