➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients pitrou
Date 2017-08-30.14:27:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1504103235.79.0.43802074293.issue31308@psf.upfronthosting.co.za>
In-reply-to
Content 
It may happen that the forkserver process dies (for example if SIGINT is received because the user pressed Ctrl-C) while the parent process is still alive.  In that case, if the parent tries to create a new Process instance, an exception is received.

The exception looks like this:

  File "/xxx/lib/python3.5/multiprocessing/popen_forkserver.py", line 52, in _launch
	self.sentinel, w = forkserver.connect_to_new_process(self._fds)
  File "/xxx/lib/python3.5/multiprocessing/forkserver.py", line 66, in connect_to_new_process
	client.connect(self._forkserver_address)
ConnectionRefusedError: [Errno 111] Connection refused
History
Date User Action Args
2017-08-30 14:27:15pitrousetrecipients: + pitrou
2017-08-30 14:27:15pitrousetmessageid: <1504103235.79.0.43802074293.issue31308@psf.upfronthosting.co.za>
2017-08-30 14:27:15pitroulinkissue31308 messages
2017-08-30 14:27:15pitroucreate