Bug 756406 - [abrt] yum-3.4.3-5.fc16: sqlutils.py:166:executeSQLQmark:OperationalError: database is locked
Summary: [abrt] yum-3.4.3-5.fc16: sqlutils.py:166:executeSQLQmark:OperationalError: da...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Packaging Toolset Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bb0c5704ce00d0499f6aeb8c857...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-23 13:22 UTC by Oliver Henshaw
Modified: 2014-01-21 23:20 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-30 09:18:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Oliver Henshaw 2011-11-23 13:22:38 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        /usr/bin/python /usr/bin/yum history list
comment:        'yum history list' while packagekit (yumBackend.py) is running.
executable:     /usr/bin/yum
kernel:         3.1.1-1.fc16.x86_64
reason:         sqlutils.py:166:executeSQLQmark:OperationalError: database is locked
time:           Tue 22 Nov 2011 20:31:03 GMT
uid:            500
username:       oliver

backtrace:
:sqlutils.py:166:executeSQLQmark:OperationalError: database is locked
:
:Traceback (most recent call last):
:  File "/usr/bin/yum", line 29, in <module>
:    yummain.user_main(sys.argv[1:], exit_code=True)
:  File "/usr/share/yum-cli/yummain.py", line 309, in user_main
:    errcode = main(args)
:  File "/usr/share/yum-cli/yummain.py", line 140, in main
:    result, resultmsgs = base.doCommands()
:  File "/usr/share/yum-cli/cli.py", line 462, in doCommands
:    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
:  File "/usr/share/yum-cli/yumcommands.py", line 2473, in doCommand
:    ret = base.historyListCmd(extcmds)
:  File "/usr/share/yum-cli/output.py", line 1775, in historyListCmd
:    tids, printall = self._history_list_transactions(extcmds)
:  File "/usr/share/yum-cli/output.py", line 1732, in _history_list_transactions
:    old = self.history.last()
:  File "/usr/lib/python2.7/site-packages/yum/history.py", line 1148, in last
:    ret = self.old([], 1, complete_transactions_only)
:  File "/usr/lib/python2.7/site-packages/yum/history.py", line 1097, in old
:    executeSQL(cur, sql, params)
:  File "/usr/lib/python2.7/site-packages/yum/sqlutils.py", line 166, in executeSQLQmark
:    return cursor.execute(query)
:OperationalError: database is locked
:
:Local variables in innermost frame:
:cursor: <sqlite3.Cursor object at 0x1c0de30>
:query: 'SELECT tid,\n                         trans_beg.timestamp AS beg_ts,\n                         trans_beg.rpmdb_version AS beg_rv,\n                         trans_end.timestamp AS end_ts,\n                         trans_end.rpmdb_version AS end_rv,\n                         loginuid, return_code\n                  FROM trans_beg JOIN trans_end USING(tid) ORDER BY beg_ts DESC, tid ASC LIMIT 1'
:params: None

Comment 1 Dan Mashal 2012-04-15 20:36:52 UTC

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

Comment 2 Adam Williamson 2012-04-19 02:34:12 UTC
This is also clearly not a dupe of 812668. It's a traceback, not yum's informational note about the yum lock. It may actually be a different lock, though that's not entirely clear.

Comment 3 Fedora Admin XMLRPC Client 2012-04-27 15:28:31 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Dan Mashal 2012-05-31 03:50:55 UTC
810530

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

Comment 5 Adam Williamson 2012-05-31 05:47:36 UTC
No, still wrong. As per comment #2. This is a traceback. The yum lock message is not a traceback.

Comment 6 Dan Mashal 2012-07-01 19:59:40 UTC
FWIW I do not receive any more yum issues anymore. 

I have experienced this specific error in the past but I no longer do.


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