SourceForge downtime

SourceForge site status:

On 2006-03-30 the developer CVS server had a hardware issue that required us to take the service offline. We are actively working on this problem and hope to have it back up soon. There is not a current estimate for the duration of this outage, but when we get one, it will be posted on the site status page (this page). We currently expect this outage to last 48 hours, at minimum.

96 hours and counting.

The SourceForge engineering blog, which would be the most natural place to keep customers informed about issues, currently has this to say:

Warning: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: FATAL: database is not accepting commands to avoid wraparound data loss in database “postgres” HINT: Stop the postmaster and use a standalone backend to vacuum database “postgres”. in /var/local/s9y/include/db/postgres.inc.php on line 38

In the meantime, the SourceForge bigshots have sent out one of their happy monthly newsletters, without a word about the problem.

I love SourceForge. Open source wouldn’t be what it is today without their service, which is provided free of charge for most users. But this sucks.

(Update: It works again. After five days.)

This entry was posted in General. Bookmark the permalink.

6 Responses to SourceForge downtime

  1. Riad says:

    Hey Richard,

    this is Riad. Remember me from computer graphics/compiler lectures? Very nice blog you got here! :-)

    Oh.. don’t let me even get started on SourceForge! I’m kinda having a love/hate affair with them. I mean I love their free file hosting and everything, but.. (mhmm.. let me phrase this in some way, that won’t prohibit me from getting on their “project of the month” for ever).. they also tend to have some areas where they could improve ;-)

    My favorite annoyance is their broken CVS stats. Instead of the real numbers it always says 0 commits and 0 adds on my project. This tends to confuse the heck out of everybody, because everybody thinks that my CVS repository isn’t used. The funny thing? It’s not broken since some weeks or even months: It never worked since I registered my project in October 2004! Seriously now, that’s ridiculous! Fix it or remove that stupid counter for once! Do anything!

    Not to mention the time when they closed their download stats system, months before they were done on the new one. Or the fact that their download stats are still “Exiting with Error” all the time. Or the fact that doing a new release takes ages, because their interface is kinda slow and complicated.

    Well.. I’ll stop here, because I still appreciate their services and what they’ve done for open source! And they got SVN at last! :-D

  2. Hi Riad, sure I remember you. Too bad you stopped blogging!

    I still remember a time when the CVS stats did work. I think that was in 2002.

    SourceForge certainly lacks the openness and user focus I’ve come to expect from companies doing business on the web. Maybe a Web 2.0 startup will come along and build a fun, beautiful and easy to use software project hosting service.

    Man, I’d pay for that.

  3. Hm … might this be a ploy to get folks to use the new subversion repositories instead of CVS???

  4. Riad says:

    SF is definitly very Web 1.0-ish. Mhmm.. maybe I should try Trac for feature/bug tracking and use SF only for file hosting.

    On Blogs: I’ll start blogging again, once I’ve figured out what I actually want to write about. Until then I’ll have to misuse my project blogs for personal ramblings ;-)

  5. Trac rocks. And the SourceForge trackers are certainly not the best parts of the service, anyway.

    Yeah, the “what to write about” problem. Took me two years to get over that ;-) Let me know when you start again.

  6. Riad says:

    I just noticed that even the repository stats seem to work for SVN. I’m sooo migrating to SVN.

Comments are closed.