Hello, since the upgrade to 3.2.11p2 I cannot create database users. Users are created in the ispconfig web interface, but they are not created in the mariaDB. Tested on 4 servers: Debian 11, mariadb 10.5.23, ispconfig 3.2.11 (only ispconfig upgrades on this one) Debian 11, mariadb 10.5.23, ispconfig 3.2.11p2 (upgraded from deb 10 and some ispconfig 3.2.x) Debian 12, mariadb 10.11.6, ispconfig 3.2.11p2 (upgraded from deb 10 and some ispconfig 3.2.x) Debian 12, mariadb 10.11.6, ispconfig 3.2.11p2 (fresh install of debian 12 and ispconfig 3.2.11p2) I see no error in /var/log/ispconfig/cron.log. Root mysql password is in /usr/local/ispconfig/server/lib/mysql_clientdb.conf Root user can be authenticated by both unix_socket and mysql_native_password: GRANT ALL PRIVILEGES ON *.* TO `root`@`localhost` IDENTIFIED VIA unix_socket OR mysql_native_password USING '*hash' WITH GRANT OPTION; As debian defaults to auth with unix_socket, I admit that at some time the mysql root was authenticated only by unix_socket, but ispconfig update complained about it so I added password auth to root user. Later I added the password to mysql_clientdb.conf, but it did not help. I tried debug output: - system / server config / Log level = debug - stopped crontab (server.sh) - created database user - ran server.sh manually: 05.04.2024-11:37 - DEBUG [plugins.inc:155] - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'. 05.04.2024-11:37 - DEBUG [server:177] - Found 1 changes, starting update process. 05.04.2024-11:37 - DEBUG [plugins.inc:118] - Calling function 'db_user_insert' from plugin 'mysql_clientdb_plugin' raised by event 'database_user_insert'. 05.04.2024-11:37 - DEBUG [modules.inc:240] - Processed datalog_id 294 05.04.2024-11:37 - DEBUG [server:217] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock finished server.php. - user deleted: - ran server.sh manually: 05.04.2024-11:36 - DEBUG [plugins.inc:155] - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'. 05.04.2024-11:36 - DEBUG [server:177] - Found 2 changes, starting update process. 05.04.2024-11:36 - DEBUG [plugins.inc:118] - Calling function 'db_user_delete' from plugin 'mysql_clientdb_plugin' raised by event 'database_user_delete'. 05.04.2024-11:36 - DEBUG [modules.inc:240] - Processed datalog_id 292 05.04.2024-11:36 - DEBUG [plugins.inc:118] - Calling function 'db_user_delete' from plugin 'mysql_clientdb_plugin' raised by event 'database_user_delete'. 05.04.2024-11:36 - DEBUG [modules.inc:240] - Processed datalog_id 293 05.04.2024-11:36 - DEBUG [server:217] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock finished server.php. Please can you hint me how to get this working, or at least how to get more debug info? It seems to me that it just does not even try to do anything. Best Regards Vladislav Kurz P.S. I wanted to report this via gitlab but I'm still waiting for account approval.
ISPConfig always requires a MySQL root user, and this is set up when you use the auto-installer automatically, or it is set up when you follow the perfect server installation instructions. A database user gets added when you add a database that uses this user, as adding a user that is not able to authenticate to a database makes no sense at all, especially as ISPconfig could not even know on which node to add that user before you create a database for it. So you missed adding a database. Gitlab would be the wrong place anyway, as Gitlab is for bugs reports and feature requests only and not a place to ask for support.
Well, this was supposed to be second read-only user for an existing database. I have already one read-write and one read-only user for that database, and needed another one. As the database page in ispconfig does not allow more users for a database, I would grant the permissions manually, but at least I wanted to have the user in the database users page. Anyway, I take it that this is not a bug but feature...
