[rhn-users] RE: Up2date Problem

Tue Jul 25 19:09:04 UTC 2006

Thanks Terry.  Makes me feel a little better that I'm not the only one and
that it wasn't some type of rookie mistake.  Thanks again. 

-----Original Message-----
From: Terry Turner [mailto:support at oit.gatech.edu] 
Sent: Tuesday, July 25, 2006 1:47 PM
To: rhn-users at redhat.com
Cc: mark.ballard at murraystate.edu
Subject: Re: Up2date Problem

There is a known bug related to the pvm package...

  http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=191841

> Date: Tue, 25 Jul 2006 10:54:30 -0500
> From: "Mark R. Ballard" <mark.ballard at murraystate.edu>
> Subject: [rhn-users] Up2date Problem
> To: <rhn-users at redhat.com>
> Message-ID: <01e901c6b002$9e612e70$b49ff9d8 at msunet2k.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> I'm fairly new to being a Linux administrator so please forgive how 
> green I am, but here's my problem.
> I ran up2date (as root) on one of my servers yesterday that aborted 
> during the installation step and I don't think everything that got 
> downloaded was installed.
> I got the following error:
>
>     127:pvm                    ###########################################
> [100%]
>     error: unpacking of archive failed on file
> /usr/share/pvm3/bin/LINUXI386: cpio: rename
>     Error on option --makefile-uninstall-rule: unknown option.
>     Run 'gconftool-2 --help' to see a full list of available command 
> line options.
>     error reading information on service keytable: No such file or
directory
>     error: %trigger(kbd-1.08-10.2) scriptlet failed, exit status 1
>     Shutting down NFS mountd: [FAILED]
>     Shutting down NFS daemon: [FAILED]
>     Shutting down NFS quotas: [FAILED]
>     Shutting down NFS services:  [  OK  ]
>     Stopping NFS statd: [  OK  ]
>     groupdel: group rpm does not exist
>     There was a fatal RPM install error. The message was:
>     There was a rpm unpack error installing the package: 
> pvm-3.4.5-6_EL3
>
> I then ran up2date again and it installed a few more packages and said 
> I was up2date, but it never attempted to reinstall pvm-3.4.5-6_EL3.  I 
> still have a ton of rpm and hdr files in /var/spool/up2date.  Does 
> up2date remove those files once they are installed?
>
> Also, my up2date problem seems to have removed several services (i.e., 
> sshd, crond, kudzu, nfs, nfslock, etc.) from the appropriate run 
> levels (rc0.d - rc6.d).
>
> Any help would be greatly appreciated.
>
> Thanks,
>
> Mark
> -------------- next part -------------- An HTML attachment was 
> scrubbed...
> URL:
>
https://www.redhat.com/archives/rhn-users/attachments/20060725/15d03699/atta
chment.html
>
> ------------------------------
>
> _______________________________________________
> rhn-users mailing list
> rhn-users at redhat.com
> https://www.redhat.com/mailman/listinfo/rhn-users
>
> End of rhn-users Digest, Vol 29, Issue 26
> *****************************************

Here's what some of our RHN users have seen:

> Friday morning (July 21), several updates for RHEL 3 (update *?) 
> popped up.... Our RHEL 3 machines tried to apply these updates 
> automatically, and they seem to have reached a problem when attempting 
> to update elfutils.  Following is the end of my /var/log/up2date file:
> [Fri Jul 21 06:28:05 2006] up2date deleting /var/spool/up2date/ 
> up2date-4.4.69-20.i386.rpm [Fri Jul 21 06:28:05 2006] up2date deleting 
> /var/spool/up2date/ up2date-4.4.69-20.i386.hdr [Fri Jul 21 06:28:05 
> 2006] up2date deleting /var/spool/up2date/ 
> up2date-gnome-4.4.69-20.i386.rpm [Fri Jul 21 06:28:05 2006] up2date 
> deleting /var/spool/up2date/ up2date-gnome-4.4.69-20.i386.hdr [Fri Jul 
> 21 06:28:05 2006] up2date deleting /var/spool/up2date/ 
> rhnlib-1.8.7-3.noarch.rpm [Fri Jul 21 06:28:05 2006] up2date deleting 
> /var/spool/up2date/ rhnlib-1.8.7-3.noarch.hdr [Fri Jul 21 06:28:05 
> 2006] up2date updating login info [Fri Jul 21 06:28:05 2006] up2date 
> logging into up2date server [Fri Jul 21 06:28:06 2006] up2date 
> successfully retrieved authentication token from up2date server [Fri 
> Jul 21 06:28:11 2006] up2date installing packages:
> ['elfutils-0.94.1-2', 'elfutils-devel-0.94.1-2', 'elfutils- 
> libelf-0.94.1-2', 'elfutils-libelf-devel-0.94.1-2']
>
> Now, if I try running up2date -l, I get the following error:
> Traceback (most recent call last):
>   File "/usr/sbin/up2date", line 11, in ?
>     import rpm
> ImportError: libelf.so.1: cannot open shared object file: No such file 
> or directory
>
> Of course, this means that if I try to run rpm, I also get an error:
> rpm: error while loading shared libraries: libelf.so.1: cannot open 
> shared object file: No such file or directory
>
> And I cannot find libelf.so.1 on my machine.
>
> Do you know of the best way to solve this problem?

====================================================

> Here is what I am finding on the nodes of a cluster running Redhat 3.0
>
> On the front node, some services such as nfsd, ssh were disabled and 
> had to be re-enabled using chkconfig.
>
> On the cluster nodes, the following symptoms are being detected:
>
> [root at node4 /]# up2date -u -f
> Traceback (most recent call last):
>   File "/usr/sbin/up2date", line 11, in ?
>     import rpm
> ImportError: libelf.so.1: cannot open shared object file: No such file 
> or directory
>
>
> The library file /usr/lib/libelf-0.9x.... is missing.
>
> Upon re-installing and recreating libelf, update starts to work again. 
> Running update -u -f creates problem and seems to correct the rpm 
> database.
>
> The best solution is to remove the pvm package and run again the 
> up2date -u -f command.
>
>
>> I am starting to find some references about a problem with Update 8.0 
>> of Redhat 3.0 
>> =====================================================================
>> ======
>>  error: unpacking of archive failed on file
>>     /usr/share/pvm3/bin/LINUXI386: cpio:  rename failed - Is a 
>> directory 
>> =====================================================================
>> ======= This seems to leave the system in a bad state. You might want 
>> to check on this.
>> Might want to check some of the posts (07/21/2006) on
>>
>> http://tinyurl.com/fzku2
>>

"ES3 update 8 has severe problems with pvm"

http://blog.gmane.org/gmane.linux.redhat.release.taroon.general