Cron Jobs dissapear?
I have created some Cron jobs to run php scripts, after about a week or so they all get removed from WHM? I have no idea why this keeps happening!
Actually its not WHM but set inside cpanel interaface
-
Hello :) Do you have root access to this system? If so, could you verify if the "crond" service is running? EX: pidof crond
Thank you.0 -
responds 3105 Cron works perfect, just that my jobs are removed randomly? Dedicated server that only I use. 0 -
Removed again ... This is insane :) 0 -
once again all cron jobs are gone? I would make a cron job to add my cron jobs but it will be removed as well! 0 -
Have you considered opening a ticket directly to cPanel Technical Support about this? 0 -
Did you check the logs for anything weird in cron? /var/log/cron
Did you check the logs for unauthorized access?/var/log/secure
ANDlast0 -
looking at the logs the last cron ran, and then this followed Jul 30 03:01:01 server1 crond[18507]: (root) CMD (run-parts /etc/cron.hourly) Jul 30 03:02:01 server1 crond[18581]: (root) CMD (/usr/local/bandmin/bandmin) Jul 30 03:05:01 server1 crond[18959]: (munin) CMD (/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron) Jul 30 03:05:01 server1 crond[18961]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1) Jul 30 03:08:01 server1 crond[19652]: (root) CMD (/usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1) Jul 30 03:10:01 server1 crond[19773]: (root) CMD (/usr/lib64/sa/sa1 1 1) Jul 30 03:10:01 server1 crond[19774]: (munin) CMD (/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron) Jul 30 03:10:01 server1 crond[19776]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1) Jul 30 03:15:01 server1 crond[20530]: (munin) CMD (/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron) Jul 30 03:15:01 server1 crond[20531]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1) Jul 30 03:20:01 server1 crond[21290]: (root) CMD (/usr/lib64/sa/sa1 1 1) Jul 30 03:20:01 server1 crond[21291]: (munin) CMD (/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron) Jul 30 03:20:01 server1 crond[21293]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1) Jul 30 03:23:01 server1 crond[21983]: (root) CMD (/usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1) Jul 30 03:25:01 server1 crond[22065]: (munin) CMD (/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron) Jul 30 03:25:01 server1 crond[22066]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1) Jul 30 03:27:01 server1 crond[22621]: (mailman) CMD (/usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/nightly_gzip) Jul 30 03:30:01 server1 crond[22709]: (munin) CMD (/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron) Jul 30 03:30:01 server1 crond[22711]: (root) CMD (/usr/lib64/sa/sa1 1 1) Jul 30 03:30:01 server1 crond[22712]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1) Jul 30 03:35:01 server1 crond[23714]: (munin) CMD (/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron) Jul 30 03:35:01 server1 crond[23715]: (root) CMD (/usr/bin/test -x /usr/local/cpanel/bin/tail-check && /usr/local/cpanel/b
inside run-parts /etc/cron.hourly is one file#!/bin/bash # is this Xen? if [ -e /proc/xen/capabilities ]; then # xen grep control_d /proc/xen/capabilities >& /dev/null if [ $? -ne 0 ]; then # domU -- do not run on xen PV guest exit 1; fi fi # is this CPU supported? /usr/sbin/mcelog --supported >& /dev/null if [ $? -eq 1 ]; then exit 1; fi # Now safe to run mcelog /usr/sbin/mcelog --ignorenodev --filter >> /var/log/mcelog0 -
Hello :) Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you. 0 -
Hello :) I've been unable to locate a support ticket for this issue. Were you able to open a support ticket or address the issue through another method? I look forward to your response. Thank you. 0
Please sign in to leave a comment.
Comments
9 comments