Re: up2date up2date

[Dag Wieers <dag wieers com>]

On Thu, 9 Mar 2006, Joshua Daniel Franklin wrote:

> On 3/8/06, Franco Saliola <saliola gmail com> wrote:
> > Hello.
> >
> > I am trying to upgrade RHEL4 U2 to U3. I ran 'up2date up2date' and I
> > got the following error message:
> >
> > error: %postun(up2date-4.4.50-4.i386) scriptlet failed, exit status 126
> >
> > And it is reproducable (I've had it happen on four out of four
> > machines). Has anyone seen this? I haven't seen anything on bugzilla
> > about this, but I may not be looking 'hard enough'.
> 
> Worked for me, try to see what it's doing with "rpm -q --scripts up2date"
> and try it by hand one of your machines:
> 
> postuninstall scriptlet (using /bin/sh):
> if [ "$1" -ge "1" ]; then
>     /etc/rc.d/init.d/rhnsd condrestart >/dev/null 2>&1
> fi

And if you find the culprit, report your findings to Red Hat 
(preferably with the proper fix attached).

Looking at the /etc/rc.d/init.d/rhnsd script, I several cases why it could 
fail:

 + /etc/rc.d/init.d/functions does not exist or is not readable (by root)
 + /etc/sysconfig/rhn/rhnsd exist but is not readable (by root)
 + Something fails in the killproc function (in functions)
 + Something fails in the daemon function (in functions)

You can test this by simply doing:

	sh /etc/rc.d/init.d/rhnsd condrestart

Most likely you have some sort of hardening script that improves the 
security of your systems but interfered with some assumptions the rhnsd 
script has.

That would explain why it fails for all four of your systems (but not for 
others).

Kind regards,
--   dag wieers,  dag wieers com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]