Cron <root@server> /root/bin/sys-snap --cron
I always get that email, subject Cron /root/bin/sys-snap --cron.
Body:
/bin/sh: /root/bin/sys-snap: No such file or directory
I did a search and could not find anything relating to it ?
-
How do i turn it off since its not installed on my server. I did a search on the crontab and did not find anything relating to it. Please help. Thanks 0 -
There should be a cron entry for it though. It's being run as a cron job you can see that in the notice you receive. What's the output of the following: crontab -u root -l
0 -
Nothing below about it. SHELL="/bin/bash" 30 1 * * * /usr/local/cpanel/scripts/exim_tidydb > /dev/null 2>&1 SHELL="/bin/bash" 48 0 * * * /usr/local/cpanel/scripts/optimize_eximstats > /dev/null 2>&1 SHELL="/bin/bash" 28 13 * * * /etc/upcp_control SHELL="/bin/bash" 35 18 * * * /usr/local/cpanel/scripts/cpbackup SHELL="/bin/bash" 26 * * * * /usr/bin/test -x /usr/local/cpanel/bin/tail-check && /usr/local/cpanel/bin/tail-check SHELL="/bin/bash" 26 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_mailman_cache && /usr/local/cpanel/scripts/update_mailman_cache SHELL="/bin/bash" 52 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_db_cache && /usr/local/cpanel/scripts/update_db_cache SHELL="/bin/bash" 19 */2 * * * /usr/local/cpanel/bin/mysqluserstore > /dev/null 2>&1 SHELL="/bin/bash" 42 */2 * * * /usr/local/cpanel/bin/dbindex > /dev/null 2>&1 SHELL="/bin/bash" 10 */6 * * * /usr/local/cpanel/scripts/autorepair recoverymgmt > /dev/null 2>&1 SHELL="/bin/bash" */5 * * * * /usr/local/cpanel/scripts/dcpumon-wrapper > /dev/null 2>&1 SHELL="/bin/bash" 31 10 * * * /usr/local/cpanel/whostmgr/docroot/cgi/cpaddons_report.pl --notify SHELL="/bin/bash" 24,39,54,9 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1 SHELL="/bin/bash" 0 2 * * * /usr/local/cpanel/bin/backup SHELL="/bin/bash" @reboot /usr/local/cpanel/bin/onboot_handler 0 * * * * /usr/sbin/tmpwatch -am 4 /tmp 5,20,35,50 * * * * /usr/local/cpanel/scripts/eximstats_spam_check 2>&1 0 */2 * * * /usr/local/cpanel/scripts/shrink_modsec_ip_database -x 2>&1 15 19 * * * /usr/local/cpanel/3rdparty/quickinstall/scripts/getCache.pl #28 13 * * 5 (/usr/local/cpanel/scripts/fix-cpanel-perl; /usr/local/cpanel/scripts/upcp --cron > /dev/null) 22 22 * * 7 /usr/local/cpanel/scripts/send_api_notifications > /dev/null 2>&1 09,39 * * * * /usr/local/cpanel/scripts/clean_user_php_sessions > /dev/null 2>&1
0 -
Hello, Thanks for that, can you run the following and let me know what the output is? grep sys-snap /var/spool/cron/*
0 -
Nothing happens. 0 -
Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks! 0 -
I forgot my password and the reset password seems to have issues. Since my email is already active :/ Ill try again tomorrow 0 -
What is the issue with reset password you're experiencing? 0 -
Your Support Ticket ID is: 93479486 0 -
Oh fantastic you were able to open a support ticket, can you let me know how/what changed? 0 -
I always get that email, subject Cron /root/bin/sys-snap --cron. Body: /bin/sh: /root/bin/sys-snap: No such file or directory I did a search and could not find anything relating to it ?
I have exactly the same problem and I've searched for the trigger in crontab, etc, can't find it.0 -
Do you have any record of it when running something like: grep sys-snap /var/spool/cron/*
orgrep -ir snap /var/spool/cron/
0 -
nope, both greps produce no results 0 -
What is the output of the following: ls -lah /var/spool/cron/
0 -
drwx------. 2 root root 4096 Mar 2 22:19 . drwxr-xr-x. 13 root root 4096 Apr 17 2013 .. -rw------- 1 beautyev beautyev 1368 Mar 11 2019 beautyev -rw------- 1 root root 1546 Mar 2 22:19 root -rw-r--r-- 1 root root 1179 Aug 31 2015 root-1441087419 -rw-r--r-- 1 root root 1220 Jul 20 2016 root-1469011960 -rw-r--r-- 1 root root 1141 Aug 4 2016 root-1470298691
0 -
What is in those root crontabs? 0 -
Same problem here, and the answer to your last question about the content of the crontabs is, "the string 'snap' is not in any of them." I've executed "perl /root/sys-snap.pl --stop" but of course I get the error "no such file." Should I install SNAP so I can stop the cron? Do you need to open a ticket? The content of /var/spool/cron/root is: 23 15 * * * /usr/local/cpanel/scripts/exim_tidydb > /dev/null 2>&1 48 14 * * * /usr/local/cpanel/scripts/optimize_eximstats > /dev/null 2>&1 #5,35 * * * * /usr/local/bandmin/bandmin #27 0 * * * /usr/local/bandmin/ipaddrmap #3 21 * * 1 (/usr/local/cpanel/scripts/fix-cpanel-perl; /usr/local/cpanel/scripts/upcp --cron > /dev/null) 3 21 * * * (/usr/local/cpanel/scripts/fix-cpanel-perl; /etc/upcp_control) 27 * * * * /usr/bin/test -x /usr/local/cpanel/bin/tail-check && /usr/local/cpanel/bin/tail-check 6 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_mailman_cache && /usr/local/cpanel/scripts/update_mailman_cache 38 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_db_cache && /usr/local/cpanel/scripts/update_db_cache 22 */2 * * * /usr/local/cpanel/bin/mysqluserstore >/dev/null 2>&1 32 */2 * * * /usr/local/cpanel/bin/dbindex >/dev/null 2>&1 8 */6 * * * /usr/local/cpanel/scripts/autorepair recoverymgmt >/dev/null 2>&1 */5 * * * * /usr/local/cpanel/scripts/dcpumon-wrapper >/dev/null 2>&1 43 0 * * * /usr/local/cpanel/whostmgr/docroot/cgi/cpaddons_report.pl --notify 8,23,38,53 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1 0 2 * * * /usr/local/cpanel/bin/backup 5,20,35,50 * * * * /usr/local/cpanel/scripts/eximstats_spam_check 2>&1 0 */2 * * * /usr/local/cpanel/scripts/shrink_modsec_ip_database -x 2>&1 @reboot /usr/local/cpanel/bin/onboot_handler 12 21 * * * /usr/local/cpanel/3rdparty/quickinstall/scripts/getCache.pl 55 2 * * * /usr/local/cpanel/3rdparty/bin/freshclam --quiet --no-warnings 22 22 * * 7 /usr/local/cpanel/scripts/send_api_notifications > /dev/null 2>&1 09,39 * * * * /usr/local/cpanel/scripts/clean_user_php_sessions > /dev/null 2>&1 0 -
@eLIANT - it might be best to open a ticket for that so we can check the cron system and get that resolved. 0
Please sign in to leave a comment.
Comments
19 comments