Hide Forgot
libreport version: 2.0.6 cmdline: executable: /usr/bin/koji kernel: 2.6.38.8-35.fc15.x86_64 reason: xmlrpclib.py:1541:__init__:IOError: unsupported XML-RPC protocol time: Mon Jul 25 14:38:29 2011 uid: 500 username: red_alert backtrace: :xmlrpclib.py:1541:__init__:IOError: unsupported XML-RPC protocol : :Traceback (most recent call last): : File "/usr/bin/koji", line 5629, in <module> : session = koji.ClientSession(options.server,session_opts) : File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1534, in __init__ : self.setSession(sinfo) : File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1561, in setSession : self.proxy = self.proxyClass(url,**self.proxyOpts) : File "/usr/lib64/python2.7/xmlrpclib.py", line 1541, in __init__ : raise IOError, "unsupported XML-RPC protocol" :IOError: unsupported XML-RPC protocol : :Local variables in innermost frame: :verbose: 0 :encoding: None comment: :$ koji --server=fqdn.example.org list-permissions : :Note: the server url was wrong (missing /kojihub if nothin else) : :Something's strange here. I set up this Pc only just yesterday and after I did I called it a day. Today I unlocked the screen and see this problem seems to have happened. No idea why koji was actually executed at all.
Did you really pass --server=fqdn.example.org? That will certainly not work. You need to reference an actual kojihub instance.
Like I said above, I did NOT do anything. I have absolutely no idea where abrt got this traceback from. It's been a fresh installation and I didn't even know/remember I had koji-client installed already at that point.
hmm, probably some other app calling koji then. I wonder which one
Could you check a few things on that box for me? 1) check/confirm the koji version (rpm -q koji) 2) see which installed packages, if any, require koji (rpm -e --test koji) 3) see if any config files reference "fqdn.example.org" (grep -rs fqdn.example.org /etc)
Okay, I just noticed there's something really wrong here. My (automatically generated) report above says this happened months ago with F15. I reported that after I installed F16 (Final RC5/GOLD). The only thing I took with me was my home. So it seems that traceback was generated at a much earlier time, saved in my home but I probably had abrt disabled/ignored. Now with the fresh install and after restoring my home abrt noticed the traceback and asked me to report it. So I can't really add more intel on how this happened, probably I did use koji wrong back then. You can safely ignore that. BUT I think the IOError should be catched either way, even if it's the users fault ;) I'll leave it to you to close this bug or have it open to fix the missing catch. Sorry for the confusion I caused :/
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping