[100140] in RedHat Linux List
Re: RH5.2 Install Exited Abnormally - Sig11 (Install BUG?)
daemon@ATHENA.MIT.EDU (Bill Carlson)
Wed Nov 18 16:54:28 1998
Date: Wed, 18 Nov 1998 15:52:09 -0600 (EST)
From: Bill Carlson <wcarlson@kinzemfg.com>
To: Redhat List redhat <redhat-list@redhat.com>
In-Reply-To: <3652FB21.CB2B451A@staffnet.com>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
On Wed, 18 Nov 1998, W. Wade, Hampton wrote:
> Update on this problem:
>
> 1) I tried the rpm -Uvh rpm*, rpm --rebuilddb -- still get Sig11.
> 2) The machine is a PII/300 Dell with no way to slow it down
> nor insert wait states. [suggested in the Sig11 FAQ]
> 3) The memory is a single 128 MB ECC DIM -- I swapped it with
> one from another WS400 -- still get Sig11. [suggested in
> the Sig11 FAQ]
> 4) /tmp/upgrade.log reports:
> error creating temporary file /tmp/var/tmp/rpm-tmp.41571
> 5) Test with only 1 CPU (install termination card): still get Sig11.
> 6) Test with cleaning out / so I have 40 MB free: still get Sig11.
> 7) Swap CPUs (use what was 2nd CPU as first, remove other
> CPU and install the termination card): still get Sig11.
> 8) Fix /var/tmp: /var/tmp was a symlink to /usr/var/tmp to save
> space on the root partition....: Seems to fix the problem!
>
> Redhat, some notes on the install software:
>
> A) The install software should check for the presence
> and free space in /tmp (/mnt/tmp) and /var/tmp (/mnt/var/tmp)
> PRIOR to installing and popup a warning message if there is
> a problem.
>
> B) Also note, if my RPM database was messed up (I had to reset
> the CPU in the middle of an install and the database was FU'ed),
> you get a Sig11 when the install script tries to determine the packages
> to install or tries to rebuild the database -- this is NOT
> GOOD. To fix, I had to reboot the old install and run rpm --rebuilddb.
>
Whoa! Did the original install work ok? ie, now SIG11's on a kernel
compile, etc.
Try running rpm -Va and see if it completes. This should verify all rpms
that are installed on your system, if it seg faults then you know the
problem lies somewhere in the rpm database.
Where in the install process are you getting the SIG11? Is it always at
the same spot?
Hang in There!
Bill Carlson | Opinions expressed are my own
KINZE Manufacturing, Inc. | not my employer's.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
