PDA

View Full Version : A different yum error


glennzo
26th September 2009, 09:31 AM
There is no lack of yum errors around here. Could someone please translate the following into Swahili for me? That way, I can probably understand it a little better.:rolleyes:
Transaction Test Succeeded
Running Transaction
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 315, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 263, in main
return_code = base.doTransaction()
File "/usr/share/yum-cli/cli.py", line 492, in doTransaction
resultobject = self.runTransaction(cb=cb)
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 1081, in runTransaction
self.history.end(rpmdbv, 2, errors=errors)
File "/usr/lib/python2.6/site-packages/yum/history.py", line 385, in end
self._log_errors(errors)
File "/usr/lib/python2.6/site-packages/yum/history.py", line 351, in _log_errors
(tid, msg) VALUES (?, ?)""", (self._tid, error))
File "/usr/lib/python2.6/site-packages/yum/sqlutils.py", line 168, in executeSQLQmark
return cursor.execute(query, params)
sqlite3.InterfaceError: Error binding parameter 1 - probably unsupported type.

SteveGYBE
26th September 2009, 10:29 AM
From the last line, it sounds like yum is having problems reading (or even recognising) some of its SQLlite data. You could try some of the "yum clean" optionsyum clean dbcache
yum clean metadata
yum clean headersand run "yum update" again after each one. Probably want to avoid "yum clean packages" and "yum clean all" unless you are happy to download all your updates again.

If all else fails you might want to tryrpm --rebuilddbjust in case it is the RPM DBs causing the problem.

glennzo
26th September 2009, 10:53 AM

Thanks for the reply Steve. I tried your suggestions one at a time. Same thing. Oddly, I am able to update one or two packages at a time with no trouble. As I whittle away at the list I imagine that I'll finally find out exactly what the root of the problem is.

Edit: I've gotten the list of updates down to kernel stuff only. Everything else updated as one would expect. I try to update these remaining kernel packages and I still get the error...

Edit2: The updates are complete. I've manually whittled away at the list until there's nothing left to update. I left the kernel updates for last. If I tried yum update I still got the error. When I updated kernel.i686 only it worked. Then I did yum update again (only kernel-PAE left) that worked too. Huh? Whatever. All done.

ryptyde
26th September 2009, 12:27 PM
I was experiencing yum hangups and stalling when trying to update large amounts of packages and did the same as you and done them in smaller increments. :)

glennzo
26th September 2009, 07:25 PM
Worked for me. I am, or was, still getting an error telling me that I need to run yum-complete-transaction as root. I did, 18 times, since that's what it took to get the system to stop bothering me. Wonder if that was related to the other issue?

typerlc
28th September 2009, 09:03 AM
I had this problem, and found I could work around it with a few commands.

But first, my guess is that the root cause of the error is that your /boot partition is full or close to full. At least that *seems* to have been the problem for me. If someone with this problem wants to test this theory, try doing:

yum remove kernel-2.6.31-23.fc12 kernel-devel-2.6.31-23.fc12 kernel-PAE-2.6.31-23.fc12 kernel-PAE-devel-2.6.31-23.fc12

Before doing that, make sure that's not your running kernel by comparing with the output from uname -a.

After that, try

/usr/sbin/yum-complete-transaction --cleanup-only
yum update

Did that work? If not, then you can try what others in this thread have suggested (worked for me too), by running something similar to:

/usr/sbin/yum-complete-transaction --cleanup-only
yum update '[a-jl-z]*' 'k[a-df-z]*'
yum update

Demz
28th September 2009, 09:37 AM
yum-complete-transaction is a plugin of yum right? just my 2cents but wouldnt that be better built into yum itself than have it as a plugin

glennzo
28th September 2009, 09:43 AM
Hi Demz. It's part of the yum-utils package.

Demz
28th September 2009, 09:59 AM
Hi Demz. It's part of the yum-utils package.

isnt the yum-utils package installed by default?

glennzo
28th September 2009, 10:10 AM
I'm not so sure it is. In the past I know I've had to install it with yum.

Demz
28th September 2009, 10:15 AM
i'll have to have a look when the beta comes out

glennzo
28th September 2009, 10:18 AM
My laptop running Fedora 12 ...
[glenn@leonardo ~]$ yum list yum*
Loaded plugins: presto, refresh-packagekit
Installed Packages
yum.noarch 3.2.24-6.fc12 @koji-i386
yum-metadata-parser.i686 1.1.2-14.fc12 @rawhide
yum-presto.noarch 0.6.1-1.fc12 @koji-i386
yum-utils.noarch 1.1.23-3.fc12 @rawhide

Basically the same thing on my Fedora 10 box.

diamond_ramsey
2nd October 2009, 03:43 AM
There is no lack of yum errors around here. Could someone please translate the following into Swahili for me? That way, I can probably understand it a little better.:rolleyes:
Transaction Test Succeeded
Running Transaction
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 315, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 263, in main
return_code = base.doTransaction()
File "/usr/share/yum-cli/cli.py", line 492, in doTransaction
resultobject = self.runTransaction(cb=cb)
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 1081, in runTransaction
self.history.end(rpmdbv, 2, errors=errors)
File "/usr/lib/python2.6/site-packages/yum/history.py", line 385, in end
self._log_errors(errors)
File "/usr/lib/python2.6/site-packages/yum/history.py", line 351, in _log_errors
(tid, msg) VALUES (?, ?)""", (self._tid, error))
File "/usr/lib/python2.6/site-packages/yum/sqlutils.py", line 168, in executeSQLQmark
return cursor.execute(query, params)
sqlite3.InterfaceError: Error binding parameter 1 - probably unsupported type.


glennzo, please see "Bug 526294 - yum history causes sqlite traceback on RPM transaction error" -

https://bugzilla.redhat.com/show_bug.cgi?id=526294

Hope this helps. ;)