Updating from SME 7.1.x or earlier

There seem to be a lot of questions about updating to SME v7.2

This document will attempt to compile the various questions and answers in one place.

Updating from SME 7.0 or 7.1 to SME 7.2

CD Update

	Incomplete:
	This article or section needs to be expanded. Please help to fill the gaps or discuss the issue on the talk page

Yum Update

First, install the latest yum support files:

yum update smeserver-support smeserver-yum yum yum-plugin-fastest-mirror python-sqlite
signal-event post-upgrade; signal-event reboot

Now, clean your yum cache and update, forcing your system to use the default repositories

yum clean all
yum --disablerepo=* \
--enablerepo=base \
--enablerepo=updates \
--enablerepo=smeaddons \
--enablerepo=smeos \
--enablerepo=smeupdates \
update
signal-event post-upgrade; signal-event reboot

Finally, reset your yum repositories to the new defaults (post SME 7.1)

cd /home/e-smith/db/
mv yum_repositories yum_repositories.po
/etc/e-smith/events/actions/initialize-default-databases
expand-template /etc/yum.conf

Updating from SME 7.1.3 to SME 7.2

CD Update

	Incomplete:
	This article or section needs to be expanded. Please help to fill the gaps or discuss the issue on the talk page

Yum Update

First, make sure you are using the default yum repository configuration:

cd /home/e-smith/db/
mv yum_repositories yum_repositories.po
/etc/e-smith/events/actions/initialize-default-databases
expand-template /etc/yum.conf

Now, clear your local yum cache and perform the update:

yum clean all
yum update
signal-event post-upgrade; signal-event reboot

Miscellaneous Cleanup Tasks

SME 7.2 includes different default values for some settings. This section tells you how to change those values.

qpsmtpd LogLevel

SME 7.0 - 7.1.3 all defaulted to qpsmtpd LogLevel 8 (or 'debug') in order to make sure that the logfile contained all plugin results.

SME 7.2 now includes the qpsmtpd logterse plugin allowing us to reduce the LogLevel to 6 without loss of critical tracking information and simultaneously reducing log activity significantly. To change the qpsmtpd LogLevel to 6:

config setprop qpsmtpd LogLevel 6
signal-event email-update
svc -t /var/service/qpsmtpd

or, to set the default value (in case it ever changes from 6):

config delprop qpsmtpd LogLevel
/etc/e-smith/events/actions/initialize-default-databases
signal-event email-update
svc -t /var/service/qpsmtpd

If you are using Brian Read's "mailstats" script to get daily emails of mail server activity, you should update to the latest version to ensure that you have support for the logterse plugin.

Update is available from http://mirror.contribs.org/smeserver/contribs/bread/mailstats.

Installation instructions here: http://mirror.contribs.org/smeserver/contribs/bread/mailstats/install_howto.txt or here: http://wiki.contribs.org/Email_Statistics

Known Problems

Webmail / Horde

If you have created custom templates designed to change the appearance of Webmail or Horde on your system, you may have to delete your existing custom templates, copy the new version of the same template fragments, and make your customizations on the new copies.

Anyone that has a custom-template of 110AppRegistryHorde is going to be
affected, because of the webroot detection changes in horde 3.1.4.  It doesn't
work as advertised.  Copying the new 110AppRegistryHorde to templates-custom
and then making your changes will allow you to customize your setup once again.

See: http://bugs.contribs.org/show_bug.cgi?id=3181

Remote Administration using SSH Tunnels

Prior versions of SME Server allowed you to access server-manager using http://localhost:980/server-manager after establishing an ssh tunnel on port 980 to your SME server.

You could also establish a tunnel from local port xxxx to port 443 on your SME server, then access server-manager at https://localhost:xxxx/server-manager

Both of these options will now generate a page not found error after entering your admin username & password, as the login page automatically redirects both of these to "https://localhost/server-manager".

You can work-around this issue in one of 3 ways:

1. Tunnel port 443, then login at https://localhost/server-manager
2. Tunnel whatever port you used previously, get the error message, then manually return to your original URL
3. Enable PPTP on your SME server and use a PPTP VPN for remote access to access server-manager.

---