Changes

From SME Server
Jump to navigationJump to search

SME Server:Documentation:FAQ (view source)

Revision as of 23:43, 30 June 2007

203 bytes removed ,  23:43, 30 June 2007
group yum items
Line 8: Line 8:       −
===Reconfigure / post-upgrade and reboot===
+
===Yum Updates===
−
*When is a post-upgrade and reboot required?
  −
The server manager yum installer has no way of determining whether
  −
any configuration files will change if all are re-expanded or to know which
  −
binaries have changed (or use libraries which have now changed) and therefore
  −
need to be restarted. The only '''safe''' option is to reconfigure and restart
  −
everything.
  −
 
  −
After clicking '''Reconfigure''' check the Status message and that the server does actually reboot.
  −
Rarely circumstances arise that prevent the reconfigure from triggering. If so run the following,
  −
 
  −
signal-event post-upgrade; signal-event reboot
  −
 
  −
 
   
=== Which repositories should be enabled===
 
=== Which repositories should be enabled===
   Line 46: Line 33:  
ahead of the distribution.}}
 
ahead of the distribution.}}
    +
{{DrawBoxNote|content=A system installed from the SME 7.1 iso will have the 5 repositories above enabled.  A system installed from the SME 7.0 iso and updated to 7.1 or later will only have the 3 SME Server repositories enabled.  After updating from SME 7.0 to SME 7.1.x you should enable the additional repositories in server-manager.
 +
}}
 +
 +
*For another way to reset the repositories to the default see [[:AddingSoftware#Restoring_Default_Yum_Repositories]]
 +
 +
 +
===Reconfigure / post-upgrade and reboot===
 +
*When is a post-upgrade and reboot required?
 +
The server manager yum installer has no way of determining whether
 +
any configuration files will change if all are re-expanded or to know which
 +
binaries have changed (or use libraries which have now changed) and therefore
 +
need to be restarted. The only '''safe''' option is to reconfigure and restart
 +
everything.
 +
 +
After clicking '''Reconfigure''' check the Status message and that the server does actually reboot.
 +
Rarely circumstances arise that prevent the reconfigure from triggering. If so run the following,
 +
 +
signal-event post-upgrade; signal-event reboot
 +
 +
 +
====General====
 +
*Please Wait - Yum Running (prereposetup)
 +
This means Yum is working out what updates are available.
 +
Occasionally such as when large sets of updates are released this could take 10+ minutes to complete
 +
 +
*Yum doesn't seem to be working correctly. What do I do now?
 +
If for some reason you can't get yum to work correctly, try:
 +
yum clean metadata
 +
or possibly 'yum clean all'
 +
yum update
 +
 +
*Fix for 'Metadata file does not match checksum'
 +
Typical error message
 +
http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz:
 +
[Errno -1] Metadata file does not match checksum Trying other mirror.
 +
Error: failure: repodata/primary.xml.gz from dag: [Errno 256] No more mirrors to try.
 +
 +
To flush the up stream proxies, using wget, run:
 +
 +
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/filelists.xml.gz
 +
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz
 +
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/repomd.xml
 +
yum update
 +
 +
* An unclean shutdown during a system update can put the system into a state where it's difficult to recover.
 +
Try not to kick the power cord and use a UPS
 +
 +
* Where can I go to learn more about yum, and about how SME uses it?
 +
[[:SME_Server:Documentation:Technical_Manual:Chapter6#Yum_Repositories]], man yum,
   −
{{DrawBoxNote|content=A system installed from the SME 7.1 iso will have the 5 repositories above enabled.  A system installed from the SME 7.0 iso and updated to 7.1 or later will only have the 3 SME Server repositories enabled.  After updating from SME 7.0 to SME 7.1.x you should enable the additional repositories in server-manager, or manually using:
  −
db yum_repositories setprop base status enabled
  −
db yum_repositories setprop updates status enabled
  −
expand-template /etc/yum.conf
  −
}}
      
===Client Computers===
 
===Client Computers===
Line 264: Line 295:  
Don't remove or rename .junkmail folders.
 
Don't remove or rename .junkmail folders.
   −
===Yum===
  −
*Please Wait - Yum Running (prereposetup)
  −
This means Yum is working out what updates are available.
  −
Occasionally such as when large sets of updates are released this could take 10+ minutes to complete
  −
  −
*Yum doesn't seem to be working correctly. What do I do now?
  −
If for some reason you can't get yum to work correctly, try:
  −
yum clean metadata
  −
or possibly 'yum clean all'
  −
yum update
  −
  −
*Fix for 'Metadata file does not match checksum'
  −
Typical error message
  −
http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz:
  −
[Errno -1] Metadata file does not match checksum Trying other mirror.
  −
Error: failure: repodata/primary.xml.gz from dag: [Errno 256] No more mirrors to try.
  −
  −
To flush the up stream proxies, using wget, run:
  −
  −
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/filelists.xml.gz
  −
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz
  −
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/repomd.xml
  −
yum update
  −
  −
*Also, see the warning about updating yum if you are running a version earler than SME 7.1.1
  −
under [[SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled|Which_repositories_should_be_enabled]]
  −
  −
* An unclean shutdown during a system update can put the system into a state where it's difficult to recover.
  −
Try not to kick the power cord and use a UPS
  −
  −
* Where can I go to learn more about yum, and about how SME uses it?
  −
[[:SME_Server:Documentation:Technical_Manual:Chapter6#Yum_Repositories]]
      
===Hard Drives, RAID's, USB Hard Drives===
 
===Hard Drives, RAID's, USB Hard Drives===
Retrieved from "https://wiki.koozali.org/Special:MobileDiff/4267"

Navigation menu