Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 101080
Summary: | using software installer or rpm -i from a console fails (intermittently) | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux Beta | Reporter: | Elton Woo <elwoo> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED DUPLICATE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | beta1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:57:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Elton Woo
2003-07-28 22:54:51 UTC
Can you supply details on "sometimes this works"? Otherwise I have little hope of reproducing. You might try rm -f /var/lib/rpm/__db* to remove locks. actually, it only worked twice, other times, I cannot install *anything* ... INCLUDING loading a cd with autorun. Using this latter option, the dialog pops up, then says "checking system for installed packages...", then it abends. I'll try seeing if it's stale locks as suggested, and report back. logged in to a root console, and watch this ---> [root@dhcp-133-74 root]# ls /var/lib/rpm/ Basenames __db.003 Installtid Provideversion Sha1header Conflictname Dirnames Name Pubkeys Sigmd5 __db.001 Filemd5s Packages Requirename Triggername __db.002 Group Providename Requireversion [root@dhcp-133-74 root]# rm -f /var/lib/rpm/_db* [root@dhcp-133-74 root]# ls /var/lib/rpm/ Basenames __db.003 Installtid Provideversion Sha1header Conflictname Dirnames Name Pubkeys Sigmd5 __db.001 Filemd5s Packages Requirename Triggername __db.002 Group Providename Requireversion [root@dhcp-133-74 root]# ... looks like the stale locks aren't deleted, even though I *am* su. even going directly into the directory and trying to delete the file *without* using wildcards, and the stale locks *aren't* removed ---> ]# cd /var/lib/rpm [root@dhcp-133-74 rpm]# ls Basenames __db.003 Installtid Provideversion Sha1header Conflictname Dirnames Name Pubkeys Sigmd5 __db.001 Filemd5s Packages Requirename Triggername __db.002 Group Providename Requireversion [root@dhcp-133-74 rpm]# rm -f _db.* [root@dhcp-133-74 rpm]# ls Basenames __db.003 Installtid Provideversion Sha1header Conflictname Dirnames Name Pubkeys Sigmd5 __db.001 Filemd5s Packages Requirename Triggername __db.002 Group Providename Requireversion [root@dhcp-133-74 rpm]# rm -f _db.001 [root@dhcp-133-74 rpm]# ls Basenames __db.003 Installtid Provideversion Sha1header Conflictname Dirnames Name Pubkeys Sigmd5 __db.001 Filemd5s Packages Requirename Triggername __db.002 Group Providename Requireversion The only thing "different" WRT installing the beta, was that I chose "high" security, rather than the default "medium" security level, but I should still be able to delete files as "su" shouldn't I? There is another possible explanation, that a running process is recreating the lock files as soon as you delete them. Make sure there are no live rpm etc. processes running first. Good point. I am quite sure that there was no other rpm process running. In fact, as I am typing this, I tried again. I'm *positive* that there is _at this very moment_ NO rpm process running, since the machine was shut down (and powered off), until I returned home from the gym a while ago. I still cannot remove those stale locks. FWIW, I login to the console with "su -" . An attempt as root, without the root path gives me the same result: ]$ su Password: [root@dhcp-133-74 abe]# cd /var/lib/rpm [root@dhcp-133-74 rpm]# rm -f _db.* [root@dhcp-133-74 rpm]# ls Basenames __db.003 Installtid Provideversion Sha1header Conflictname Dirnames Name Pubkeys Sigmd5 __db.001 Filemd5s Packages Requirename Triggername __db.002 Group Providename Requireversion [root@dhcp-133-74 rpm]# You are trying to remove __db* (2 underscores) and not _db* as your post suggests? Bingo! I *was* trying with *one* underscore instead of *two*. NOW, I am able to delete those stale locks. NOTE: on my screen (1024 x 768), it's a bit difficult to diffrentiate, since there is no visible space between the two underscores. Now to try rpm again.... I tried installing via automount (Disk 1) again. Place disk in my DVD drive /dev/hdd alias /mnt/cdrom The dialog abends "checking system status..." (*blooey*!!!). When I go to a root console I see the same three locked files have been recreated: __001.db,__002.db, and __003.db. I delete them ---> root]# ls /var/lib/rpm Basenames __db.003 Installtid Provideversion Sha1header Conflictname Dirnames Name Pubkeys Sigmd5 __db.001 Filemd5s Packages Requirename Triggername __db.002 Group Providename Requireversion [root@dhcp-133-74 root]# rm -f /var/lib/rpm/__db.* [root@dhcp-133-74 root]# ls /var/lib/rpm Basenames Group Providename Requireversion Conflictname Installtid Provideversion Sha1header Dirnames Name Pubkeys Sigmd5 Filemd5s Packages Requirename Triggername [root@dhcp-133-74 root]# ... and try with a different drive, my cdwriter (/dev/hdc alias /mnt/cdrom1). SAME result. QED: the problem is reproducible and consistent. As a test, I mounted Disk 2, and clicked on the taipei fonts package, which installed without any problems. I guess the problem lies with autorun and rpm? Also, only Disk 1 will load as autorun. Is this the same problem as described in bug 100445? The first paragraph of comment #1 sounds similar. Yes. I also encounter that problem (as in bug 100445). I insert a CD and I say "yes" to autorun, then select a package to install. The installer then asks me to insert (say) Disk 2 (which I place in my other drive) e.g. autorun from /dev/cdrom1 (cdwriter), and insert the needed disk in /dev/cdrom (DVD drive). The dialog will keep popping up: "please insert Disk 2", I click OK, and there might be a slight flicker of the drive light. The dialog comes up several times, and eventually after several "OK's", it disappears _without any error message_. *** This bug has been marked as a duplicate of 100445 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |