Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

configd: startup sometimes fails to bring up the socket in time #218

Closed
fichtner opened this issue Jun 22, 2015 · 2 comments
Closed

configd: startup sometimes fails to bring up the socket in time #218

fichtner opened this issue Jun 22, 2015 · 2 comments
Assignees
@AdSchellevis
Labels
bug Production bug
Milestone
15.7

Comments

@fichtner
Copy link
Member

Workaround exists: wait a little longer for configd to come up. It seems we need a retry/delay for the socket on configctl invokes.

via: https://forum.opnsense.org/index.php?topic=731.0
@fichtner fichtner added the bug Production bug label Jun 22, 2015
@fichtner fichtner added this to the 15.7 milestone Jun 22, 2015
@fichtner fichtner mentioned this issue Jun 22, 2015
Closed
AdSchellevis added a commit that referenced this issue Jun 22, 2015
@AdSchellevis
wait for configd socket if it's not there yet (#218)
b282f65
AdSchellevis added a commit that referenced this issue Jun 22, 2015
@AdSchellevis
also let configctl wait for configd to start (#218)
f43baf4
AdSchellevis added a commit that referenced this issue Jun 22, 2015
@AdSchellevis
cleanup configd socket on exit (related to #218)
064de35
@AdSchellevis
Copy link
Member

fixed with :
b282f65
f43baf4
064de35

@fichtner
Copy link
Member Author

thank you! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AdSchellevis AdSchellevis

Labels
bug Production bug
Milestone
15.7
Development

No branches or pull requests
2 participants
@fichtner @AdSchellevis