Hi, I upgraded a slaver server to debian 13 and realized after a while that it doesn't update system information. The cronjob for updating ispconfig data seems to work, but since days it shows the wrong system version and the wrong (old) uptime. I enabled debug for this server, too. I don't see any error messages inside the cron.log or server.log - I tried to run server.sh / cron.sh manually, nothing. I added a print statments into /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_os_version_inc.php - it showed that the file is loaded but the method "onRunJob" is never called. from here I have no idea anymore, this confuses me. Any hints what I can check?
You can not trigger a cron job by running these files manually, as a cron job is triggered only at the time it is scheduled to run. If you want to run a cron job manually, use the cron_debug.php script. The most common reason for such a problem is that the slave node can no longer connect to the master node. Take care that you did not close a firewall on the master that disallows connections from the slave node.
Ok, makes sense. I tried php cron_debug.php --cronjob=100-monitor_os_version.inc.php that worked, eg., it updated the os version in master. so connection seems to be fine. But now: after this the cron is executed for this. But the other ones still not. So I used the same for 100-monitor_sys_usage.inc.php - clean executed with cron_debug.php. And AFTER it is executed in regular cron job, too! This is a bit unexpected for me and I can't evaluate what went wrong. I tried to do an update with --force to re-trigger possible setup steps, but didn't help. Any idea? Tnx Rajko
Might be that the sys_cron table in the dbispconfig database on the slave node is corrupted (check / repair with mysql command or phpmyadmin) or that all jobs are stuck running there, in this case empty the table. And be careful, I mean sys_cron and not cron table.
