Changes

From SME Server
Jump to navigationJump to search

Updating from SME 7.1.x or earlier (view source)

Revision as of 10:27, 27 November 2015

1,124 bytes added ,  10:27, 27 November 2015
modified Note box content
Line 1: Line 1: −
There seem to be a lot of questions about updating to SME v7.2
+
There seem to be a lot of questions about updating to SME Server version 7.2 and higher from releases of SME Server 7.1.x and before.
−
 
   
This document will attempt to compile the various questions and answers in one place.
 
This document will attempt to compile the various questions and answers in one place.
−
  −
      
==CD Update==
 
==CD Update==
 
{{Note_box|For this you need physical access to your server as SSH access is unavailable during CD updates.}}
 
{{Note_box|For this you need physical access to your server as SSH access is unavailable during CD updates.}}
 
# Insert the CD into your server and issue a reboot, follow the instructions presented to you on the server screen to update to SME Server 7.2.
 
# Insert the CD into your server and issue a reboot, follow the instructions presented to you on the server screen to update to SME Server 7.2.
−
# Reset yum to the new default configuration as described here: [[:AddingSoftware#Restoring_Default_Yum_Repositories]]
+
# Reset yum to the new default configuration as described here: [[:SME Server:Adding_Software#Restoring_Default_Yum_Repositories]]
 
# Reset other settings to new defaults as shown here: [[:Updating_to_SME_7.2#Updating_Configuration_Database_with_New_Default_Values]]
 
# Reset other settings to new defaults as shown here: [[:Updating_to_SME_7.2#Updating_Configuration_Database_with_New_Default_Values]]
 
# Perform a final ''yum update'' to obtain updates or patches released after the generation of the 7.2 iso.
 
# Perform a final ''yum update'' to obtain updates or patches released after the generation of the 7.2 iso.
Line 21: Line 18:  
  mv yum_repositories yum_repositories.po
 
  mv yum_repositories yum_repositories.po
 
  /etc/e-smith/events/actions/initialize-default-databases
 
  /etc/e-smith/events/actions/initialize-default-databases
−
  expand-template /etc/yum.conf
+
  signal-event yum-modify
 
  signal-event post-upgrade; signal-event reboot
 
  signal-event post-upgrade; signal-event reboot
 
<li>Obtain the remaining support files</li>
 
<li>Obtain the remaining support files</li>
Line 53: Line 50:  
* A fresh install from the SME 7.2 CD is the ''only'' instance in which you do ''not'' need to reconfigure your yum repositories.
 
* A fresh install from the SME 7.2 CD is the ''only'' instance in which you do ''not'' need to reconfigure your yum repositories.
   −
Therefore, unless you are an expert with yum and have made specific sme-related customizations for some reason, you '''must''' reset your yum repository configuration to the SME defaults using the instructions found at [[:AddingSoftware#Restoring_Default_Yum_Repositories]] or your yum updates '''will''' fail sooner or later.
+
Therefore, unless you are an expert with yum and have made specific sme-related customizations for some reason, you '''must''' reset your yum repository configuration to the SME defaults using the instructions found at [[:SME Server:Adding_Software#Restoring_Default_Yum_Repositories]] or your yum updates '''will''' fail sooner or later.
    
All SME updates assume that the default repositories are enabled, and that any 3rd party repositories you may have configured are
 
All SME updates assume that the default repositories are enabled, and that any 3rd party repositories you may have configured are
Line 77: Line 74:  
  signal-event email-update
 
  signal-event email-update
 
  svc -t /var/service/qpsmtpd
 
  svc -t /var/service/qpsmtpd
−
{{Note_box|If you are using Brian Read's spamfilter-stats-7.pl 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. The update is available from http://mirror.contribs.org/smeserver/contribs/bread/mailstats .
+
{{Note_box|If you are using Brian Read's spamfilter-stats-7.pl 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. See '''[[Mailstats]]''' for more information}}
−
 
  −
Installation instructions here: http://mirror.contribs.org/smeserver/contribs/bread/mailstats/install_howto.txt or here: http://wiki.contribs.org/Email_Statistics}}
      
====RHSBL Servers====
 
====RHSBL Servers====
 
RHSBL or ''Right-Hand Side Black List'': Search for known spam hosts by host name.   
 
RHSBL or ''Right-Hand Side Black List'': Search for known spam hosts by host name.   
   −
If you want to try out the RHSBL servers configured by default in SME 7.2:
+
If you want to try out the RHSBL servers configured by default in SME:
 
  <nowiki>config delprop qpsmtpd SBLList
 
  <nowiki>config delprop qpsmtpd SBLList
−
config setprop qpsmtpd SBLList bogusmx.rfc-ignorant.org:multi.surbl.org:black.uribl.com\
+
config setprop qpsmtpd SBLList dbl.spamhaus.org:multi.surbl.org:black.uribl.com:rhsbl.sorbs.net
−
:rhsbl.sorbs.net:bulk.rhs.mailpolice.com:fraud.rhs.mailpolice.com\
  −
:porn.rhs.mailpolice.com:adult.rhs.mailpolice.com:ex.dnsbl.org\
  −
:blackhole.securitysage.com
   
signal-event email-update</nowiki>
 
signal-event email-update</nowiki>
    
This will enable the following SBL servers for your system.  Be sure to check them out to see if they are consistent with your policies before enabling them.  Don't forget that RHSBL is '''disabled''' by default in SME!
 
This will enable the following SBL servers for your system.  Be sure to check them out to see if they are consistent with your policies before enabling them.  Don't forget that RHSBL is '''disabled''' by default in SME!
−
* [http://www.rfc-ignorant.org/policy-bogusmx.php bogusmx.rfc-ignorant.org]
+
* [http://www.spamhaus.org/ dbl.spamhaus.org]
 
* [http://www.surbl.org/ multi.surbl.org]
 
* [http://www.surbl.org/ multi.surbl.org]
 
* [http://www.uribl.com/about.shtml black.uribl.com]
 
* [http://www.uribl.com/about.shtml black.uribl.com]
 
* [http://www.au.sorbs.net/using.shtml rhsbl.sorbs.net]
 
* [http://www.au.sorbs.net/using.shtml rhsbl.sorbs.net]
−
* [http://rhs.mailpolice.com/ bulk.rhs.mailpolice.com]
  −
* fraud.rhs.mailpolice.com
  −
* porn.rhs.mailpolice.com
  −
* adult.rhs.mailpolice.com
  −
* [http://www.dnsbl.org/ex.dnsbl.php3 ex.dnsbl.org]
  −
* [http://wiki.openrbl.org/wiki/Blackhole.securitysage.com blackhole.securitysage.com]
     −
{{Note box|Some of the SBLList above are quiet aggressive. As a result, genuine mail may be blocked. You should check your qpsmtpd logs at regular intervals to assess the impact of your selection. To reduce the amount of information presented in the logs, filter with "logterse".}}
+
<br>
 +
{{Warning box|[http://wiki.openrbl.org/wiki/Blackhole.securitysage.com blackhole.securitysage.com] was a default SBL server but is no longer working and was removed on Oct 5, 2008.  If you have blackhole.securitysage.com in your SBLList and have RHSBL enabled then <b>ALL INCOMING EMAIL WILL BOUNCE.</b>  You must remove blackhole.securitysage.com from your SBLList for your email server to work properly. Follow the instructions above to reset the default SBLList.}}
 +
 
 +
{{Note box|Some of the SBLList above are quite aggressive. As a result, genuine mail may be blocked. You should check your qpsmtpd logs at regular intervals to assess the impact of your selection. To reduce the amount of information presented in the logs, filter with "logterse".
 +
 
 +
A conservative (& some would consider safe) setting for RHSBL would be as follows:
 +
config setprop qpsmtpd SBLList dbl.spamhaus.org
 +
signal-event email-update
 +
 
 +
This will enable the following SBL server for your system. Don't forget that RHSBL is '''disabled''' by default in SME!
 +
* [http://www.spamhaus.org/ dbl.spamhaus.org]}}
    
====DNSBL Servers====
 
====DNSBL Servers====
 
DNSBL (DNS Block List): Block spam hosts based on the IP address of the remote system.
 
DNSBL (DNS Block List): Block spam hosts based on the IP address of the remote system.
   −
If you want to try out the DNSBL servers configured by default in SME 7.2:
+
If you want to try out the DNSBL servers configured by default in SME:
 
  <nowiki>config delprop qpsmtpd RBLList
 
  <nowiki>config delprop qpsmtpd RBLList
−
config setprop qpsmtpd RBLList bl.spamcop.net:combined.njabl.org:dnsbl.ahbl.org\
+
config setprop qpsmtpd RBLList bl.spamcop.net\
−
:dnsbl-1.uceprotect.net:dnsbl-2.uceprotect.net:list.dsbl.org\
+
:dnsbl-1.uceprotect.net:dnsbl-2.uceprotect.net\
−
:multihop.dsbl.org:psbl.surriel.com:zen.spamhaus.org
+
:psbl.surriel.com:zen.spamhaus.org
 
signal-event email-update</nowiki>
 
signal-event email-update</nowiki>
    
This will enable the following DNSBL servers for your system.  Be sure to check them out before enabling them.  (List updated 7/31/2007 to replace ''sbl-xbl.spamhaus.org'' with the new ''zen.spamhaus.org'').
 
This will enable the following DNSBL servers for your system.  Be sure to check them out before enabling them.  (List updated 7/31/2007 to replace ''sbl-xbl.spamhaus.org'' with the new ''zen.spamhaus.org'').
 +
 +
NOTE: as of January 1, 2015, [http://www.ahbl.org/ dnsbl.ahbl.org] service is no longer active. If you have added this service to your DNSBL record, please remove it. Leaving it in will cause a great many false positives.
    
Don't forget that DNSBL is '''disabled''' by default in SME!  
 
Don't forget that DNSBL is '''disabled''' by default in SME!  
    
* [http://www.spamcop.net/ bl.spamcop.net]
 
* [http://www.spamcop.net/ bl.spamcop.net]
−
* [http://www.njabl.org/ combined.njabl.org]
  −
* [http://www.ahbl.org/ dnsbl.ahbl.org]
   
* [http://www.uceprotect.net/en/index.php?m=1&s=0 dnsbl-1.uceprotect.net] Conservative (blocks single IPs)
 
* [http://www.uceprotect.net/en/index.php?m=1&s=0 dnsbl-1.uceprotect.net] Conservative (blocks single IPs)
 
* [http://www.uceprotect.net/en/index.php?m=1&s=0 dnsbl-2.uceprotect.net] More agressive (blocks class C networks)
 
* [http://www.uceprotect.net/en/index.php?m=1&s=0 dnsbl-2.uceprotect.net] More agressive (blocks class C networks)
−
* [http://dsbl.org/main list.dsbl.org] single-stage relays tested by trusted testers
  −
* [http://dsbl.org/main multihop.dsbl.org] the outputs of multihop relays, tested by trusted testers
   
* [http://psbl.surriel.com/ psbl.surriel.com]
 
* [http://psbl.surriel.com/ psbl.surriel.com]
 
* [http://www.spamhaus.org/zen/ zen.spamhaus.org] ''formerly sbl-xbl.spamhaus.org''
 
* [http://www.spamhaus.org/zen/ zen.spamhaus.org] ''formerly sbl-xbl.spamhaus.org''
   −
{{Note box|Some of the RBLList above are quiet aggressive. As a result, genuine mail may be blocked.
+
{{Note box|Some of the RBLList above are quite aggressive. As a result, genuine mail may be blocked.
 
Many will argue what's best but most would agree that you can set best-practice recommended settings by:
 
Many will argue what's best but most would agree that you can set best-practice recommended settings by:
−
  config setprop qpsmtpd RBLList zen.spamhaus.org:whois.rfc-ignorant.org:dnsbl.njabl.org
+
  config setprop qpsmtpd RBLList zen.spamhaus.org
 
  signal-event email-update
 
  signal-event email-update
   Line 153: Line 147:  
This probably indicates that your yum repositories are misconfigured.  You should follow the standard [[#Yum_Update]] procedure above.
 
This probably indicates that your yum repositories are misconfigured.  You should follow the standard [[#Yum_Update]] procedure above.
 
====Existing lock /var/run/yum.pid: another copy is running. Aborting.====
 
====Existing lock /var/run/yum.pid: another copy is running. Aborting.====
−
SME runs yum automatically to check for available updates.  If this background check is running you will see this error. Just wait a few minutes for the background process to finish.
+
SME Server runs yum automatically to check for available updates.  If this background check is running you will see this error. Just wait a few minutes for the background process to finish.
    
====GLib-CRITICAL **: file gtimer.c: line 106 (g_timer_stop)====
 
====GLib-CRITICAL **: file gtimer.c: line 106 (g_timer_stop)====
 
This error indicates that you have installed yum packages that require later versions of sqlite and python-sqlite than you have installed on your system.  You can recover using the commands shown below, which should:
 
This error indicates that you have installed yum packages that require later versions of sqlite and python-sqlite than you have installed on your system.  You can recover using the commands shown below, which should:
−
* Download and install the latest versions of python-sqlite and sqlite (to make yum operational) and smeserver-yum (to provide proper repository defaults).
+
<ol></li><li>Download and install the latest versions of python-sqlite and sqlite (to make yum operational) and smeserver-yum (to provide proper repository defaults).
−
* Reset your repository configuration
+
  cd /tmp
−
* Reboot to activate all changes
+
wget ftp://ibiblio.org/pub/linux/distributions/smeserver/releases/7.2/smeos/i386/SME/RPMS/*sqlite-*
−
<nowiki>cd /tmp
+
wget ftp://ibiblio.org/pub/linux/distributions/smeserver/releases/7.2/smeos/i386/SME/RPMS/smeserver-yum-*
−
wget ftp://ibiblio.org/pub/linux/distributions/smeserver/releases/7.2/smeos/i386/SME/RPMS/*sqlite-*
+
yum localinstall sqlite python-sqlite smeserver-yum
−
wget ftp://ibiblio.org/pub/linux/distributions/smeserver/releases/7.2/smeos/i386/SME/RPMS/smeserver-yum-*
+
</li><li>Reset  your repository configuration
−
yum localinstall sqlite python-sqlite smeserver-yum
+
cd /home/e-smith/db/
 +
mv yum_repositories yum_repositories.po
 +
/etc/e-smith/events/actions/initialize-default-databases
 +
signal-event yum-modify
 +
</li><li>Reboot to activate all changes
 +
signal-event post-upgrade; signal-event reboot
 +
</li><li>After rebooting, make sure you have the basic files before beginning your major update:
 +
yum update dbus dbus-glib smeserver-support yum
 +
</li><li>Then finish your update:
 +
yum update
 +
</li></ol>
 +
 
   −
cd /home/e-smith/db/
+
=====Troubleshooting when yum install is broken=====
−
mv yum_repositories yum_repositories.po
  −
/etc/e-smith/events/actions/initialize-default-databases
  −
expand-template /etc/yum.conf
     −
signal-event post-upgrade; signal-event reboot</nowiki>
+
If yum is broken, then it's obviously not possible to use yum to do updates (to yum).
 +
If you are unable to install the sqlite and smeserver-yum packages with yum as per the above instructions, then you will need to manually download the packages & (dependency packages) & install them from the local machine using rpm -Uvh.
 +
You might receive this type of error when manually updating packages:
 +
rpm -Uvh sqlite* python-sqlite* smeserver-yum*
 +
error: Failed dependencies:
 +
yum-plugin-fastestmirror is needed by
 +
smeserver-yum-1.2.0-37.el4.sme.noarch
   −
After rebooting, make sure you have the basic files before beginning your major update:
+
This indicates you also need to download the dependency rpm, in this case yum-plugin-fastestmirror.
−
  yum update dbus dbus-glib smeserver-support yum
+
 
 +
Manually download ALL the required packages to an empty folder, eg from
 +
http://mirror.contribs.org/smeserver/releases/7/ then do:
 +
  rpm -Uvh *.rpm
 +
signal-event post-upgrade
 +
reboot
   −
Then finish your update:
+
Then continue on with the normal yum update process
 
  yum update
 
  yum update
 +
signal-event post-upgrade
 +
reboot
    
===Webmail / Horde===
 
===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.
 
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.
−
{{Note_box|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 [[Bugzilla:3181]].}}
+
{{Note_box|msg=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 [[Bugzilla:3181]].}}
    
===IMAP subfolders do not show in IMP===
 
===IMAP subfolders do not show in IMP===
Line 206: Line 221:     
===Missing email folders after upgrade===
 
===Missing email folders after upgrade===
−
This link explains why you may appear to be missing your mail folders after an upgrade: [[:Email#After_I_upgrade_my_SMESERVER.2C_my_email_folders_have_disappeared_when_using_IMAP|After I upgrade my SMESERVER, my email folders have disappeared when using IMAP]]
+
This link explains why you may appear to be missing your mail folders after an upgrade: [[:Email#After_I_upgrade_my_SME_Server.2C_my_email_folders_have_disappeared_when_using_IMAP|After I upgrade my SME Server, my email folders have disappeared when using IMAP]]
    
===10fix_privilege_tables in message log===
 
===10fix_privilege_tables in message log===
Line 217: Line 232:  
----
 
----
 
[[Category:Howto]]
 
[[Category:Howto]]
 +
[[Category:Administration]]
RayMitchell
624

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/5934...29644"

Navigation menu