Hello,
Well: In the end I've deleted all patches and re-installed pk2 from
scratch. This went painless. I've used dupatch to delete all patches,
did *not* rebuild a new kernel, started dupatch again and installed
pk2 and finally build a new kernel. The machine is up again and
I hope that the system-hangs are gone. One small glitch: I has
restored the root crontab to the version I had before installing pk3.
Thanks to the following people (sorry if I forgot someone) for their
replies which I'm appending below:
Raymond.Fagnon_at_firstunion.com
Stephen L LaBelle <labelles_at_mscd.edu>
Larry Griffith <larry_at_cs.wsc.ma.edu>
Yaacov Fenster <fenster_at_zk3.dec.com>
Thanks everybody // Tom
---------------------------------------------------------------
From: Raymond.Fagnon_at_firstunion.com
I am pretty sure you can do it manually. Just find on the system were dupatch
put the rollback and copy back to its place. The only problem is the dupatch
database will not be current. If you have a junker machine try it on there first
before doing it on your productin box.
---------------------------------------------------------------
From: Raymond.Fagnon_at_firstunion.com
Try reinstalling pk2, if it doesn't help you then mv the dupatch database dir
/var/adm/patch to let dupatch think that it is a
virgin machine. Then reinstall pk2. Your cat's are they named after famouse
composers?
---------------------------------------------------------------
From: Stephen L LaBelle <labelles_at_mscd.edu>
The suggested way to remove patches via dupatch is to remove them
all. That assumes that you made the patches reversible.
You them put patches back to return to a certain patch level. I had
to do this once and it worked out but anytime you deal with patches
it can be tediuos.
Steve
---------------------------------------------------------------
From: Larry Griffith <larry_at_cs.wsc.ma.edu>
Dear Tom,
I tried deleting patches ONCE. I had an even worse experience
than you did. When I deleted a patch, I had to delete the patches
depending on it, just as you did. This went through about 10
iterations, at which point the operating system collapsed and I had to
do a complete reinstall.
I normally install patches by attempting to install all
patches that aren't obviously inappropriate for my systems (3000/300s
with a 3000/600, hopefully soon to be upgraded) and let dupatch select
the ones that shouldn't be installed. Despite the fact that the
client machines are essentially the same (except for total memory),
the process seems to yield different results on each machine. I would
guess there is something inherently unstable in the patch system
somewhere.
My advice, painful as it is, is to do a reinstall. Ugh...
Larry
---------------------------------------------------------------
From: Yaacov Fenster - System Engineering Troubleshooting and other
miracles <fenster_at_zk3.dec.com>
dupatch also has a command line interface where you can specify patches
to be deleted. For details try dupatch -help.
Yaacov
---------------------------------------------------------------
ORIGINAL POSTING BELOW
Hi,
I'm experiencing system hangs under heavy load on our DU 4.0E, pk3
system (an Alpha PC 164LX box with 512MB RAM). The system hangs did not
occur before installing pk3 where only pk2 was installed. With "system
hangs" I mean that the machine just gets stuck. All I can do is to reboot
it by pushing the reset button. There are not log entries whatsoever.
So I decided to take a closer look at the patches and found some patches
which sound like they could lead to something like this.
These are OSFPAT0036000435 and
OSFPAT0042900435.
Well: Has anyone ever tried to delete patches with dupatch? It's a
nightmare and a perfect example for how not to design a user interface.
First: The patches cannot be selected by number. Instead you have to
read though the complete unsorted 200+ entry list in order to find the
appropriate patch number to delete. Second: If the patch dependency check
fails, the message scrolls by so fast that you have a hard time to
push CTRL-S fast enough to catch it.
While I managed to delete OSFPAT0036000435 I just can't delete
OSFPAT0042900435 because some other patches depend on it. When I try to
select all of the patches which depend on each other, I still get some
messages stating that this and that patch can't be deleted because
some other patch depends on it.
To make a long story short: Is there any other way to delete this
patch OSFPAT0042900435? I've already tried "setld -d" but it says
that patches can only be deleted with dupatch.
Or should I try to go back to pk2? If so, how would I do this?
Delete *all* patches and re-install pk2 ?
Thanks // Tom
--
--------------------------------------------------------------------------
Dr. Tom Leitner Dept. of Communications
Graz University of Technology,
e-mail : tom_at_radar.tu-graz.ac.at Inffeldgasse 12
Phone : +43-316-873-7455 A-8010 Graz / Austria / Europe
Fax : +43-316-463-697
Home page : http://wiis.tu-graz.ac.at/people/tom.html
PGP public key on : ftp://wiis.tu-graz.ac.at/pgp-keys/tom.asc or send
mail with subject "get Thomas Leitner" to pgp-public-keys_at_keys.pgp.net
--------------------------------------------------------------------------
Before we have the paperless office, we have the paperless toilet!
Received on Mon Jan 03 2000 - 18:28:02 NZDT