abrt version: 1.1.13 architecture: x86_64 component: translate-toolkit executable: /usr/bin/tmserver kernel: 2.6.34.7-61.fc13.x86_64 package: translate-toolkit-1.8.0-1.fc13 reason: __init__.py:1596:start:error: [Errno 98] Address already in use release: Fedora release 13 (Goddard) time: 1288852184 uid: 500 backtrace ----- __init__.py:1596:start:error: [Errno 98] Address already in use Traceback (most recent call last): File "/usr/bin/tmserver", line 27, in <module> tmserver.main() File "/usr/lib/python2.6/site-packages/translate/services/tmserver.py", line 195, in main wsgi.launch_server(options.bind, options.port, application.rest) File "/usr/lib/python2.6/site-packages/translate/misc/wsgi.py", line 84, in launch_server server(host, port, app) File "/usr/lib/python2.6/site-packages/translate/misc/wsgi.py", line 72, in launch_server_cherrypy server.start() File "/usr/lib/python2.6/site-packages/cherrypy/wsgiserver/__init__.py", line 1596, in start raise socket.error, msg error: [Errno 98] Address already in use Local variables in innermost frame: info: [(2, 1, 6, '', ('127.0.0.1', 55555))] af: 2 canonname: '' self: <cherrypy.wsgiserver.CherryPyWSGIServer object at 0x1b96050> proto: 6 msg: error(98, 'Address already in use') host: 'localhost' res: (2, 1, 6, '', ('127.0.0.1', 55555)) socktype: 1 sa: ('127.0.0.1', 55555) port: 55555
Created attachment 457670 [details] File: backtrace
Was tmserver started manually by yourself or was this while running Virtaal?
Package: translate-toolkit-1.8.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.just errered on its own 2. 3.
*** Bug 683144 has been marked as a duplicate of this bug. ***
ALfredo > where you using Virtaal when this error occured? You said that you where clicking on a .mo file. Where you trying to open some random MO file from within Virtaal or from a file manager?
Dwaynem, from Nautilus file manager.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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
Any update here? Moving to F14 based on comment 3 and comment 4.
(In reply to comment #8) > Any update here? > > Moving to F14 based on comment 3 and comment 4. Nope still not fixed upstream. Still setup some tests to try to simulate getting into this situation or making this fail more gracefully if the port is in use.
No information provided long while and f14 ended up EOL product some while ago. closing this so far. please reopen if you still persists on the supported product. thanks.