Bug 518125 - Zypper hangs on install waiting for transaction lock
Summary: Zypper hangs on install waiting for transaction lock
Status: RESOLVED DUPLICATE of bug 510788
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: libzypp (show other bugs)
Version: Milestone 3
Hardware: 32bit Other
: P3 - Medium : Critical (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-01 07:54 UTC by Atri Bhattacharya
Modified: 2009-07-29 11:40 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Zypper.log file relating to problem (3.87 MB, text/x-log)
2009-07-02 22:46 UTC, Atri Bhattacharya
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Atri Bhattacharya 2009-07-01 07:54:04 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.0) Gecko/20090617 SUSE/3.5.0-2.2 Firefox/3.5

While installing a large number of packages (I was trying to install the gnome patterns from the internet) zypper hangs (after some packages have been installed) attempting to install a package. This happens randomly and zypper actually shows that the package has been retrieved successfully at 0 B/s (which is strange, considering it shows the correct speed for all earlier packages), but the install hangs at 0%. Only a Ctrl-C Ctrl-C sequence works and the following message is then shown

"Installation of gnome-panel-2.26.2-1.9 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: waiting for transaction lock on /var/lib/rpm/__db.000"

Problem also occurs with YAST, in which case only killing y2base as root is the only way out. Once this error happens, it keeps re-occurring every time the software management is used subsequently. One has to restart for the problem to disappear.

Reproducible: Sometimes

Steps to Reproduce:
1.Select a large number of packages to install using zypper or YAST.
2.At some stage process hangs trying to install a package at 0%
3.Kill install procedure and try again. Error persists.
4.Restart, and attempt installation. Works until error occurs randomly again.
Actual Results:  
Installation fails with message:
"(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: waiting for transaction lock on /var/lib/rpm/__db.00"

Expected Results:  
Installation successful.
Comment 1 Jan Kupec 2009-07-01 08:54:58 UTC
Can you please try to reproduce it and while it hangs do 'pstree' in other terminal and look for useradd or usermod. If you find them, this is bug 510788. If not, please attach your zypper.log. Maybe installation of the previous package crashed and thus did not release the lock? But then you should see some error message in the output... let's see.
Comment 2 Michael Schröder 2009-07-01 09:14:45 UTC
(I doubt that the error has something to do with the "waiting for transaction lock" message, it's just written to stderr so YaST displays it. Plus, the lock is process bound, so the lock is always released on a crash.)
Comment 3 Atri Bhattacharya 2009-07-02 22:46:35 UTC
Created attachment 302619 [details]
Zypper.log file relating to problem
Comment 4 Atri Bhattacharya 2009-07-02 22:47:59 UTC
I have not been able to reproduce the problem yet. In the meanwhile I have attached the zypper.log file.
Comment 5 Jan Kupec 2009-07-29 11:40:26 UTC
Thanx. The log does not provide any more clue, we'd need to reproduce it and check where exactly it hangs. Bug 510788 is the prime suspect, so i'll mark this report as duplicate of that bug. Please reopen, if it happens again and 'pstree' does not show 'usermod' or 'useradd' under the hanging 'rpm' process.

*** This bug has been marked as a duplicate of bug 510788 ***