abrt 1.0.8 detected a crash. architecture: i686 cmdline: python -m SimpleHTTPServer component: python executable: /usr/lib/python2.6/SimpleHTTPServer.py kernel: 2.6.32.10-90.fc12.i686.PAE package: python-2.6.2-4.fc12 reason: <string>:1:bind:error: [Errno 98] Address already in use release: Fedora release 12 (Constantine) backtrace ----- <string>:1:bind:error: [Errno 98] Address already in use Traceback (most recent call last): File "/usr/lib/python2.6/runpy.py", line 122, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib/python2.6/runpy.py", line 34, in _run_code exec code in run_globals File "/usr/lib/python2.6/SimpleHTTPServer.py", line 218, in <module> test() File "/usr/lib/python2.6/SimpleHTTPServer.py", line 214, in test BaseHTTPServer.test(HandlerClass, ServerClass) File "/usr/lib/python2.6/BaseHTTPServer.py", line 584, in test httpd = ServerClass(server_address, HandlerClass) File "/usr/lib/python2.6/SocketServer.py", line 400, in __init__ self.server_bind() File "/usr/lib/python2.6/BaseHTTPServer.py", line 108, in server_bind SocketServer.TCPServer.server_bind(self) File "/usr/lib/python2.6/SocketServer.py", line 411, in server_bind self.socket.bind(self.server_address) File "<string>", line 1, in bind error: [Errno 98] Address already in use Local variables in innermost frame: self: <socket._socketobject object at 0x9a221ec> args: (('', 8000),)
Created attachment 404315 [details] File: backtrace
How to reproduce ----- 1. Bind a program to TCP port 8080 2. Run "python -m SimpleHTTPServer" Comment ----- I think that ABRT should stop reporting/complaining about this bug.
The test case for the module is hardcoded to use port 8080, so if that's already in use it will fail. In theory it could be rewritten to use a different port, but that seems like an issue for upstream. Closing this one out with the resolution "NOTABUG". Feel free to reopen if I've misunderstood this.
(In reply to comment #3) > The test case for the module is hardcoded to use port 8080, so if that's > already in use it will fail. In theory it could be rewritten to use a > different port, but that seems like an issue for upstream. That's correct, it's an expected failure, nothing unusual, although the module could handle this case more gracefully instead of spitting an exception. > Closing this one out with the resolution "NOTABUG". Feel free to reopen if > I've misunderstood this. Well, the problem is not with the python module, but with ABRT. Why does ABRT complain about this, when it shouldn't as far as I can see?
I'm using python-2.6.4-27.fc13.x86_64.rpm, abrt-1.1.1-1.fc13.x86_64.rpm and abrt-addon-python-1.1.1-1.fc13.x86_64.rpm.
(In reply to comment #4) > (In reply to comment #3) [snip] > > Closing this one out with the resolution "NOTABUG". Feel free to reopen if > > I've misunderstood this. > Well, the problem is not with the python module, but with ABRT. Why does ABRT > complain about this, when it shouldn't as far as I can see? As I understand it, when ABRT sees an unhandled Python exception, it looks to see if the script that Python run was part of an RPM payload, as opposed to a "local script"; in the former case, then it's treated as a bug against that RPM. This feels to me like a bit of a weird special-case; it doesn't seem worth fixing to me. Reopening and reassigning to ABRT so the ABRT folks see it, but feel free to close it.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
The issue is still present in python-2.7-8.fc14.1.x86_64.rpm, abrt-1.1.14-1.fc14.x86_64.rpm and abrt-addon-python-1.1.14-1.fc14.x86_64.rpm.
This bug is still present in F16+python2.7 and I agree with comment#4 that the exception should be handled in the python code, so reassigning back to python.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is 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" 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
It's still present in Fedora 17 (python-2.7.3-7.2.fc17.x86_64).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
*** Bug 922294 has been marked as a duplicate of this bug. ***
It's still present in Fedora 18 (python-2.7.3-13.fc18.x86_64).
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
It's still present in Fedora 20.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.