Zippiness upgrade tonight

May 29, 2007

Tonight at midnight PDT there will be a bit of downtime as we switch to our new tracd cluster setup. This will make Trac super zippy and a bit more friendly on our servers. We were hoping to return Trac SSL with this update, but we weren’t able to get it properly working in time and we need to push this upgrade.

We’ll also let a few more projects in after this, so if you asked for an invite, keep an eye on your inbox.

We’re a few projects short of 1024 beta projects. When we reach this power of two we’re going to have ourselves a little hacker celebration. Just thought I’d share that. :P


15 Responses to “Zippiness upgrade tonight”

  1. w3positive Says:

    When trying to commit my project I got this error :
    svn: MERGE request failed on ‘/w3positive/francechicha’
    svn: ‘pre-commit’ hook failed with error output:
    /data/devjavu/current/projects/devjavu/svn/w3positive/hooks/pre-commit: line 2: /data/devjavu/current/config/pre-commit.proxy: No such file or directory

    What is this file ? What can I do ?
    Thanks in advance (hope it’s not a too-frequently asked question)

  2. Jeff Lindsay Says:

    Yes, a glitch in our upgrade script. It should be back to normal now + faster Trac. We don’t do these kinds of migrations very much, but we’re trying to get them done mostly before we launch. That way too we’ll be able to avoid bugs like this later by experiencing them now.

  3. torncanvas Says:

    I’m getting a LOT of Service Temporarily Unavailable errors. Generally 1 in 3 attempts to do anything returns with this. :( Is this a temporary behavior? How temporary?

  4. I’m getting the lot of Service Temporarily Unavailable errors, too, lately. No pressure intended, just to let you know.

  5. Jeff Lindsay Says:

    Our old setup led us to turning the swap off and on one of the slices that’s been killing off our new tracd processes. We have swap back on and we’ll be placing monitors on those processes. So yes, temporary behavior. ; )

  6. torncanvas Says:

    That’s all right, it’s not the end of the world. We’re managing just fine here. Thanks for letting us know what’s going on. :)

  7. chao Says:

    Congrats on reaching 1024, Jeff! We have really enjoyed and benefited from your service thus far :)

  8. torncanvas Says:

    We seem to be getting a lot of 502 Proxy Errors now. Just thought I’d give my feedback…

  9. kcbanner Says:

    I’m also getting 502 errors, I cant access my site either. Just an update to let us know would be cool.

  10. torncanvas Says:

    Fixed! Thanks guys!

  11. Jeff Lindsay Says:

    Yeah, this is turning into a bigger issue than we expected. It might take a couple days to make sure it stops happening, but until then we’ll be on alert when it goes down with a monitor script.

    We’ll post details once we figure it out.

  12. pcarman Says:

    I am getting the following message on every page request directly from a link or form submit. I hit refresh and then the page will display. The issue has been going on since the upgrade. Looks like you are looking into issues and just wanted to make sure you know about this one.

    Service Temporarily Unavailable

    The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
    Apache Server at Port 80

  13. Jeff Lindsay Says:

    Thank you for letting us know. Our monitor emails weren’t getting to us because of a permission problem. Sorry about that.

  14. Jason Says:

    FYI it’s still giving 502 proxy errors right now.

  15. Jeff Lindsay Says:

    Thanks. We’re reverting back to CGI. More info in a new post coming later tonight.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: