running pdns_server (without parameters) makes control socket unusable for previously started instance #841

Closed
RvdE opened this Issue Jun 4, 2013 · 0 comments

Projects

None yet

1 participant

@RvdE
Contributor
RvdE commented Jun 4, 2013

if you have a running pdns auth instance and then start pdns_server again (it wont start), the control socket becomes unusable.

I wanted pdns_server to dump a config and used this 'pdns_server config' instead of 'pdns_server --config'.

This happens on both version 3.2 and 3.3rc1

@ahupowerdns ahupowerdns added a commit that closed this issue Jun 10, 2013
@ahupowerdns ahupowerdns CHANGES BEHAVIOUR: before we launch, check if we can connect to the c…
…ontrolsocket we are about to obliterate. If it works, abort. Fixes #841 and changes standing behaviour. There might be circumstances where PowerDNS now refuses to start, where it previously would. However, starting and making our previous instance mute wasn't good.
ce19a81
@ahupowerdns ahupowerdns added a commit that referenced this issue Jun 10, 2013
@ahupowerdns @Habbie ahupowerdns + Habbie CHANGES BEHAVIOUR: before we launch, check if we can connect to the c…
…ontrolsocket we are about to obliterate. If it works, abort. Fixes #841 and changes standing behaviour. There might be circumstances where PowerDNS now refuses to start, where it previously would. However, starting and making our previous instance mute wasn't good.
d72166c
@ahupowerdns ahupowerdns added a commit that referenced this issue Jun 10, 2013
@ahupowerdns ahupowerdns CHANGES BEHAVIOUR: before we launch, check if we can connect to the c…
…ontrolsocket we are about to obliterate. If it works, abort. Fixes #841 and changes standing behaviour. There might be circumstances where PowerDNS now refuses to start, where it previously would. However, starting and making our previous instance mute wasn't good.
7db735c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment