Red Hat Bugzilla – Bug 454456
Unable to start carod immediately after stopped
Last modified: 2009-02-04 11:06:04 EST
Description of problem:
Starting carod immediately after stopping it will fail. This is because the
port that carod is listening on doesn't seem to be closing cleanly and is going
into the CLOSE_WAIT state. The code attempts to cleaning shut down all sockets,
but something must be missed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
A sock was found to be missed being closed, and along with daemonizing carod the problem seems to have been solved. I have been able to stop and restart carod many times back-to-back.
Dec 5 15:37:34 north-11 carod: socket error 98: Address already in use
Dec 5 15:37:34 north-11 carod: Failed to listen on 127.0.0.1:10000
Dec 5 15:37:37 north-11 hook_fetch_work.py: socket error 107: Transport endpoint is not connected
Dec 5 15:37:38 north-11 hook_fetch_work.py: socket error 107: Transport endpoint is not connected
Dec 5 15:37:38 north-11 carod: socket error 98: Address already in use
Dec 5 15:37:38 north-11 carod: Failed to listen on 127.0.0.1:10000
with -8. So still happening.
Needed to set SO_REUSESOCKET on the listen socket carod uses. Fixed in:
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.