Hi All I have just migrated my ispconfig 3 server to a Raspberry Pi 4. All seems to be working apart from 43 actions in the pending queue. Any ideas on how to resolve this? I thought it might be a problem with the ns servers not communicating with the main server database. However, when I reinstalled ISPC3, on the ns server it did not give any errors. Just a nudge in the right direction would be a help.
Please see "read before posting", it contains a section about ISPConfig not writing changes to disk. You can find the post here: https://forum.howtoforge.com/threads/please-read-before-posting.58408/
Hi Till, I had waited about 18 hours before contacting you to make sure it was an issue. Also, thank you for the reminder regarding running the server.sh script. I have run the script as the instructions suggest, but I get no faults Code: ~# /usr/local/ispconfig/server/server.sh finished server.php. Nothing has been written to the ispconfig.log file, I mean, it is empty. I have done a search on my syslog and noticed some SSL errors, but I would think this is a different issue to not processing the pending items. Any other suggestions?
I guess you ran it on the wrong server then. Also, the output you posted shows that you missed enabling debug mode.
Hi Till. I ran it on the main server, not the NS servers. I did as the instructions requested, I set the server to Debug under System > System > Server Config, ran "crontab -e" and disabled / commented out "#* * * * * /usr/local/ispconfig/server/server.sh > /dev/null >> /var/log/ispconfig/cron.log" ran it for a few minutes, probably about 10 to 15, I was not actually counting. Then I re-enabled it. and turned off debug mode. Did I miss something or did I run it on the wrong server? I thought I followed as it stated, but maybe I got something wrong.
Double-check that, debug mode is not enabled for the server you ran server.sh. Probably you either changed the debug mode for a different server, or you did not set log level to debug but edited another settings like email reporting level or so. You ran it on the wrong server, as the server you ran it on has no issues.
OK, I don't know what happened but I just ran it again and got the following. Code: /# /usr/local/ispconfig/server/server.sh 02.10.2023-20:38 - DEBUG [plugins.inc:155] - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'. 02.10.2023-20:38 - DEBUG [server:217] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock finished server.php.
Ok, now you have debug mod enabled. The server you ran it on is fine, so you must do the same thing on the other servers to find out which one fails. And do not forget to enable server.sh cronjob again afterwards.
