3,250
edits
Changes
From SME Server
Jump to navigationJump to search→Known issues when upgrading from previous SME9.x
the following should solve this:
the following should solve this:
yum update smeserver-BackupPC smeserver-phpki smeserver-freepbx --enablerepo=smecontribs
yum update smeserver-BackupPC smeserver-phpki smeserver-freepbx --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)
route add default gateway `db configuration get GatewayIP`
yum update e-smith-base
signal-event post-upgrade; signal-event reboot
===SME 8===
===SME 8===
