Cron's doesn't start automatically

aaP_info34

Hello so we are facing problem with newest aa panel version that our crons doesn't start automatically on ubuntu VM with newest aapanel and we have to manually execute them. Anyone else have this problem or have a solution to fix it? Tried to restart server, tried to update to beta, tried to fix panel but nothing changed.

Last execution time 10:24:50 and now we have 10:27:30 and nothing changed (did not executed automatically).

`cron.service - Regular background program processing daemon
Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2022-06-14 10:14:53 EEST; 13min ago
Docs: man:cron(8)
Main PID: 123157 (cron)
Tasks: 1 (limit: 6861)
Memory: 1.3M
CGroup: /system.slice/cron.service
└─123157 /usr/sbin/cron -f

Jun 14 10:14:53 .net systemd[1]: Started Regular background program processing daemon.
Jun 14 10:14:53.net cron[123157]: (CRON) INFO (pidfile fd = 3)
Jun 14 10:14:53.net cron[123157]: Error: bad day-of-month; while reading crontab for user root
Jun 14 10:14:53.net cron[123157]: (root) ERROR (Syntax error, this crontab file will be ignored)
Jun 14 10:14:53.net cron[123157]: (CRON) INFO (Skipping @reboot jobs -- not system startup)
Jun 14 10:17:01.net CRON[124063]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 14 10:17:01.net CRON[124070]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jun 14 10:17:01.net CRON[124063]: pam_unix(cron:session): session closed for user root
`

root@aa:~# cat /www/server/cron/3ab48c27ec99cb9787749c362afae517 #!/bin/bash PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:~/bin export PATH /www/server/panel/pyenv/bin/python -u /www/server/panel/class/acme_v2.py --renew=1 echo "----------------------------------------------------------------------------" endDate=date +"%Y-%m-%d %H:%M:%S"echo "★[$endDate] Successful" echo "----------------------------------------------------------------------------" root@aa2754:~#

aaPanel_Kern

aaP_info34
Hello, check whether the Log of "Renew Let's Encrypt Certificate" is running on the cron interface
At the same time, "Renew Let's Encrypt Certificate" runs by default at 0:10 am.

It is recommended that you check whether the prompt is caused by other tasks: around 10:14
crontab -l

aaP_info34

aaPanel_Kern Hello! last cron for lets encrypt was 2022-06-13 20:24:32
we have around 20+ crons added but none is auto starting at needed time, every time we need to launch them manually

aaP_info34

aaPanel_Kern

root@aa:~# crontab -l
10 0 * * * /www/server/cron/3ab48c27ec99cb9787749c362afae517 >> /www/server/cron/3ab48c27ec99cb9787749c362afae517.log 2>&1
42 23 * * * /www/server/cron/5251469e6fb96af1f9453b6c84a0ab58 >> /www/server/cron/5251469e6fb96af1f9453b6c84a0ab58.log 2>&1
40 5 * * * /www/server/cron/ffc5844818b5299c43d1d0c80c9ed91a >> /www/server/cron/ffc5844818b5299c43d1d0c80c9ed91a.log 2>&1
35 5 * * * /www/server/cron/57ad126c264d30f5d3fae72fd9325c15 >> /www/server/cron/57ad126c264d30f5d3fae72fd9325c15.log 2>&1
30 5 * * * /www/server/cron/426ac9ef1b37e139d0ec9d72fa336d16 >> /www/server/cron/426ac9ef1b37e139d0ec9d72fa336d16.log 2>&1
15 5 * * * /www/server/cron/54528eade621b30f165b7e7d03f6ef19 >> /www/server/cron/54528eade621b30f165b7e7d03f6ef19.log 2>&1
25 5 * * * /www/server/cron/c4cf83fe6ea6e54ae95b759568df3922 >> /www/server/cron/c4cf83fe6ea6e54ae95b759568df3922.log 2>&1
20 5 * * * /www/server/cron/fdaf8541bffede959b5f7aa3f93fed81 >> /www/server/cron/fdaf8541bffede959b5f7aa3f93fed81.log 2>&1
15 3 * * * /www/server/cron/3609a246e8567814cc576f4d30ffade2 >> /www/server/cron/3609a246e8567814cc576f4d30ffade2.log 2>&1
16 8 * * * /www/server/cron/f80055072c71bbace7814d78f8410331 >> /www/server/cron/f80055072c71bbace7814d78f8410331.log 2>&1
35 23 * * * /www/server/cron/f1db250fc5fbf76c7270eb788172065a >> /www/server/cron/f1db250fc5fbf76c7270eb788172065a.log 2>&1
30 23 * * * /www/server/cron/a3ac35bc6dcf821ecea8f3127130051e >> /www/server/cron/a3ac35bc6dcf821ecea8f3127130051e.log 2>&1
0 17 * * * /www/server/cron/b3a6ac5429c43709b79adfc0ee846c1d >> /www/server/cron/b3a6ac5429c43709b79adfc0ee846c1d.log 2>&1
30 18 * * * /www/server/cron/ffe9519d7820bd7b4986dd9a459d9486 >> /www/server/cron/ffe9519d7820bd7b4986dd9a459d9486.log 2>&1
40 2 * * * /www/server/cron/51ff4a86832d09265411452c620599a1 >> /www/server/cron/51ff4a86832d09265411452c620599a1.log 2>&1
40 13 * * * /www/server/cron/73840b24956d6bdf5bb4b29a56b13ee7 >> /www/server/cron/73840b24956d6bdf5bb4b29a56b13ee7.log 2>&1
*/2 * * * * /www/server/cron/96d7668cf4763e37792a6e3ac83f164e >> /www/server/cron/96d7668cf4763e37792a6e3ac83f164e.log 2>&1
03 20 * * * /www/server/cron/855409317716defecd003d33012a5306 >> /www/server/cron/855409317716defecd003d33012a5306.log 2>&1
*/2 * * * * /www/server/cron/595df5d3442a3d224b74474719caf12d >> /www/server/cron/595df5d3442a3d224b74474719caf12d.log 2>&1
45 1 * * * /www/server/cron/826ca2feebb37273531509c49a686fd4 >> /www/server/cron/826ca2feebb37273531509c49a686fd4.log 2>&1
33 1 * * * /www/server/cron/75312ea894a49fa990b2c5d3ff8e6849 >> /www/server/cron/75312ea894a49fa990b2c5d3ff8e6849.log 2>&1
0 3 * * * /www/server/cron/ee9b1d175d1dc0140d3c6364cfc114da >> /www/server/cron/ee9b1d175d1dc0140d3c6364cfc114da.log 2>&1
0 14 * * * /www/server/cron/46d4a5dcdbfa5b314b4f35704d72aaa1 >> /www/server/cron/46d4a5dcdbfa5b314b4f35704d72aaa1.log 2>&1
13 13 * * * /www/server/cron/2e8ff2ebf8dc2b436d4a040eea810eaa >> /www/server/cron/2e8ff2ebf8dc2b436d4a040eea810eaa.log 2>&1
00 12 * * * /www/server/cron/546cfc71d9f031f9334efb7a02758f7d >> /www/server/cron/546cfc71d9f031f9334efb7a02758f7d.log 2>&1
00 15 * * * /www/server/cron/a874d2896ecf460b56b82dd602c8c7ad >> /www/server/cron/a874d2896ecf460b56b82dd602c8c7ad.log 2>&1
00 16 * * * /www/server/cron/47a026c76a589284fd3e6500cb258cb3 >> /www/server/cron/47a026c76a589284fd3e6500cb258cb3.log 2>&1
*/2 * * * * /www/server/cron/b1570263c15701f20a24d6a3d207a589 >> /www/server/cron/b1570263c15701f20a24d6a3d207a589.log 2>&1
*/2 * * * * /www/server/cron/6928b45a4430acf79b6d6d1d948de49d >> /www/server/cron/6928b45a4430acf79b6d6d1d948de49d.log 2>&1
30 3 27 * * /www/server/cron/a919a0734a42453d11d8fb0281dcae57 >> /www/server/cron/a919a0734a42453d11d8fb0281dcae57.log 2>&1
30 1 * * 1 /www/server/cron/0db473def81878cc8f463fcf5fa9be30 >> /www/server/cron/0db473def81878cc8f463fcf5fa9be30.log 2>&1
30 1 25 * * /www/server/cron/bbe557059b2d2f6725e410a52ea8ad14 >> /www/server/cron/bbe557059b2d2f6725e410a52ea8ad14.log 2>&1
01 22 * * * /www/server/cron/3d6bc67a7d70ea2b716f3e2b7ce55ff7 >> /www/server/cron/3d6bc67a7d70ea2b716f3e2b7ce55ff7.log 2>&1
30 2 * * * /www/server/cron/db19b7c9a91385a6adabf9c937844a1b >> /www/server/cron/db19b7c9a91385a6adabf9c937844a1b.log 2>&1
00 5 * * * /www/server/cron/ed4a3be858ab5569105bf797ac10e300 >> /www/server/cron/ed4a3be858ab5569105bf797ac10e300.log 2>&1
30 */10 * * * /www/server/cron/70c20f5fb17841166deed3458e900ac8 >> /www/server/cron/70c20f5fb17841166deed3458e900ac8.log 2>&1
0 */10 * * * /www/server/cron/96fc544e86ba3949a2222fc25345ab09 >> /www/server/cron/96fc544e86ba3949a2222fc25345ab09.log 2>&1
0 23 * * * /www/server/cron/8f1be86a7e012c93c5f9582e16b931bf >> /www/server/cron/8f1be86a7e012c93c5f9582e16b931bf.log 2>&1
30 1 * * * /www/server/cron/a7de7f8a27ec61bacd3669ce6dcb6d89 >> /www/server/cron/a7de7f8a27ec61bacd3669ce6dcb6d89.log 2>&1
30 2 * * * /www/server/cron/58a4fc797641f55519d5b78b808d1238 >> /www/server/cron/58a4fc797641f55519d5b78b808d1238.log 2>&1
30 1 1 * * /www/server/cron/54a01de4a675289b671baaac2432a5ee >> /www/server/cron/54a01de4a675289b671baaac2432a5ee.log 2>&1
30 1 * * * /www/server/cron/0f8bb35ecea951d05e494f6b0bfb5341 >> /www/server/cron/0f8bb35ecea951d05e494f6b0bfb5341.log 2>&1
30 3 * * * /www/server/cron/5176418aea07285d5f7422b1350a7eee >> /www/server/cron/5176418aea07285d5f7422b1350a7eee.log 2>&1
30 2 * * * /www/server/cron/8c71c24bdb76e1f3a3fa363d63d6a611 >> /www/server/cron/8c71c24bdb76e1f3a3fa363d63d6a611.log 2>&1
30 5 3 * * /www/server/cron/ed43f4e0ab06c105c66d37f0b93629d6 >> /www/server/cron/ed43f4e0ab06c105c66d37f0b93629d6.log 2>&1
30 2 * * * /www/server/cron/f6bf2a6cbd14c2b4a393d383c288e749 >> /www/server/cron/f6bf2a6cbd14c2b4a393d383c288e749.log 2>&1
30 1 365 * * /www/server/cron/aa125ff5ec231b1662f8e3746da66dd9 >> /www/server/cron/aa125ff5ec231b1662f8e3746da66dd9.log 2>&1
30 1 365 * * /www/server/cron/f0c2e5e8af8c311a7fc71db8f702e316 >> /www/server/cron/f0c2e5e8af8c311a7fc71db8f702e316.log 2>&1
30 2 365 * * /www/server/cron/d4876e51ef6a8a1e60b247d7ea7126b5 >> /www/server/cron/d4876e51ef6a8a1e60b247d7ea7126b5.log 2>&1
0 */12 * * * /www/server/cron/41dbdda0cceafcb574ca46d5e11a31ee >> /www/server/cron/41dbdda0cceafcb574ca46d5e11a31ee.log 2>&1
*/60 * * * * /www/server/cron/60a9cf7461c9b4265af0c94325b6ab14 >> /www/server/cron/60a9cf7461c9b4265af0c94325b6ab14.log 2>&1
30 4 * * * /www/server/cron/82a05d68b83cd6bbe68627826768c3ca >> /www/server/cron/82a05d68b83cd6bbe68627826768c3ca.log 2>&1
0 */12 * * * /www/server/cron/fbf3a9f4e029861582dc5fe80d9500d3 >> /www/server/cron/fbf3a9f4e029861582dc5fe80d9500d3.log 2>&1
30 2 * * * /www/server/cron/a976fc27f9f0d028108666199cf95edc >> /www/server/cron/a976fc27f9f0d028108666199cf95edc.log 2>&1
53 16 * * * /www/server/cron/f3a0381fef638b9e7ebd5ee2ecc9b34e >> /www/server/cron/f3a0381fef638b9e7ebd5ee2ecc9b34e.log 2>&1
*/1 * * * * /www/server/cron/3661da67fd6d0f2b140ff17ee3f3e291 >> /www/server/cron/3661da67fd6d0f2b140ff17ee3f3e291.log 2>&1

aaPanel_Kern

aaP_info34
Try adding a test task, run every minute, and wait for it to run, check the logs if it works?
echo "test"

aaP_info34

aaPanel_Kern
test task added every 1 minute, but nothing goes on.

/www/server/cron/3661da67fd6d0f2b140ff17ee3f3e291: line 4: asdasd: command not found

★[2022-06-14 10:15:06] Successful

/www/server/cron/3661da67fd6d0f2b140ff17ee3f3e291: line 4: asdasd: command not found

★[2022-06-14 10:24:50] Successful

aaPanel_Kern

aaP_info34
Isn't this what works?

aaP_info34

aaPanel_Kern

it has to work automatically every 1min, but it works only if i manually launch it.

aaPanel_Kern

aaP_info34
Please don't run it manually. Makes you wait for it to run. .
Try restarting cron, and then observe whether the test task runs automatically.
debian/ubuntu:
systemctl restart cron
Cenots:
systemctl restart crond

aaP_info34

aaPanel_Kern

1) restarted cron
2) created new cron test2 n minutes 1 echo test
3) log: Task logs are empty!

aaP_info34

aaPanel_Kern

5 minutes passed still no cron job executed

aaPanel_Kern

aaP_info34
Make sure there are no settings errors?
Also check cron logs
tail /var/log/cron.log
If the file does not exist, enable cron logging:

cp /etc/rsyslog.conf /etc/rsyslog.conf_bak
vim /etc/rsyslog.conf

#cron.* /var/log/cron.log
Remove the # sign, save the file, and restart rsyslog
/etc/init.d/rsyslog restart

aaP_info34

aaPanel_Kern Done everything as you have mentioned, nothing changed. tail shows nothing.

aaPanel_Kern

aaP_info34
Hi, can you give us your aapanel information? The server makes a snapshot backup first, if possible, please send it to kern@aapanel.com.
It is recommended to fill in the following
Post link:
SSH account password and port:
aapanel login link address and account password:

aaP_info34

aaPanel_Kern sended details.

aaP_alimehran200

dear sir. i want to auto restart MySQL after every two hours. can you please write me shell scripts, here what i should write.

thanks

aaP_alimehran200

/etc/init.d/mysqld restart

i found this solution using centos..
please ignore my question
thanks