Changed settings after upgrading to 5.01 Pro and 1.791

Submitted by hasse_basse on Tue, 04/05/2016 - 06:09 Pro Licensee

After the last upgrade to 5.01 and 1.791 my Drupal 7 site went down. It turned out that the MySQL setting Maximum packet size had changed to a too low value. I put it back to 16M but today it happend again, it went down to 1M. What is this about?

Another issue is that with the upgrade, a Postfix setting changed so I had HELO problems with other mailservers. The "Internet hostname of this mail system" changed to an old system setting setting I had used earlier and didn't use "Default (provided by the system)". I changed the setting to "Default (provided by the system)" and it worked fine, but when I later went back just to check the setting it had moved away from "Default (provided by the system)" but thanks God it shows the right value.

So for the moment all is fine but why is the MySQL setting changing and why does the Postfix setting not stay as I asked it to stay?

Best regards

Hans

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Tue, 04/05/2016 - 09:41

Howdy -- sorry to hear that your config is changing!

However, I don't think that Virtualmin is actually what is changing that.

Virtualmin woudn't have a reason to make changes like the ones you're describing (in fact, it rarely ever makes any config changes without being prompted to do that.

Is it possible that another admin re-ran the setup wizard (which can be done in System Settings)? If the setup wizard were re-run, the person running that could choose a different MySQL config to use.

Submitted by hasse_basse on Tue, 04/05/2016 - 11:33 Pro Licensee

Hmm...

I'm alone on this server. It is a one man server in a one man business. So no. The changes came after upgrading Virtualmin and Webmin.

Submitted by andreychek on Tue, 04/05/2016 - 11:53

Just to verify, I did a global search through the entire Virtualmin code base for the text "max_allowed_packet". The only reference to max_allowed_packet is in feature-mysql.pl, where the setup wizard is being run. When selecting a new MySQL config, it will at that point change that option to 1M.

However, I don't see any anything that would ever cause that change to occur automatically.

On my own personal server, I have "max_allowed_packet" set to 16M.

That option isn't actually set in virtualmin.com's my.cnf file.

In both cases though, it's been set that way for years without being changed.

I will ask Jamie just to be super sure, but I don't believe that is being changed by Webmin or Virtualmin.

I believe you that it's changing, but I suspect there may be something else at work here that's causing that to occur.

Out of curiosity, what is the output of this command:

dpkg -l 'mysql*'

Submitted by JamieCameron on Tue, 04/05/2016 - 23:36

Correct -that setting should only be changed by running the setup wizard.

Submitted by hasse_basse on Wed, 04/06/2016 - 03:42 Pro Licensee

ii mysql-client 5.5.47-0+deb all MySQL database client (metapackag un mysql-client-5 (no description available) un mysql-client-5 (no description available) ii mysql-client-5 5.5.47-0+deb amd64 MySQL database client binaries ii mysql-common 5.5.47-0+deb all MySQL database common files, e.g. ii mysql-server 5.5.47-0+deb all MySQL database server (metapackag un mysql-server-5 (no description available) un mysql-server-5 (no description available) ii mysql-server-5 5.5.47-0+deb amd64 MySQL database server binaries an un mysql-server-c (no description available) un mysql-server-c (no description available) un mysql-server-c (no description available) ii mysql-server-c 5.5.47-0+deb amd64 MySQL database server binaries

OK, I had changed the "Maximum packet size settings" in MySQL Server Configuration under Webmin and I did so again to 16M. Then I run the Wizard and the setting went back to 1M. So the conclusion is that when I upgraded, Virtualmin forced its settings upon the settings I had done manually in MySQL under Webmin. So now we know this.

I think you should be clear about what values in Webmin will be overridden by Virtualmin. Apache Webserver warns that the settings are controlled by Virutalmin, but for MySQL there are no such warnings. And what about what happend in Postfix?

Submitted by hasse_basse on Wed, 04/06/2016 - 04:28 Pro Licensee

This getting worse. Either I don't understand what I'm doing or.............

I went to /etc/mysql/my.cnf and [mysqld] and changed to max_allowed_packet = 16M. Then I run the Wizard again and the value changed back to 1M!

The settings I use are: In the Wizard: MySQL configuration size: Huge system

So what ever I do, the Wizard has made up its mind that the value should be 1M !!! So everytime I run the Wizard I have to manually change the value back to 16M. Or?

Hans

Submitted by andreychek on Wed, 04/06/2016 - 09:08

Well, in most cases the setup wizard is only run once, immediately after Virtualmin is first installed.

The setup wizard is not run during upgrades.

Did you manually run the setup wizard after performing the upgrade? If not, then something else may be going on there.

However, if you need to run the installation wizard after your system is all setup, but wish to preserve your MySQL config, I would recommend choosing the option to keep the existing MySQL config. That tells Virtualmin not to make any changes to the MySQL config.