• Follow us on Twitter @buckeyeplanet and @bp_recruiting, like us on Facebook! Enjoy a post or article, recommend it to others! BP is only as strong as its community, and we only promote by word of mouth, so share away!
  • Consider registering! Fewer and higher quality ads, no emails you don't want, access to all the forums, download game torrents, private messages, polls, Sportsbook, etc. Even if you just want to lurk, there are a lot of good reasons to register!
MililaniBuckeye;1077954; said:
Couldn't get anything for about 3-4 minutes...kept timing out with "can't find the page" error. When the forum front page finally loaded (after about the fifth or sixth refresh) and I clicked on the Administrative Forum, the same thing happened. After about the third refresh, the header area loaded fairly slowly and then locked for a minute or so before finally loading. When I clicked on this thread, it timed out twice and on the third refresh it loaded near instantly. This started around 6:10 PM HST (11:10 PM EST).

i proudly proclaim responsiblity for that initial attack... the first of many on my campaign to usurp BP.

join the revolution Mili. PM me. we need bread to feed all the recruits (one less since bobcatbuckeye has already been martyred).

viva la revolucion!
 
Upvote 0
KyleDawson;1077962; said:
i proudly proclaim responsiblity for that initial attack... the first of many on my campaign to usurp BP.

join the revolution Mili. PM me. we need bread to feed all the recruits (one less since bobcatbuckeye has already been martyred).

viva la revolucion!
Hey kyle, Don't worry about in , I hear the effects of smoking that stuff wear off after a few hours. :tongue2:
 
Upvote 0
MililaniBuckeye;1077954; said:
Couldn't get anything for about 3-4 minutes...kept timing out with "can't find the page" error. When the forum front page finally loaded (after about the fifth or sixth refresh) and I clicked on the Administrative Forum, the same thing happened. After about the third refresh, the header area loaded fairly slowly and then locked for a minute or so before finally loading. When I clicked on this thread, it timed out twice and on the third refresh it loaded near instantly. This started around 6:10 PM HST (11:10 PM EST).

Yeah, I experienced the same several times today at work, I would time out, refresh, time out then after a few minutes connect. I thought it was specific to my work connection and there might be routing issues, but trace route went through fine, and each time we times out I could ping and get a fairly quick response time.

If it happens again I will post times, today was just bleh at work and I actually had to do stuff instead of just hanging out here :(
 
Upvote 0
KyleDawson;1077962; said:
i proudly proclaim responsiblity for that initial attack... the first of many on my campaign to usurp BP.

join the revolution Mili. PM me. we need bread to feed all the recruits (one less since bobcatbuckeye has already been martyred).

viva la revolucion!

You sound like a mama's boy. Does shetuck you into bed?
 
Upvote 0
Access over the last 10-15 minutes has been sporadic...site would be unavailable for a few minutes, available for a minute or so, and then unavailable again (around 3:30 am EST). Database backups?
 
Upvote 0
Nope. Hard to say what that would have been. There are some cron jobs that run between 2am and 6am that tend to bog the machine down a bit for a few minutes these days, could have been one of them.
 
Upvote 0
Clarity;1132737; said:
There are some cron jobs that run between 2am and 6am that tend to bog the machine down a bit for a few minutes these days, could have been one of them.

That would explain the behavior (non-responsive for a while, then perfectly fine, then non-responsive again).
 
Upvote 0
Clarity;1132737; said:
Nope. Hard to say what that would have been. There are some cron jobs that run between 2am and 6am that tend to bog the machine down a bit for a few minutes these days, could have been one of them.
From a shell prompt change to /etc/cron.daily and remove the execute bit from mlocate.cron

[]# chmod -x mlocate.cron

This will disable updatedb, which builds a database so you can search the disk faster with the locate command. It really doesn't need to be running every single night, and it is a HUGE resource hog as it completely ties up the disks while indexing the entire filesystem. An alternative is to move the mlocate.cron job out of cron.daily and put it in cron.weekly instead.

You might also want to check /etc/logrotate.conf and make sure you're not compressing old log files (verify that the 'compress' statement should be commented out).
 
Upvote 0
Dryden;1136052; said:
From a shell prompt change to /etc/cron.daily and remove the execute bit from mlocate.cron

[]# chmod -x mlocate.cron

This will disable updatedb, which builds a database so you can search the disk faster with the locate command. It really doesn't need to be running every single night, and it is a HUGE resource hog as it completely ties up the disks while indexing the entire filesystem. An alternative is to move the mlocate.cron job out of cron.daily and put it in cron.weekly instead.

You might also want to check /etc/logrotate.conf and make sure you're not compressing old log files (verify that the 'compress' statement should be commented out).

Ahhh, so you're not running Solaris, eh? :biggrin:
 
Upvote 0
Had some significant stalls a few minutes ago. Took about 90 seconds for the server to respond and then load the page. It wasn't piecemeal loading the page (little-by-little) but rather sat there and seemed to wait and then decided to load.
 
Upvote 0
Back
Top