Directadmin Cron killing mysql

localrich

Verified User
Joined
Feb 14, 2008
Messages
15
Randomly for the last 60 or so days when the daily directadmin cron runs at 4am mysql dies. I cant log into the server via ssh either :confused: only solution thus far has been to power cycle the server. It will sometimes go 7-8 days sometimes it will do it 2-3 days later.

Looking for insight on what I should change or setup to keep the server going.

THANKS
Rich
 
What does the 4am cron do?

here is the entire cron file


PHP:
* * * * * root /usr/local/directadmin/dataskq
2 0-23/6 * * * root echo 'action=vacation&value=all' >> /usr/local/directadmin/data/task.queue;
#5 5 * * 0 root /sbin/quotaoff -a; /sbin/quotacheck -augm; /sbin/quotaon -a;
10 0 * * * root echo 'action=tally&value=all' >> /usr/local/directadmin/data/task.queue
20 4 1 * * root echo 'action=reset&value=all' >> /usr/local/directadmin/data/task.queue
0 4 * * * root echo 'action=check&value=license' >> /usr/local/directadmin/data/task.queue

Here is the logfile from /var/log/cron when there is an issue

PHP:
Aug 28 04:00:01 da4 crond[23337]: (root) CMD (/usr/local/directadmin/dataskq)
Aug 28 04:00:01 da4 crond[23338]: (root) CMD (/usr/local/nobody_check/nobody_check >/dev/null 2>&1)
Aug 28 04:00:01 da4 crond[23339]: (root) CMD (/usr/local/sitezen/prd/zendaemon checkup)
Aug 28 04:00:01 da4 crond[23340]: (root) CMD (echo 'action=check&value=license' >> /usr/local/directadmin/data/task.queue)
Aug 28 04:00:01 da4 crond[23341]: (root) CMD (/usr/lib/sa/sa1 1 1)
Aug 28 04:01:01 da4 crond[23465]: (root) CMD (run-parts /etc/cron.hourly)
Aug 28 04:01:01 da4 crond[23466]: (root) CMD (/usr/local/directadmin/dataskq)
Aug 28 04:02:01 da4 crond[23516]: (root) CMD (run-parts /etc/cron.daily)
Aug 28 04:02:01 da4 crond[23519]: (root) CMD (/usr/local/directadmin/dataskq)
Aug 28 04:02:01 da4 anacron[23521]: Updated timestamp for job `cron.daily' to 2010-08-28
Aug 28 09:41:07 da4 crond[3395]: (CRON) STARTUP (V5.0)
Aug 28 09:41:07 da4 anacron[3435]: Anacron 2.3 started on 2010-08-28
Aug 28 09:41:07 da4 anacron[3435]: Normal exit (0 jobs run)
Aug 28 09:42:01 da4 crond[3690]: (root) CMD (/usr/local/directadmin/dataskq)
Aug 28 09:43:01 da4 crond[3824]: (root) CMD (/usr/local/directadmin/dataskq)
Aug 28 09:44:01 da4 crond[3897]: (root) CMD (/usr/local/directadmin/dataskq)
Aug 28 09:45:01 da4 crond[3982]: (root) CMD (/usr/local/directadmin/dataskq)

None of the other log files have anything around that time

More server info

PHP:
Processor Name	Intel(R) Xeon(R) CPU E3110 @ 3.00GHz
Vendor ID	GenuineIntel
Processor Speed (MHz)	2000.000
Processor Name	Intel(R) Xeon(R) CPU E3110 @ 3.00GHz
Vendor ID	GenuineIntel
Processor Speed (MHz)	2000.000
Total Memory	3368192 kB
Free Memory	1586160 kB
Total Swap Memory	2104504 kB
Free Swap Memory	2104504 kB
System Uptime	0 Days, 14 Hours and 29 Minutes
Apache 2.2.16	Running
DirectAdmin 1.36.0	Running
Exim 4.72	Running
MySQL 5.0.67	Running
Named 9.3.6	Running
ProFTPd 1.3.3a	Running
sshd	Running
dovecot 1.2.13	Running
Php 5.2.14
 
Basically, it's the /usr/local/sitezen/prd/zendaemon checkup that runs around 4am - so by the looks of it, it could be that, although, I've not used SiteZen Builder before so I'm not sure what checkup does?

Does the CPU load raise when it crashes?
 
Last edited:
Basically, it's the /usr/local/sitezen/prd/zendaemon checkup that runs around 4am - so by the looks of it, it could be that, although, I've not used SiteZen Builder before so I'm not sure what checkup does?

Does the CPU load raise when it crashes?

That checkup runs every 15min all day every day. It's making sure the sitezen deamon is running if it's not it restarts it. I've moved it to an odd minute to see if thats it.

I've never been able to catch it during one of the downtimes but I'm not getting any notices of high load.
 
So really the title should be changed because this does not have anything to do with mysql since the whole server is unreachable.

When it dies you need to get somebody at the data center to look at the screen to see what it says. There could be important information there. You could easily have a hardware problem. It could be an "out of memory" problem.
 
So really the title should be changed because this does not have anything to do with mysql since the whole server is unreachable.

When it dies you need to get somebody at the data center to look at the screen to see what it says. There could be important information there. You could easily have a hardware problem. It could be an "out of memory" problem.

The server is not completely unreachable Just anything tied to mysql and SSH:confused: DA login, email, DB drive webpages etc

The server still serves static htm,html,php pages.
 
The server is not completely unreachable Just anything tied to mysql and SSH:confused: DA login, email, DB drive webpages etc

The server still serves static htm,html,php pages.

So only 99% of the server is unreachable. Again get the DC to look at the screen when it happens.
 
Back
Top