Hi, I have an old version of ISPConfig it is 3.1.13, it was working well until I upgraded MySQL(from 5.5.x to 5.7.30) and PHP(from 7.0.x to 7.2.30) on my dedicated server. Everything seem to work fine, except that the flashing red circle for the waiting jobs is now always flashing indefinitely. I tested my ISPConfig installation with the script (wget -q -O htf-common-issues.php "****://gitplace.net/pixcept/ispconfig-tools/raw/stable/htf-common-issues.php" && php -q htf-common-issues.php) and I have not seen any errors in the report (htf_report.txt). I have run the /usr/local/ispconfig/server/server.sh script manually and everything worked, the queue emptied and the flashing circle disappeared ! I did not had to run the script before, ISPConfig was managing the jobs itself without issues, can you figure out the problem?
Note that upgrading mysql or php from the OS's supplied version can and does break things at times. I would set the default php version back, then run 7.2 as an additional php version. I don't know if there are known issues with that mysql version offhand. Beyond that, I would start with upgrading to the latest ISPConfig version, and allow it to reconfigure services and write root's cronjobs (which should run that server.sh). If there is still an issue, there's a field in the database that can be off for what datalog entries have already been run which would be worth checking. I don't remember exactly what needs done (look it up in the forums here), but it has to do with comparing the 'update' number for this server in the server table to the datalog_id in sys_datalog, and updating one to be equal to the other.
I verified my crontab and it contain for ISPConfig : * * * * * /usr/local/ispconfig/server/server.sh 2>&1 | while read line; do echo mercredi 29 avril 2020, 20:35:24 (UTC-0400) "" >> /var/log/ispconfig/cron.log; done * * * * * /usr/local/ispconfig/server/cron.sh 2>&1 | while read line; do echo mercredi 29 avril 2020, 20:35:24 (UTC-0400) "" >> /var/log/ispconfig/cron.log; done Is it not supposed to have : * * * * * /usr/local/ispconfig/server/server.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done * * * * * /usr/local/ispconfig/server/cron.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done Could it be the cause of the CronJob not working?
That is definitely not correct, but I believe it would still run. The parenthesis in "(UTC-0400)" will probably cause an error to be logged along with that 'mercredi 29 avril 2020, 20:35:24' in your /var/log/ispconfig/cron.log, but I don't think it would stop the initial command from running. What shell do you have for /bin/sh? It needs to be bash. What cron daemon do you have? Again, I would download the latest ISPConfig update and install it, letting it reconfigure services and rewrite your cron job. It would be interesting if the cronjob is still "broken" like that afterwards.
Thank you Jesse for your help! You give good advises. After I corrected the CronTab syntax, everything was operating correctly afterward. I really have no idea how come that the Crontab syntax was modified this way, but it seem to have happened after my PHP upgrade! The reason I am not upgrading my ISPConfig, is because I added a lot of new functions to the admin part and I do not want to loose their functionality in the process.
