 | | | ES3 update 8 has severe problems with "pvm " | ES3 update 8 has severe problems with "pvm " 2006-07-24 - By Ben
Back
On Fri, 21 Jul 2006, Lawrence Houston wrote:
> On Fri, 21 Jul 2006, James Leinweber wrote:
>
>> On any server with the "pvm" package installed, which seems to creep
>> in by default, running "up2date -u" on 2006-July-20 (See http://uly-20.ora-code.com) dies with the
>> message:
>>
>> error: unpacking of archive failed on file
>> /usr/share/pvm3/bin/LINUXI386: cpio: rename failed - Is a directory
>>
>> This leaves the system in a very unfortunate state, with the updates
>> partially applied, and about 50 RPM's missing in action, including
>> rather important things such as "openssh-server". With a lot of
>> hand work using "rpm", 'find ... -name "*.rpm*" -print' and the like I
>> was able to get a couple of systems past that.
>>
>> a) is anyone else having this problem?
>
> July 20th I was Upgrading a Remote WS3-U7 System (with all previous updates
> already applied), using the Graphical version of UP2DATE via NoMachine's NX
> Client. Part way through the Upgrade there was an error related to the pvm
> update (in the Graphical Mode I did NOT see/remember the detailed Error
> Message which James saw/noted), so I restarted UP2DATE to complete the WS3-U8
> Upgrade (which generated no further errors and completed with RHN Icon going
> back to its "comforting" Blue Checkmark)...
I got the following on 2006-07-20:
...
154:pvm ########################################### [100%]
error: unpacking of archive failed on file /usr/share/pvm3/bin/LINUXI386:
cpio: rename
error reading information on service keytable: No such file or directory
error: %trigger(kbd-1 (See http://kbd-1.ora-code.com).08-10.2) scriptlet failed, exit status 1
Shutting down smartd: [FAILED]
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 (See http://pvm-3.ora-code.com).4.5-6_EL3
I also found no SSHd running even though at the beginning of the up2date I'd
seen the SSHd stopped and restarted. I had to go in and manually start it
from console to regain remote connection. Although I now have the bluetick
for this machine in RHN I really don't know if the box is fully patched now
other than by laboriously going through the 180-odd packages to see if
they're all at the right level.
> [...]
>> b) BEWARE! You probably want to avoid running "up2date" on systems
>> with "pvm" installed unless you are a masochist.
>
> According to the rpmpkgs Log Files pvm-3 (See http://pvm-3.ora-code.com).4.4-22.i386.rpm was installed on the
> system at the WS3-U7 Level and the WS3-U8 Upgrade had attempted to update
> using pvm-3 (See http://pvm-3.ora-code.com).4.5-6_EL3.i386.rpm (which is NO longer in the system and I did
> NOT explicitly remove it myself)??? There were only a handful of *.rpmnew
> Files on the System and they all seems older than the WS3-U8 Upgrade
> anyway... The effected system is a RHEL WS3 Pre-installed DELL System, so
> possibly DELL had included the pvm RPM (PVM is NOT something I Installed,
> Require or Use)???
I've got kickstart-built RHEL3u7 boxes (Dell) which appear to have pvm
installed. For the moment I'm just taking it off everything until I see a
need to put it back, or I've upgraded my kickstart point to RHEL3u8 and
built boxes using that successfully.
I'm worried about this loss of SSH connectivity, but I don't think it's
connected to the pvm snafu.
Of course, now I need to think about those machines with MySQL 5 on them and
this perl-DBD-MySQL thing...
Ben
--
Unix Support, MISD, University of Cambridge, England
Plugger of wire, typer of keyboard, imparter of Clue
Life Is Short. It's All Good.
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|