Bug 917320

Summary: [abrt] Zim-0.59-1.fc18: ipc.py:275:start_server_if_not_running:AssertionError: Failed to start server (spawning)
Product: [Fedora] Fedora Reporter: DarkShell <byujiang>
Component: ZimAssignee: Robin Lee <robinlee.sysu>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: fabian, robinlee.sysu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f3ad20dc9c8a559bc98d74e0db43b89daf1a9c07
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-23 02:21:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: environ none

Description DarkShell 2013-03-03 04:27:11 UTC
Version-Release number of selected component:
Zim-0.59-1.fc18

Additional info:
cmdline:        /usr/bin/python /usr/bin/zim
executable:     /usr/bin/zim
kernel:         3.7.9-205.fc18.x86_64
uid:            1000

Truncated backtrace:
ipc.py:275:start_server_if_not_running:AssertionError: Failed to start server (spawning)

Traceback (most recent call last):
  File "/usr/bin/zim", line 73, in <module>
    zim.main(argv)
  File "/usr/lib/python2.7/site-packages/zim/__init__.py", line 443, in main
    start_server_if_not_running()
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 275, in start_server_if_not_running
    raise AssertionError, 'Failed to start server (spawning)'
AssertionError: Failed to start server (spawning)

Local variables in innermost frame:
ZimCmd: <function ZimCmd at 0xb52500>
trace: 'Traceback (most recent call last):\n  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 264, in start_server_if_not_running\n    s.ping()\n  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 702, in call\n    conn = Client(SERVER_ADDRESS, SERVER_ADDRESS_FAMILY)\n  File "/usr/lib64/python2.7/multiprocessing/connection.py", line 169, in Client\n    c = SocketClient(address)\n  File "/usr/lib64/python2.7/multiprocessing/connection.py", line 293, in SocketClient\n    s.connect(address)\n  File "/usr/lib64/python2.7/socket.py", line 224, in meth\n    return getattr(self._sock,name)(*args)\nerror: [Errno 2] No such file or directory\n'
i: 9
app: <Application: ('/usr/bin/python', u'/usr/bin/zim')>
traceback: <module 'traceback' from '/usr/lib64/python2.7/traceback.pyc'>
loglevel: 30
s: <zim.ipc.ServerProxyClass object at 0xc82390>
time: <module 'time' from '/usr/lib64/python2.7/lib-dynload/timemodule.so'>

Comment 1 DarkShell 2013-03-03 04:27:15 UTC
Created attachment 704519 [details]
File: backtrace

Comment 2 DarkShell 2013-03-03 04:27:17 UTC
Created attachment 704520 [details]
File: core_backtrace

Comment 3 DarkShell 2013-03-03 04:27:20 UTC
Created attachment 704521 [details]
File: environ

Comment 4 Fedora End Of Life 2013-12-21 11:49:15 UTC
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.

Comment 5 Robin Lee 2013-12-23 02:21:59 UTC

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