3,254
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + Line 54:
Line 54: − + Line 67:
Line 67: + + + + + − + − + + + + + + + Line 84:
Line 95: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 146:
Line 200: + + + + + + + + + + + + + + + + + + + + + + + +
→Access to web panel of some contribs
{{Languages}}
{{Languages}}
We dedicate this release of SME Server 9.2 to Tony Keane who passed away on 1st April, 2016. He was a long time user and supporter of Koozali SME Server and one of the founding members of the Koozali Foundation.
We dedicate this release of SME Server 9.2 to [[Tony Keane]] who passed away on 1st April, 2016. He was a long time user and supporter of Koozali SME Server and one of the founding members of the Koozali Foundation.
==SME Server 9.2 Final (Tony Keane)==
==SME Server 9.2 Final ([[Tony Keane]])==
The SME Server development team is pleased to announce the release of
The SME Server development team is pleased to announce the release of
===Note===
===Note===
In-place upgrades are not supported. It is necessary to backup and then restore.
In-place upgrades from SME Server prior to version 9.0 are not supported. It is necessary to backup and then restore.
/boot partition is always RAID 1.
/boot partition is always RAID 1.
[[SME_Server:Documentation:Administration_Manual:Chapter5|Installation procedure]]
[[SME_Server:Documentation:Administration_Manual:Chapter5|Installation procedure]]
{{Warning box|SME 9.2 ISO only, DO NOT enable nic bonding on an initial install when server only mode is selected.
If your hardware has two network adapters installed or there are two nics configured in a VM and you have selected server only mode during the install you will be offered the opportunity to enable bonding of the nics, the current SME 9.2 ISO has an issue with this initial configuration and a loss of connectivity will result on reboot.
DO NOT enable bonding on initial install, carry out a yum update after initial install and then reconfigure and enable bonding if that is your wish.}}
===Upgrading===
===Upgrading===
===SME 9===
===SME 9===
{{Note box|msg=In-place upgrades to SME 9.2 *are* supported - from 9.# only. # yum upgrade, see note below for caveats.}}
{{Note box|msg=In-place upgrades to SME 9.2 *are* supported - from 9.# only. # yum upgrade or yum update, see note below for caveats.}}
{{Note box|Although a yum upgrade should return a working updated server, to be 100% sure, you are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}
{{Note box|Although a yum upgrade should return a working updated server, to be 100% sure, you are advised to only upgrade clean machines, e.g. without contribs or other modifications.
yum upgrade forces the removal of obsolete packages, while yum update may or may not also do this. The removal of obsolete packages can be risky, as it may remove packages that you use.
This makes yum update a safer option when not knowing state of server..}}
Please see[[SME_Server_9.2_Addendum| The Addendum]] for additional notes released after initial ISO release.
====DVD/CD====
====DVD/CD====
====Check for contrib packages that may need upgrading====
====Check for contrib packages that may need upgrading====
Even though it is recommended that you only upgrade clean machines (e.g. without contribs or other modifications), it may be possible that you have a contrib installed that you forgot about. After the upgrade, check if any contribs may require an upgrade from the smecontribs repository.
Even though it is recommended that you only upgrade clean machines (e.g. without contribs or other modifications), it may be possible that you have a contrib installed that you forgot about. After the upgrade, check if any contribs may require an upgrade from the smecontribs repository.
====Known issues when upgrading from previous SME9.x====
=====QPSMTPD stop accepting incoming mails=====
Some plugins have a different name with the new version of qpsmtpd, the service in charge of the incoming emails. This is why some template custom and some not up to date contribs could make this service fail to start.
1. you must take attention to upgrade 3 contribs (if they are already installed) related to email, otherwise you server might stop receiving email
# [[Mailstats|smeserver-mailstat]] >=1.1-9 (or your daily mail stats will be incomplete but email will work)
# [[GeoIP|smeserver-geoip]] >=1.1.2-7 (as geoip database have changed)
# '''[[Wbl|smeserver-wbl]] >=0.3.0-14 (or will prevent email service to start)'''
yum update --enablerepo=smecontribs
2. you must pay attention with current custom-templates related to qpsmtpd. A quick way to check is
/sbin/e-smith/audittools/templates
If you see any templates in /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/, we suggest you to remove them.
mkdir /root/qpsmtpd-old-custom-templates
mv /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers /root/qpsmtpd-old-custom-templates/
signal-event email-update
You can then put them one after the other if you want to test them individually and really want some of them back. You can see a list of available plugins to control the name of your custom-templates by doing
ll /usr/share/qpsmtpd/plugins
templates-custom related to plugins with new names known to conflict
#10check_earlytalker see [[Qpsmtpd_check_earlytalker]]
#31check_badmailfromto see [[Email#How_to_block_email_from_one_address_to_another_address_with_check_badmailfromto_plugin]]
=====Access to web panel of some contribs=====
Security has been increased for the authorization mechanism and as a result the following 3 contribs need to be updated to keep access to their panel :
# [[BackupPC|smeserver-BackupPC]]
# [[PHPki|smeserver-phpki]]
# [[FreePBX|smeserver-freepbx]]
# [[Isoqlog|smeserver-isoqlog]]
the following should solve this:
yum update smeserver-BackupPC smeserver-phpki smeserver-freepbx smeserver-isoqlog --enablerepo=smecontribs
=====no external network access when using bonding=====
with e-smith-base-5.6.0-30.el6.sme.noarch.rpm provided on the SME 9.2 ISO, if you are using bonding of two network interfaces (e.g. server-only with two indentical network adapter) the default route to the gateway is not created.
to check if you have any bonding on your server:
# ifconfig |grep bond
If it returns something then you have bonding.
This is fixed in e-smith-base-5.6.0-31.el6.sme.noarch.rpm available in smeupdates since May the 4th, so you have nothing to worry if ou simply did a yum update after this date. If you installed the previous from an iso and do not have network here is how to fix this ( you can replace `db configuration get GatewayIP` by your gateway IP if you know it, but this command should give the value you previously configured). Alternatively. from SME9.2 iso you can just configure your server without bonding, do a yum update and use console to reconfigure your server with bonding.
route add default gateway `db configuration get GatewayIP`
yum update e-smith-base
signal-event post-upgrade; signal-event reboot
===SME 8===
===SME 8===
Where extensive modifications have been made to the "old server (eg SME8.1)", it is recommended to carry out a test backup & restore upgrade first, to discover any problems & ascertain suitable fixes & workarounds. Removing contribs & custom templates before upgrading is recommended.
Where extensive modifications have been made to the "old server (eg SME8.1)", it is recommended to carry out a test backup & restore upgrade first, to discover any problems & ascertain suitable fixes & workarounds. Removing contribs & custom templates before upgrading is recommended.
====Known issues upgrade from SME8====
'''1.''' You might want to check what are the current installed extra rpm on your old SME 8 to be able to simply install them on your new SME 9. Usually this is simply done this way :
# /sbin/e-smith/audittools/newrpms
Loaded plugins: fastestmirror, protect-packages, smeserver
Loading mirror speeds from cached hostfile
Cannot find a valid baseurl for repo: base
YumRepo Error: All mirror URLs are not using ftp, http(s) or file.
Eg. Invalid release/
removing mirrorlist with no valid mirrors: /var/cache/yum/base/mirrorlist.txt
This is because Centos mirror are no longer available. Do not worry there is a workaround :
db yum_repositories setprop base BaseURL 'http://vault.centos.org/5.11/os/$basearch/'
db yum_repositories setprop updates BaseURL 'http://vault.centos.org/5.11/updates/$basearch/'
db yum_repositories delprop base MirrorList
db yum_repositories delprop updates MirrorList
signal-event yum-modify
yum clean all
and then you can issue the good old command without issue:
/sbin/e-smith/audittools/newrpms
'''2.''' You might also want to check [[#Known_issues_when_upgrading_from_previous_SME9.x| SME9 specific issues]] as some might apply also for a migration from SME8.
===RAID===
===RAID===