Version 4 (modified by Ross, 8 years ago) (diff)


Technical notes on upgrading from squeeze to wheezy

This page details some of the issues we've encountered regarding the squeeze to wheezy upgrades, additional information can be found on #7425, squeeze-wheezy-mosh-upgrade, and support-team/server-upgrade-status.

major changes

please add more as we discover them:

we move from PHP 5.3 (which is approaching end of life) to PHP 5.4

phpmyadmin and php5_cgi

We encountered weirdness with phpmyadmin during the upgrade to rose.

After the upgrade phpmyadmin failed to load with the error:

navigation.php< not found on the server.

Apparently the apache module php5_cgi created this problem as dis-enabling it fixed the error. However, we're not sure why the module got loaded. We'll need to pay attention to this issue on future upgrades, though that module does not seem to be loaded on other moshes.

We also needed to rebuild the phpmyadmin control database. This was done using the info from /etc/phpmyadmin/config-db.php. It's not clear why, but the old phpmyadmin control database did not transfer to the upgraded version of the system. Likely due to choices made during the phpmyadmin reconfiguration.

configuration files to keep

Almost all configuration files will use the package maintainers version. Here is the short list of things not to modify:


Keep the currently installed version, we do not actually want awstats to install a cronjob since we manage this cronjob separately.


The newer version of sysstat asks that you delete the current files, do it


You will be given the following options for grub:

  1. install the package maintainer's version
  2. keep the local version currently installed
  3. show the differences between the versions
  4. show a side-by-side difference between the versions
  5. show a 3-way difference between available versions
  6. do a 3-way merge between available versions (experimental)
  7. start a new shell to examine the situation

You can safely just choose to keep the local version as there are no meaningful changes to the package maintainers version.

mysql-5.5 open files

It's not yet clear if this particular issue will be chronic across servers. However, according to ticket #8040, it appears that mysql file limits might need to be increased just to be safe. The current recommendation judging from rose is to modify...


And add the following lines to that file:

mysql   soft    nofile  4096
mysql   hard    nofile  32768

root    soft    nofile  4096
root    hard    nofile  32768


Upon rebooting rose using shutdown -h now the service on rose's host failed to start the kvm process. This required the following commands from

sv down rose
sv up /etc/sv/kvm/rose