Difference between revisions of "Updating from SME 7.1.x or earlier"
Line 56: | Line 56: | ||
===Ensuring the correct yum repository configuration=== | ===Ensuring the correct yum repository configuration=== | ||
− | Unless you are an expert with yum you are highly encouraged to reset your yum repository configuration to the defaults using the instructions found at [[:AddingSoftware#Restoring_Default_Yum_Repositories]] | + | Unless you are an expert with yum you are highly encouraged to reset your yum repository configuration to the defaults using the instructions found at [[:AddingSoftware#Restoring_Default_Yum_Repositories]]. |
+ | |||
+ | SME updates assume that the default repositories are enabled, and that any 3rd party repositories you may have configured are | ||
+ | * disabled by default | ||
+ | * created with appropriate "Exclude" paramaters | ||
+ | * accessed manually when necessary using the ''yum --enablerepo=xxx'' syntax. | ||
==Known Problems== | ==Known Problems== |
Revision as of 17:01, 27 July 2007
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
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). Unless you are an expert with yum you are highly encouraged to reset your yum repository configuration to the defaults using the instructions found at AddingSoftware#Restoring_Default_Yum_Repositories
Updating from SME 7.1.3 to SME 7.2
CD Update
Yum Update
First, make sure you are using the default yum repository configuration by following the instructions found at AddingSoftware#Restoring_Default_Yum_Repositories
Now, clear your local yum cache and perform the update:
yum clean all yum update signal-event post-upgrade; signal-event reboot
Cleanup Tasks
Updating Configuration Database with New Default Values
SME 7.2 includes different default values for some settings. This section tells you how to change those values.
Generic Instructions
Any configuration database item that has a "default" value can be set to the default value using
config delprop key prop /etc/e-smith/events/actions/initialize-default-databases
Afterwards, you will need to re-expand the affected templates and restart the affected services..
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.
config delprop qpsmtpd LogLevel /etc/e-smith/events/actions/initialize-default-databases signal-event email-update svc -t /var/service/qpsmtpd
Ensuring the correct yum repository configuration
Unless you are an expert with yum you are highly encouraged to reset your yum repository configuration to the defaults using the instructions found at AddingSoftware#Restoring_Default_Yum_Repositories.
SME updates assume that the default repositories are enabled, and that any 3rd party repositories you may have configured are
- disabled by default
- created with appropriate "Exclude" paramaters
- accessed manually when necessary using the yum --enablerepo=xxx syntax.
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:
- Tunnel port 443, then login at https://localhost/server-manager
- Tunnel whatever port you used previously, get the error message, then manually return to your original URL
- Enable PPTP on your SME server and use a PPTP VPN for remote access to access server-manager.
Missing email folders after upgrade
After I upgrade my SMESERVER, my email folders have disappeared when using IMAP