"Server too busy" message

[01101001]

It's been a little slow recently, outside of normal system-maintenance time, about 1 hour ago:

Tue Jan 26 01:26:30 UTC 2010 270 seconds
Tue Jan 26 01:30:09 UTC 2010 189 seconds
Tue Jan 26 01:33:08 UTC 2010 128 seconds
Tue Jan 26 01:37:57 UTC 2010 237 seconds
Tue Jan 26 01:38:30 UTC 2010 30 seconds

Monday had an unusual slowdown, too, a different time:

Mon Jan 25 22:05:09 UTC 2010 189 seconds
Mon Jan 25 22:06:22 UTC 2010 22 seconds
Mon Jan 25 22:07:01 UTC 2010 The server is too busy at the moment.
Mon Jan 25 22:11:47 UTC 2010 227 seconds
Mon Jan 25 22:12:00 UTC 2010 The server is too busy at the moment.
Mon Jan 25 22:13:01 UTC 2010 The server is too busy at the moment.
Mon Jan 25 22:14:00 UTC 2010 The server is too busy at the moment.
Mon Jan 25 22:15:01 UTC 2010 The server is too busy at the moment.

And, so did Sunday:

Sun Jan 24 19:35:34 UTC 2010 1894 seconds
Sun Jan 24 19:36:07 UTC 2010 7 seconds
Sun Jan 24 19:38:36 UTC 2010 96 seconds
Sun Jan 24 19:39:20 UTC 2010 20 seconds

bautbot

[Swift]

Yes, it has been very slow this morning. I had some timeout errors an hour or so ago.

[Fazor]

Yes, it has been very slow this morning. I had some timeout errors an hour or so ago.

I couldn't even get a response an hour or so ago, but it seems better now. Maybe a little slow, but nothing that's a problem.

[Fraser]

There was something else slowing the server down. I'm not sure what it was, but something was tying up all its connections. I've restarted the server and I'm going to keep it on a short leash.

I'm going to do a bunch of maintenance work on the server, that I've been putting off. So maybe this slowdown will magically go away...

[Fraser]

Hmm, maybe I need to do this right away.

[Fazor]

It's fine again on my end, but there were a grand total of 9 users logged on a minute ago. I guess I'm just one of the lucky ones . . . though with so few able to log in, it's sort of like talking to a wall . . . which I do as well.

[Fraser]

We've upgraded mySQL and PHP. Let me know if you see any problems. Next upgrade will be vBulletin.

[TheOncomingStorm]

About an hour ago when I tried to post I got this message.
Site error: the file /var/www/vhosts/bautforum.com/httpdocs/vbseo.php requires the ionCube PHP Loader ioncube_loader_lin_5.2.so to be installed by the site administrator.

[jlhredshift]

About an hour ago when I tried to post I got this message.
Site error: the file /var/www/vhosts/bautforum.com/httpdocs/vbseo.php requires the ionCube PHP Loader ioncube_loader_lin_5.2.so to be installed by the site administrator.

Wow, me too, thought it was the corporate server. Guess not.

[Swift]

I had those error messages too at that time. All seems ok now

[01101001]

It's been a couple of very smooth days following the Great Anguish. The daily maintenance period even goes pretty quick.

Wed Jan 27 10:12:17 UTC 2010 137 seconds
Thu Jan 28 10:14:40 UTC 2010 340 seconds

bautbot

[Fraser]

That's because of the PHP/mySQL upgrades, I think.

vBulletin 4 isn't going to help, in fact it's going to make you all mad with its funky new features that you'll have to relearn. Progress!

[mahesh]

... in fact it's going to make you all mad with its funky new features that you'll have to relearn. Progress!

Mayflower!

Thanks, Fraser.

[01101001]

Maintenance went swiftly.

Wed Mar 31 09:34:11 UTC 2010 251 seconds
Wed Mar 31 09:35:22 UTC 2010 22 seconds

Following the vBulletin 4 upgrade, no more than 9-1/2 minutes, as little as 4-1/2.

The day before, the possible range was 13 to 18 minutes.

bautbot

[HenrikOlsen]

Could be it's still building some of its index tables so the size of the backups isn't up to what it used to be yet.

[01101001]

Daily maintenance is just not the same anymore.

Thu Apr 1 00:02:00 UTC 2010 New day
Thu Apr 1 09:13:52 UTC 2010 352 seconds
Thu Apr 1 09:14:16 UTC 2010 16 seconds
Fri Apr 2 00:00:01 UTC 2010 New day
Fri Apr 2 05:10:13 UTC 2010 253 seconds
Fri Apr 2 09:12:46 UTC 2010 106 seconds
Sat Apr 3 00:03:01 UTC 2010 New day
Sun Apr 4 00:04:01 UTC 2010 New day
Mon Apr 5 00:00:01 UTC 2010 New day
Mon Apr 5 07:04:09 UTC 2010 189 seconds
Tue Apr 6 00:00:00 UTC 2010 New day
Wed Apr 7 00:01:01 UTC 2010 New day

A few minutes instead of forty. Nice. Hope it continues.

bautbot

[AstroRockHunter]

I got this message when I tried to go from the 'Against the Main Stream' area back to the main Forum:

This website is temporarily unavailable. Please check back later.
Unfortunately there were no suitable nodes available to serve this request.

Thinking that it might be me, I re-started my computer and tried to get to BAUT. Got the same message for several tries.

Any thoughts?

[Gillianren]

I entered through Google, because two tries using my bookmark didn't work.

[AstroRockHunter]

Also, when I do manage to access the BAUT, it either runs slow or stops working completely. When it stops working, I then can't access ANY web page, even my home page without re-starting my computer.

I'm using I.E.8, BTW.

[galacsi]

I got this message when I tried to go from the 'Against the Main Stream' area back to the main Forum:



Thinking that it might be me, I re-started my computer and tried to get to BAUT. Got the same message for several tries.

Any thoughts?

Hello : I got the same messages 3 times , just now ,from firefox , before being able to connect to the forum. The succesfull connection was very long. But an acces via google chrome/google was immediate.

[AstroRockHunter]

Hello : I got the same messages 3 times , just now ,from firefox , before being able to connect to the forum. The succesfull connection was very long. But an acces via google chrome/google was immediate.

O.K. I just loaded Google Chrome and it does load faster, but the formatting isn't correct. Is there some setting that I should change?

[slang]

These last couple of errors are likely nothing to do with the type of browser in use. AstroRockHunter's looks like it is a (temporary) problem within the new type of hosting, and in GillianRen's case it might have something to do with DNS. Granted, that is a bit of a (slightly educated) guess, and something that's happened to me the last couple of days too, a few times. A few retries usually do the trick. Anyway, switching browsers in such cases may seem to be the fix, but a couple of retries in the current browser might have fixed it as well.

[AstroRockHunter]

These last couple of errors are likely nothing to do with the type of browser in use. AstroRockHunter's looks like it is a (temporary) problem within the new type of hosting, and in GillianRen's case it might have something to do with DNS. Granted, that is a bit of a (slightly educated) guess, and something that's happened to me the last couple of days too, a few times. A few retries usually do the trick. Anyway, switching browsers in such cases may seem to be the fix, but a couple of retries in the current browser might have fixed it as well.

After two minutes and then being told that I.E. could not load this reply to thread window and then refreshing the page, I am FINALLY able to type this.

I've been having this problem ALL DAY, and this type of problem has been happening with lesser frequency since the move to the new server.

I don't think that this is a temporary problem.

Frazser, could you please look into this???

Also, on those times when things have worked correctly, when I have clicked the 'submit' button, everything hangs up and I have to leave the browser and come back to see if my message posted. So I may not know if this message posts for awhile.

[grapes]

This is weird, this was supposed to be an attachment

[Fraser]

There is no maintenance period any more, so any slowdowns you're experiencing are problems with Rackspace. Especially when you see that message that there aren't enough nodes to serve your request. That means they don't have enough computers to make the cloud really work, and I can nag them about it.

[01101001]

I'm testing a new private bautbot:

Beginning at Thu Apr 8 00:35:13 UTC 2010
Watching page http://www.bautforum.com
Reporting instances of rendering taking more than 5 seconds
Reporting instances of "The server is too busy at the moment."
Reporting instances of "This website is temporarily unavailable."
Reporting each new day
Sleeping 1 minutes after a report, otherwise 5

Thu Apr 8 03:00:05 UTC 2010 5 seconds

So it's looking for the new dreaded phrase.

This is weird, this was supposed to be an attachment

Stranger still, this article was supposed to be an accordion concert. Huh!

[Fraser]

This is fantastic, if you can track this for a couple of days, give me the data and I'll take it to Rackspace to get them to fix it.

[01101001]

I'm testing a new private bautbot:

It's not seeing the new bad news: "This website is temporarily unavailable."

Thu Apr 8 03:00:05 UTC 2010 5 seconds
Thu Apr 8 23:41:51 UTC 2010 51 seconds
Fri Apr 9 00:02:01 UTC 2010 New day
Sat Apr 10 00:03:01 UTC 2010 New day
Sun Apr 11 00:04:01 UTC 2010 New day
Mon Apr 12 00:00:01 UTC 2010 New day

Are any others still seeing "This website is temporarily unavailable"? How often?

Well, I might as well put this version into production. Look for the "temporarily unavailable" results, if any, in the regular bautbot log.

[mugaliens]

There is no maintenance period any more...

Yeah!

[01101001]

It's not seeing the new bad news: "This website is temporarily unavailable."

Bautbot scored a couple isolated instances this week. Mostly things were pretty smooth. If there's a typical sort of disruption on the new site, it is rare, an hour or two of frequent short -- circa 10-second -- delays. As here, using BAUT Forum at 1800-1900 UTC April 26 might have been a bit of a bother:

Mon Apr 26 00:00:03 UTC 2010 New day
Mon Apr 26 04:56:05 UTC 2010 5 seconds
Mon Apr 26 05:07:05 UTC 2010 5 seconds
Mon Apr 26 16:18:10 UTC 2010 10 seconds
Mon Apr 26 17:59:08 UTC 2010 8 seconds
Mon Apr 26 18:00:10 UTC 2010 10 seconds
Mon Apr 26 18:01:06 UTC 2010 6 seconds
Mon Apr 26 18:12:07 UTC 2010 7 seconds
Mon Apr 26 18:23:05 UTC 2010 5 seconds
Mon Apr 26 18:29:06 UTC 2010 6 seconds
Mon Apr 26 18:40:07 UTC 2010 7 seconds
Mon Apr 26 18:41:19 UTC 2010 19 seconds
Mon Apr 26 18:42:06 UTC 2010 6 seconds
Mon Apr 26 19:03:05 UTC 2010 5 seconds
Mon Apr 26 19:14:00 UTC 2010 This website is temporarily unavailable.
Tue Apr 27 00:00:01 UTC 2010 New day
Tue Apr 27 08:01:06 UTC 2010 6 seconds
Tue Apr 27 09:02:01 UTC 2010 This website is temporarily unavailable.
Tue Apr 27 16:53:06 UTC 2010 6 seconds
Tue Apr 27 18:39:05 UTC 2010 5 seconds
Wed Apr 28 00:00:01 UTC 2010 New day

It's nothing like the long-duration delays, measured in minutes instead of seconds, of days of old.