My DirectAdmin Server have 1 account and after installation CloudLinux , All cronjobs Stopped!

[1saeed]

Hello Dear Friend

I installed Directadmin 2 months ago moved my WHMCS system to 1 hosting account and set daily task cronjobs and worked fine.

I installed CloudLinux on this server (CentOS 7 ) that installed DA and WHMCS and all this CloudLinux is installed and working correctly!

but after cloudLinux installation, my all cronjobs stopped and did not work!

on the previous server, I had this issue and I Didn't For what not working cron jobs I migrated to a new VPS, and this cron issue was fixed! but after installing Cloudlinux i faced a cronjob-stopping issue! I know on the previous Server too I have this issue because I installed Cloudlinux and on this server that installed Cloudlinux like the previous server, all cronjobs stopped!

but when I run this command from SSH, cronjob from root on SSH working by level by level completed :

command running fine on SSH is :

php -q /home/kando/domains/demo.com/public_html/client/crons/cron.php --force -vvv

but this cron even when added on the direct admin panel not working!

why does this issue occur? why did Cloudlinux installation stop cronjob activity on the panel?

how can fix this issue?

thanks

 

[Richard G]

why did Cloudlinux installation stop cronjob activity on the panel?

You might want to ask that at Cloudlinux. It's their installation which stops te cronjobs as far as I read it here.

Fix it... well... did you check if the cron service was running already? I presume yes, but just asking to be sure:
service crond status

 

[1saeed]

I run this command on SSH :

[root@sv00 ~]# service crond status

and result :

Redirecting to /bin/systemctl status crond.service ● crond.service - Command Scheduler Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-08-31 03:50:16 +0330; 1 day 21h ago Main PID: 4778 (crond) CGroup: /system.slice/crond.service └─4778 /usr/sbin/crond -n Aug 31 03:50:16 sv00.kandohost.com systemd[1]: Started Command Scheduler. Aug 31 03:50:16 sv00.kandohost.com crond[4778]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 17% if used.) Aug 31 03:50:16 sv00.kandohost.com crond[4778]: (CRON) INFO (running with inotify support) Aug 31 03:59:01 sv00.kandohost.com crond[4778]: (*system*) RELOAD (/etc/cron.d/lvemanager-selector) Aug 31 03:59:01 sv00.kandohost.com crond[4778]: (*system*) RELOAD (/etc/cron.d/lvemanager-cron) Aug 31 04:23:01 sv00.kandohost.com crond[4778]: (kando) RELOAD (/var/spool/cron/kando) Aug 31 04:33:01 sv00.kandohost.com crond[4778]: (kando) RELOAD (/var/spool/cron/kando) Aug 31 04:38:01 sv00.kandohost.com crond[4778]: (kando) RELOAD (/var/spool/cron/kando)


what means?
if running, why stop my added cron codes on directadmin host panel?

 

[Richard G]

Check your cron log, normally to be found in your /var/log directory, if that points to errors.

Next to that, just for testing sake, change the cronjob from php -q to the full path of the php version the users chooses like:
* 1 * * * /usr/local/php80/bin/php -q /home/kando/domains/demo.com/public_html/client/crons/cron.php
or add those -vvv if required, I don't think you need the --force.
Change the * 1 * * * to your own requirements ofcouse.

It might be that it has to be different in Cloudlinux, I don't know because I don't use Cloudlinux.