Like other people. I'm getting this error when I attempt to change anything in the Custom php.ini section in the Options tab. The error pops up when I attempt to save the changes. I followed the corrections given in the Priority support area for someone else experiencing this same problem. however, when I execute the SQL: ALTER TABLE `web_domain` ADD `disable_symlinknotowner` enum('n','y') NOT NULL default 'n' AFTER `last_jailkit_hash`; I get the error: #1118 - Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs Any suggestion? Thanks Norm
Which ISPConfig version do you use on which operating system and which MariaDB version does your server use?
The server uses the latest patch level of ISPConfig (3.2.12p1) running on CentOS 7, with MariaDB 10.6.18.
Hi, I see the same error message as of today. Running Debian 10, with php8.2 and isp version 3.2.12p1.
Seems as if database changes in the last ISPConfig update could not be applied. It is the SQL change file install/sql/incremental/upd_0100.sql. Maybe you change the MySQL root password and did not set the new password in /usr/local/ispconfig/server/lib/mysql_clientdb.conf file?
The ALTER TABLE-statement from above fixed the problem for me to just recently. Problem was: after Upating the master to 3.3.1p1 I had problems with domain alias config update jobs on a slave still running 3.2.8p1. With the statement above it worked, the jobs finished then. BUT: Do such "hardcoded" changes break the update processes in the future? In my opinion a later ALTER TABLE statement would this field to be non-existent yet and could fail...
Do not manually alter the database; just take care to update all nodes to the same ISPConfig version. You can not run different versions of ISPConfig in a multiserver system.
I really try to do it the right way now. But that was an old installation, and well that was a suggestion on this site, and it worked. I just wondered what might be the consequence. We'll see... Thank you anyway!
