I updated today to ispconfig 3.2.2. When a user tries to create a database, it appears as created in the panel. But in practice it is not created in Mariadb. In version 3.2.1 it was working normal. Debian environment 10 and 9. Ispconfig 3.2.2. There is no error in the cron.log in the debug. And we noticed that the task of creating the bank in the red ball does not appear next to the research field. But the task is recorded in the sys_datalog logs. I upgraded to 3.2.2 and now I'm starting to regret it. https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5998
It works fine here. Please follow the debug steps: https://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/
Did you reconfigure database permissions on your master server? Are all servers at 3.2.2? Did you do the debug steps on the correct server?
root@servidor:/var/log/ispconfig# /usr/local/ispconfig/server/server.sh 05.01.2021-11:35 - DEBUG - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'. 05.01.2021-11:35 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock finished server.php. Did you configure database permissions on your master servers? Reconfigure Permissions in master database? (yes,no) [no] -> I always left no. Everything was working in 3.2.1. Now in 3.2.2 this situation has appeared. And I've been updating since 3.1 Are all servers at 3.2.2? yes Did you do the debug steps on the correct server? yes
Alright, on the master server, it is better to do so, but it shouldn't break your install. Can you try running the whole upgrade again? What is in the updated column of the server table for the server that has issue? En what is the latest datalog ID? (sys_datalog table)
And are you sure that you added a database too and not just a MySQL user? The MySQL user gets added when you add a database that requires that user and not when you add the user.
How I have been updating my ispconfig since version 3.0. The sys_datalog was large. So I did a truncate. It is currently on datalog_id 48. I made an attempt to create the database and went to datalog_id 49 I've been upgrading from 3.0 to 3.1 and now 3.2 For testing I tried to create an email and it worked normal. Only creating database does not work
Well, there you go. In the server table it is saved which datalog_id was processed last, and that will be a much higher ID. Lower that so it runs all missed actions (for every server). No problem with 3.2.2
