One for napster :)

Mick

Administrator
Staff member
Administrator
Premium Member
Joined
Jan 19, 1999
Messages
32,077
Reaction score
8,748
I found the 10:15 bug mate that just lagged the server ;)

it was a backup that was planned for 4am in the morning and gzip the backup... the problem was the time was set wrong on the database server lol.

it was still set to Central American time so 4am in the morning was 10am over here.

anyway I changed the cron to 23:00 hours which will be at 5am in the morning when not many should be effected while it does its job.

I also set a cron to shut down and restart mysql before and after it finishes.

Mickie
 

hackmax

VIP Member
VIP Member
Joined
Feb 11, 2006
Messages
2,155
Reaction score
342
Location
given up.
There's a 10 o'clock in the MORNING aswell?????!!!!!!!!!!
 
TEST
Top