• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join free Log in
    Want zero display ads or expanded classifieds tools? Compare plans.

Please try again later....

#5
I'm at GMT+1 and it's "daylight saving time" or whatever it is called - the clock is set an hour forward in the summertime here i Norway. So it could indeed be the same time.
 
#8
paul said:
Just to make certain - this happens on the :30 minute mark, and not on the hour?
Click to expand...

There is one for me at 2AM Central Time.

It starts with the website just not responding, then after a couple of minutes, I get the server busy. By the time it's 2:07ish, it's back online.
 
#9
Looks like we're all looking at the same time: 16:30 in Australia is 2:00am Central US.

I have found one scheduled task that runs at this time, however it's just an rsync backup command... I've run it manually at all times of day and it never causes any bit of increase in server load, so I'm a bit confused.

If I could get your help on this, it would be much appreciated: I moved this particular scheduled task back 3 hours. So, if you get the same error at the same time, it will rule out this task. If it happens 3 hours later (5am Central, or 19:30 in Australia), we've got our culprit.

Thanks!
 
#11
3:00 AM EST. Every day. Again tonight, like clockwork.

Funny thing is, a lot of Internet "trash collection" and other utilities are scheduled to run at 3:00 am, presumably because the traffic is low at that time...but the truth is, it really isn't.

I have my own server, and used to run a very popular website from it. Analysis actually showed that the time of least activity was actually about 5-6 am. I wish more admins would choose that as the time for such tasks, because that's really when web traffic is lowest, not 3:00 am.

It seems that there are more night owls out there than most would believe, surfing away...
 
#12
Thanks for the input. I found the culprit, it's obvious now. I've moved it back to 5am Central, as that's our slowest time according to bandwidth graphs. I'll see what I can do to optomize this process so the server doesn't overload.
 
#14
If you got a 'server busy' error at 5pm EST, it must have been an unrelated problem. The task is set to 0600 EST (linux uses a 24hr system). There are no maintenance operations occuring during daylight hours in the US.
 
#16
Alright. Well, it looks like our database has grown to the point where a live backup is not possible any longer. The webserver will have to be shut down for about 3-5 minutes while the backup occurs. When I do this, you won't get the error anymore, but you wont be able to access TB either ;( I'm getting some new hardware this fall, so I may try the live backup again.
 
#17
paul said:
Alright. Well, it looks like our database has grown to the point where a live backup is not possible any longer. The webserver will have to be shut down for about 3-5 minutes while the backup occurs. When I do this, you won't get the error anymore, but you wont be able to access TB either ;( I'm getting some new hardware this fall, so I may try the live backup again.
Click to expand...

Did you ever think this site would be this sucessful? :)`
 
You must log in or register to reply here.

Latest posts

Top Bottom
Back