Topic: (Resolved) Yum hangs

[tviles]

Tell me what to search for. I have updates waiting. If I go into server manager and go to software installer and tell it to install updates it will but it will never complete. After so long an hour or so I just select reconfigure and let it reboot. Once the server comes back up it says system is up to date.
Thanks tviles

Should I try any of these? Below is from the faq file.
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.
find all the duplicate rpm's

rpm -qa | sort | less
Then remove all the duplicate rpm's

rpm -e --nodeps rpmname
Install the newest rpms

yum install rpmname
signal-event post-upgrade; signal-event reboot

[tviles]

2008-10-20 04:03:28.584402500 yum grouplist installed status 256
2008-10-20 04:03:32.312864500 Error: No Groups on which to run command
2008-10-20 04:03:32.370797500 yum grouplist updates status 256
2008-10-21 04:03:43.943804500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2008-10-21 04:03:44.003269500 yum list available status 51200
2008-10-21 04:03:44.550003500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2008-10-21 04:03:44.623378500 yum grouplist available status 51200
2008-10-21 04:03:45.180813500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2008-10-21 04:03:45.236419500 yum list installed status 51200
2008-10-21 04:03:50.818788500 Error: No Groups on which to run command
2008-10-21 04:03:50.877018500 yum grouplist installed status 256
2008-10-21 04:03:59.024028500 Error: No Groups on which to run command
2008-10-21 04:03:59.081162500 yum grouplist updates status 256

[cactus]

2008-10-20 04:03:28.584402500 yum grouplist installed status 256
2008-10-20 04:03:32.312864500 Error: No Groups on which to run command
2008-10-20 04:03:32.370797500 yum grouplist updates status 256
2008-10-21 04:03:43.943804500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2008-10-21 04:03:44.003269500 yum list available status 51200
2008-10-21 04:03:44.550003500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2008-10-21 04:03:44.623378500 yum grouplist available status 51200
2008-10-21 04:03:45.180813500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2008-10-21 04:03:45.236419500 yum list installed status 51200
2008-10-21 04:03:50.818788500 Error: No Groups on which to run command
2008-10-21 04:03:50.877018500 yum grouplist installed status 256
2008-10-21 04:03:59.024028500 Error: No Groups on which to run command
2008-10-21 04:03:59.081162500 yum grouplist updates status 256

Irrerelevant log file.

What version are you running? What does the following command do:

Code: [Select]

yum update

[cactus]

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:

Why is this configured? Are you running SME 6 still? Those RPM's in that repository are not compatible with SME Server 7.x and up at any way.

[tviles]

Why is this configured? Are you running SME 6 still? Those RPM's in that repository are not compatible with SME Server 7.x and up at any way.

I'm running SME 7.3 I quoted things to try from the faq.

[tviles]

Irrerelevant log file.

What version are you running? What does the following command do:

Code: [Select]

yum update

SME 7.3 is that what you are asking? I will try the yum update command after 5 pm today when most of the people leave. I also have updates waiting that came in last night to the server. So if I have problems again which log file do I look at?

[David Harper]

If you run yum update from the console (direct/Putty) it will tell you what is happening as it goes along -- no need for a log file.

[tviles]

OK the agency was too busy for me tonight to install updates and reboot the server. I can VPN in and use Putty to log in as root and issue command if that is what you are saying to do. I still cannot reboot server yet due to too many people working on reports still.

[tviles]

OK this is what I got. But I can't reboot on them just yet.

[root@shpdserver ~]# yum update
==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Loading "fastestmirror" plugin
Loading "installonlyn" plugin
Loading "smeserver" plugin
Setting up Update Process
Setting up repositories
smeaddons                 100% |=========================|  951 B    00:00
updates                   100% |=========================|  951 B    00:00
base                      100% |=========================| 1.1 kB    00:00
smeos                     100% |=========================| 1.9 kB    00:00
smeupdates                100% |=========================| 1.9 kB    00:00
Determining fastest mirrors
Reading repository metadata in from local files
Excluding Packages from CentOS - updates
Finished
Excluding Packages from CentOS - os
Finished
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for httpd-suexec to pack into transaction set.
httpd-suexec-2.0.52-41.en 100% |=========================|  24 kB    00:00
---> Package httpd-suexec.i386 0:2.0.52-41.ent.2.centos4 set to be updated
---> Downloading header for httpd to pack into transaction set.
httpd-2.0.52-41.ent.2.cen 100% |=========================|  65 kB    00:00
---> Package httpd.i386 0:2.0.52-41.ent.2.centos4 set to be updated
---> Downloading header for mod_ssl to pack into transaction set.
mod_ssl-2.0.52-41.ent.2.c 100% |=========================|  27 kB    00:00
---> Package mod_ssl.i386 1:2.0.52-41.ent.2.centos4 set to be updated
--> Running transaction check

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Updating:
 httpd                   i386       2.0.52-41.ent.2.centos4  updates           902 k
 httpd-suexec            i386       2.0.52-41.ent.2.centos4  updates            31 k
 mod_ssl                 i386       1:2.0.52-41.ent.2.centos4  updates           100 k

Transaction Summary
=============================================================================
Install      0 Package(s)
Update       3 Package(s)
Remove       0 Package(s)
Total download size: 1.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): httpd-suexec-2.0.5 100% |=========================|  31 kB    00:00
(2/3): httpd-2.0.52-41.en 100% |=========================| 902 kB    00:07
(3/3): mod_ssl-2.0.52-41. 100% |=========================| 100 kB    00:00
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
smeserver trap pre-install: httpd-suexec
smeserver trap pre-install: httpd
smeserver trap pre-install: mod_ssl
  Updating  : httpd-suexec                 ######################### [1/6]
  Updating  : httpd                        ######################### [2/6]
  Updating  : mod_ssl                      ######################### [3/6]
  Cleanup   : httpd-suexec                 ######################### [4/6]
  Cleanup   : httpd                        ######################### [5/6]
  Cleanup   : mod_ssl                      ######################### [6/6]
Migrating existing database networks
Migrating existing database yum_available
Migrating existing database dar2
Migrating existing database accounts
Migrating existing database backups
Migrating existing database spamassassin
Migrating existing database mailpatterns
Migrating existing database yum_installed
Migrating existing database yum_repositories
Migrating existing database yum_updates
Migrating existing database hosts
Migrating existing database configuration
Migrating existing database domains
smeserver trap post-install: httpd-suexec
smeserver trap post-install: httpd
smeserver trap post-install: mod_ssl

Updated: httpd.i386 0:2.0.52-41.ent.2.centos4 httpd-suexec.i386 0:2.0.52-41.ent.2.centos4 mod_ssl.i386 1:2.0.52-41.ent.2.centos4
Complete!
==============================================================
WARNING: You now need to run BOTH of the following commands
to ensure consistent system state:

signal-event post-upgrade; signal-event reboot

You should run these commands unless you are certain that
yum made no changes to your system.
==============================================================

[tviles]

Yup that worked thanks.

But now I am getting this error in the messages log file.

Probably should post this over in contribs. Trying to do DAR2 backup.
Nov 18 21:05:09 shpdserver e-smith-bg: Connecting /mnt/dar2/pdserver to //dave/ServerBackup
Nov 18 21:05:10 shpdserver e-smith-bg: 6064: tree connect failed: ERRDOS - ERRnomem (Insufficient server memory to perform the requested function.)
Nov 18 21:05:10 shpdserver e-smith-bg: SMB connection failed

[David Harper]

This may be resolved after a reboot and post-upgrade run. Updates can do some pretty serious stuff to the system.

[cactus]

This may be resolved after a reboot and post-upgrade run. Updates can do some pretty serious stuff to the system.

Indeed, always do this as shortly after updates as possible. If there is no time to reboot, refrain from updating.