Bug 65157 - installation fails with exit status 2
Summary: installation fails with exit status 2
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i686 Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-05-18 19:30 UTC by Sebastian Krieg
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-01 11:16:39 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Sebastian Krieg 2002-05-18 19:30:09 UTC
From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; 
Konqueror/3.0.0-10; Linux) 
Description of problem: 
RPM-install failed with: 
1. Unabele to identify operating system" 
2. "%pre scriptlet failed (2)" 
Version-Release number of selected component (if 
applicable): 4.0.4-7x.18 
How reproducible: 
Steps to Reproduce: 
1. go to RPM-destination 
2. rpm -ivh <package> 
Actual Results:  Preparing...   ###### [100%] 
Unable to identify operating system 
error: execution of %pre scriptlet from <package> 
failed, exit status 2 
error: install: %pre scriptlet failed (2), skipping 
Expected Results:  the package should be installed 
Additional info: 
It`s a basic feature, that's not work...

Comment 1 Jeff Johnson 2002-05-21 15:59:04 UTC
What is <package>? This is a problem with
that <package>'s %pre, not with rpm.

Comment 2 Sebastian Krieg 2002-05-22 17:08:31 UTC
<package> decribes every RPM-package and was used as a 
wildcard. But the installation routine was sucessful.

Comment 3 Jeff Johnson 2002-05-22 17:10:52 UTC
If it's a problem with every package scriptlet,
then you /bin/sh is borked somehow.

Comment 4 Sebastian Krieg 2002-05-26 07:21:07 UTC
What do You mean with "borked". If You mean "broken",  
what's broken on the shell /bin/bash? 
Just I've done the "rpm --rebuilddb" failing with an 
error: "Item 146 on page 581 hashes incorrectly. db4 
error (-30979) from db->verify: DB_VERIFY: Database 
verification failed."

Comment 5 Jeff Johnson 2002-05-26 17:03:02 UTC
Yes broken.

Judging from your problems, I suggest you start looking
for causes outside of rpm, like bad disk/memory.

Meanwhile, you might try (as root, you need db*-utils installed)
	cd /var/lib
	tar czvf /tmp/rpmdb.tar.gz rpm	# <-- just in case
	cd rpm
	db_verify Packages
	mv Packages Packages-ORIG
	db_dump Packages-ORIG | db_load Packages
	rpm --rebuilddb

Comment 6 Sebastian Krieg 2002-05-28 15:45:46 UTC
I found the file "PACKAGE" in the 
rpmdb-redhat.i386.rpm. I run the commands in 
/usr/lib/rpmdb/redhat/ with no shown errors. 
The command "rpm --rebuilddb" works, but the following 
command "rpm -ivh webmin-0.88.rpm" failed with the 
known error. 
The errors outside from rpm, this should be a bad 
installation-cd (corrupt data) or errors at my hard 

Comment 7 Sebastian Krieg 2002-05-28 20:10:48 UTC
I have done "rpm -V rpm". I got this message: 
.....UG. c /var/lib/rpm/Basenames 
.....UG. c /var/lib/rpm/Conflictname 
.....UG. c /var/lib/rpm/Dirnames 
.....UG. c /var/lib/rpm/Filemd5s 
.....UG. c /var/lib/rpm/Group 
.....UG. c /var/lib/rpm/Installtid 
.....UG. c /var/lib/rpm/Name 
.....UG. c /var/lib/rpm/Packages 
.....UG. c /var/lib/rpm/Providename 
.....UG. c /var/lib/rpm/Provideversion 
.....UG. c /var/lib/rpm/Requirename 
.....UG. c /var/lib/rpm/Requireversion 
.....UG. c /var/lib/rpm/Sha1header 
.....UG. c /var/lib/rpm/Sigmd5 
.....UG. c /var/lib/rpm/Triggername 
.....UG. c /var/lib/rpm/__db.001 
.....UG. c /var/lib/rpm/__db.002 
Calling "rpm -V bash" brings nothing... Is the only way 
installing rpm as a tgz.-file?

Comment 8 Jeff Johnson 2002-06-21 19:57:50 UTC
I'm not going to be able to reproduce this problem.

Comment 9 Sebastian Krieg 2002-08-01 11:16:32 UTC
Hi jbj,

for your info and your help:

I4ve installed the system new and It works. 
I saw, that there are different filesystems between the buggy system and now. 
At the buggy system the / partition was an ext3 and the <package> I4d tried to 
install was on an ext2 filesystem. I used this filesystem as an backup.

During mounting this "backup"-filesystem I got some problems with e2fsck. I 
think, that4s the error4s reason. After checkng the ext2-"backup" filesystem 
all the packages from the "backup"-filesystem shows this error.

That4s why I think, mounting an ext2-filesystem in an ext3-system may be 
dangerous for the rpm-package saving there.

You will see, I have an explanation, thank you for your patience.

Greetings willicat

Note You need to log in before you can comment on or make changes to this bug.