Rawhide...I've been seeing random script failures like this: exit code 255.
Preparing... ########################################### [100%] 1:libcap ########################################### [ 17%] error: %post(libcap-1.10-23.i386) scriptlet failed, exit status 255 2:libgtk-java ########################################### [ 33%] error: %post(libgtk-java-2.8.1-1.i386) scriptlet failed, exit status 255 3:libcap-devel ########################################### [ 50%] 4:libgtk-java-devel ########################################### [ 67%] 5:tar ########################################### [ 83%] error: %post(tar-1.15.1-11.i386) scriptlet failed, exit status 255 6:tftp-server ########################################### [100%] error: %post(tftp-server-0.41-1.i386) scriptlet failed, exit status 255 error: %postun(libcap-1.10-22.i386) scriptlet failed, exit status 255 error: %postun(libgtk-java-2.8.0-7.i386) scriptlet failed, exit status 255
All kinds of scripts will fail, including preun, postun, pre, post, and trigger. The exit status is always 255. Some of those scripts are really simple:
[root@cobra packages]# rpm -q libcap --scripts postinstall program: /sbin/ldconfig postuninstall program: /sbin/ldconfig
[root@cobra packages]# rpm -q tar --scripts postinstall scriptlet (using /bin/sh): /sbin/install-info /usr/share/info/tar.info.gz /usr/share/info/dir preuninstall scriptlet (using /bin/sh): if [ $1 = 0 ]; then /sbin/install-info --delete /usr/share/info/tar.info.gz /usr/share/info/dir fi
This causes chaos in my rpm databases, which I must later fix manually - it's really driving me crazy. I hadn't reported it so far, since I assumed it's a known problem, and will be fixed, but now I'm starting to suspect that only my system is broken... ideas?
On Sat, Nov 05, 2005 at 04:13:55PM -0500, Ivan Gyurdiev wrote:
Rawhide...I've been seeing random script failures like this: exit code 255.
.....
error: %post(libcap-1.10-23.i386) scriptlet failed, exit status 255 2:libgtk-java ########################################### [ 33%] error: %post(libgtk-java-2.8.1-1.i386) scriptlet failed, exit status 255
That may be related to messed up "alternatives". https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171843 was already mentioned today. See discussion there.
[root@cobra packages]# rpm -q tar --scripts postinstall scriptlet (using /bin/sh): /sbin/install-info /usr/share/info/tar.info.gz /usr/share/info/dir preuninstall scriptlet (using /bin/sh): if [ $1 = 0 ]; then /sbin/install-info --delete /usr/share/info/tar.info.gz /usr/share/info/dir fi
....
... but now I'm starting to suspect that only my system is broken... ideas?
Did you try saving such failig scripts to a file, editing results accordingly so that will be indeed a correct script to run and running that? Possibly with 'sh -x ...'? This may provide you with some clues why things are unhappy on your system. My particular test boxes seem to be doing mostly ok.
Michal
That may be related to messed up "alternatives". https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171843 was already mentioned today. See discussion there.
I know about the alternatives bug - I filed a very similar one. This is a different issue, which affects 80% of the rpms that I install.
... but now I'm starting to suspect that only my system is broken... ideas?
Did you try saving such failig scripts to a file, editing results accordingly so that will be indeed a correct script to run and running that? Possibly with 'sh -x ...'? This may provide you with some clues why things are unhappy on your system. My particular test boxes seem to be doing mostly ok.
The scripts are all different...one of them runs /sbin/ldconfig and fails...
On Sun, Nov 06, 2005 at 01:35:26AM -0500, Ivan Gyurdiev wrote:
The scripts are all different...one of them runs /sbin/ldconfig and fails...
Sure. You told us that; but you never gave any hints why this may be happening. Misconfigured, and/or missing labels, selinux? Hardware problems? Some libraries shot? Do you have some working crystal ball to lend?
It is not even clear if you did try to run failing scripts "by hand".
Michal
The scripts are all different...one of them runs /sbin/ldconfig and fails...
Sure. You told us that; but you never gave any hints why this may be happening. Misconfigured, and/or missing labels, selinux?
I have both kinds - misconfigured and missing labels... but in permissive mode this should not cause failures.
Hardware problems? Some libraries shot?
Not that I know of...
Do you have some working crystal ball to lend?
I'm not sure a crystal ball is required - I was just looking for some expertise on when RPM scripts can fail with exit code of 255. I suppose I could figure that out myself, but I thought it'd be simpler to ask...
It is not even clear if you did try to run failing scripts "by hand".
Running /sbin/ldconfig seems to work fine, with exit code of 0
-
Ivan Gyurdiev -
Michal Jaegermann