mysql error number: 1053 / server or vB?

[dsotmoon]

for a a week or two now I have been getting vB database errors like the one below every single night at the exact same time 12:00AM, then I get sql cant connect errors for approx 8 minutes, then exim fails and restarts and everything is back to normal for another 24 hours, its just an 8 minute window every night, I havent changed or added anything in months, yes its 3.0.06 and its hacked so I know its not supported, I am waiting to upgrade with at least 3.5.0 Stable, anyway, what could cause this problem everynight at the same time? I did email my server provider and here is their reply, I couldnt understand if it was/is/could be a server issue or a vB issue...

We have checked the issue with the mysql error you are receiving. The reason for the error can be due to a couple of reasond which we have checked.
One of the reasons which is a permission issue with the user connecting to the forum database fullsize_fsbforums is fixed by granting full privileges to the user. The settings in the config.php is also correct for the database to work properly.
We have also configured the mysql configuration file regarding the maximum connections and buffer to the mysql databases in the server .

here is the error...

Database error in vBulletin 3.0.6:

Invalid SQL: SELECT COUNT(threadid) AS total FROM post WHERE dateline >= 1123041600
mysql error: Server shutdown in progress

mysql error number: 1053

Date: Thursday 04th of August 2005 12:00:06 AM
Script: http://www.fullsizebronco.com/forum/...p?&rand=334285
Referer: http://fullsizebronco.com/forum/foru...4&daysprune=-1

thanks in advance for any help!

[Steve Machol]

The MySQL server is shutting down and restarting. This is probably done by a cron job on the server. This is not a good sign and there is no reason for your host to do this. This can and will cause database corruption inn MySQL is shutdown when the db is being written to. I suggest contacting your host about this.

[dsotmoon]

its a dedicated server so the host shouldnt have any crons running, using crontab -e this is a list of things that run...

root@srv01 [~]# crontab -e



12 5 * * * /scripts/upcp
0 1 * * * /scripts/cpbackup
*/15 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1
0 6 * * * /scripts/exim_tidydb > /dev/null 2>&1
2,58 * * * * /usr/local/bandmin/bandmin
0 0 * * * /usr/local/bandmin/ipaddrmap
*/5 * * * * /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1

does anything jump out there?

[Steve Machol]

Nothing stands out. However:

mysql error: Server shutdown in progress

And this:

for a a week or two now I have been getting vB database errors like the one below every single night at the exact same time 12:00AM

Do indicate the MySQL server is being shut down at the same time every night. Whatever is causing this needs to be stopped.

[dsotmoon]

here is the latest response from support

We have checked the issue in detail and found that there are no server settings or cron jobs set to restart mysql server automatically at the particular time as you mentioned. We are monitoring the server and mysql sever is running fine without any problems.

does it have anything to do with vB crons since it was in the error?

http://www.fullsizebronco.com/forum/...p?&rand=334285

[Steve Machol]

vB cannot restart the MySQL server. This has to be done on the server level by either a script with root permissions or manually by someone with root permissions. Since this happens at exactly the same time everyday, it is almost certainly an automated process. Frankly I'm rather surprised that your host cannot track this down.

[dsotmoon]

Frankly I'm rather surprised that your host cannot track this down.

here is their latest reply...

We had a look into the issue for you. MySQL service is running fine in the server. We also couldn't find any cron jobs set for shutting down the service. We have hardened your /tmp directory as a preventive measure against executing malicious scripts from within the /tmp directory. Following is a list of cron jobs currently set server wide.

======================================
12 5 * * * /scripts/upcp
0 1 * * * /scripts/cpbackup
*/15 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1
0 6 * * * /scripts/exim_tidydb > /dev/null 2>&1
2,58 * * * * /usr/local/bandmin/bandmin
0 0 * * * /usr/local/bandmin/ipaddrmap
*/5 * * * * /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1

and then 5 minues after that email I start getting NEW vB errors...

Database error in vBulletin :

Invalid SQL:
SELECT title, data
FROM datastore
WHERE title IN ('options', 'cron', 'forumcache', 'usergroupcache', 'stylecache', 'adv_modules', 'adv_portal_opts', 'attachmentcache', 'bbcodecache', 'birthdaycache', 'eventcache', 'iconcache', 'maxloggedin', 'smiliecache', 'userstats')

mysql error: Got error 127 from table handler

mysql error number: 1030

Date: Sunday 07th of August 2005 05:05:20 AM
Script: http://fullsizebronco.com/

Database error in vBulletin 3.0.6:

Invalid SQL:
SELECT COUNT(*) AS threads,
SUM(IF(lastpost>=1123375793 AND open<>10,1,0)) AS newthread
FROM thread AS thread
LEFT JOIN deletionlog AS deletionlog ON(thread.threadid = deletionlog.primaryid AND type = 'thread')
WHERE forumid = 34
AND sticky = 0
AND visible = 1

AND lastpost >= 1091876864

AND deletionlog.primaryid IS NULL

mysql error: Incorrect key file for table: 'thread'. Try to repair it

mysql error number: 1034

Date: Sunday 07th of August 2005 07:07:44 AM

Database error in vBulletin 3.0.6:

Invalid SQL:
SELECT threadid
FROM thread AS thread
LEFT JOIN deletionlog AS deletionlog ON(thread.threadid = deletionlog.primaryid AND type = 'thread')
WHERE forumid = 29
AND sticky = 0
AND visible = 1



AND deletionlog.primaryid IS NULL
ORDER BY sticky DESC, thread.title DESC
LIMIT 0, 24

mysql error: Got error 134 from table handler

mysql error number: 1030

Date: Sunday 07th of August 2005 07:14:55 AM
Script: http://www.fullsizebronco.com/forum/...c&daysprune=-1

and emails from members...

Keep getting this message when I post...

Warning: mysql_query(): Unable to save result set in /includes/db_mysql.php on line 212

Its 4:08AM Central time here

what can I do now?

[dsotmoon]

looks like repairing the tables took care of the problems above, still confused about the SQL problem though

[Steve Machol]

MySQL error: 127 = Record-file is crashed
MySQL error: 134 = Record was already deleted (or record file crashed)

Which specific 'SQL problem' do you mean?

[Zachery]

Its more than possible you have your WHM Settings to auto upgrade your cPanel and WHM versions ( VERY BAD IDEA!!!!!!!) and you got that error while the server was upgrading MySQL.

[dsotmoon]

MySQL error: 127 = Record-file is crashed
MySQL error: 134 = Record was already deleted (or record file crashed)

Which specific 'SQL problem' do you mean?

I was talking about the original 12:00am sql shutdown problem, the host doesnt seem to think it exists from their end even though I am getting the vB errors

We had a look into the issue for you. MySQL service is running fine in the server. We also couldn't find any cron jobs set for shutting down the service. We have hardened your /tmp directory as a preventive measure against executing malicious scripts from within the /tmp directory. Following is a list of cron jobs currently set server wide.

======================================
12 5 * * * /scripts/upcp
0 1 * * * /scripts/cpbackup
*/15 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1
0 6 * * * /scripts/exim_tidydb > /dev/null 2>&1
2,58 * * * * /usr/local/bandmin/bandmin
0 0 * * * /usr/local/bandmin/ipaddrmap
*/5 * * * * /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1

[dsotmoon]

Its more than possible you have your WHM Settings to auto upgrade your cPanel and WHM versions ( VERY BAD IDEA!!!!!!!) and you got that error while the server was upgrading MySQL.

it is set up to update automaticaly to current tree, the only thing is this is a problem that started just recently, I will change to manual update and see if that helps, thanks for everyones help so far btw

[George L]

check what cronjob /scripts/cpbackup does as well

[dsotmoon]

check what cronjob /scripts/cpbackup does as well

how do i do that? ls into that file? sorry i am linux dumb

[dsotmoon]

ok, here is another twist, when this goes down from 12am to approx 12:08am (tonight it only lasted less than a minute), it kicks off all my vB users and emails me a database error that it cant connect to mySQL, however in the exact same time I get these errors I am able, along with other users, to post on a IPB forum i have running on the same server? ? ? ? ? ? ?

all this on top of my host saying there is nothing shutting down SQL on the server, any other ideas or suggestions?