madmax

The "SET GLOBAL" variables used in the .sql update scripts were working prior to 5.5 but MySQL has made a change that they now need to be set in My.cnf This has been tested and verified by both myself and @H0zen. Making this entry so we can get a push at getting this changed or whatever changes are needed. It should be noted that only one .sql file in all of the updates actually need these lines added and I feel they are being overused. SET GLOBAL Statements SET GLOBAL net_read_timeout=30; SET GLOBAL net_write_timeout=60; SET GLOBAL net_buffer_length=1000000; SET GLOBAL max_allowed_packet=1000000000; SET GLOBAL connect_timeout=10000000; MariaDB This issue is very obvious on MariaDB since it actually rejects the SET GLOBAL (i can only hope MySQL implement this). MariaDB sends back an error and fails the script from running any further. MySQL silently fails and continues to run the script. Currently to get updates to apply to MairaDB based server you have to remove the lines entirely from the top of the .sql files. My Recommendation: For updates that need the variables added we should add a special update step that forces the user to either make the change in My.cnf or enter the changes in the server console which would stay in effect until the server is restarted. A simple step in the scripts that need these settings to check what the server value is, is what we really need. Now awaiting feedback of other developers and @antz

Currently users are reporting that they are getting kicked by warden with reason "Exceeded warden response delay". Warden commit: https://github.com/mangoszero/server/commit/1ff6c40b0d95e21ba220158eb010dc310fb85d8b