On 12/11/2012 11:25 PM, Stefan Schmidt wrote:
I don't see why this is happening. A manual "start pdns-recursor"
works just fine - so the problem isn't the execution from Upstart,
but there must be some timing/event issue I'm not seeing. Any ideas?
It just a wild guess, but might
Hello Daniel,
On Dec 12, 2012, at 5:41 , Daniel L. Miller wrote:
> While occasionally this works on boot - I've found a problem more usually
> occurs. My dmesg output:
> [ 57.783902] init: pdns-recursor main process (1555) terminated with status
> 1
> [ 57.783925] init: pdns-recursor main
Hallo Daniel,
On Wed, Dec 12, 2012 at 5:41 AM, Daniel L. Miller wrote:
> I've made a pair of simple Upstart scripts for controlling pdns &
> pdns-recursor. For pdns -
>
> /etc/init/pdns.conf
> start on started mysql
> respawn
> respawn limit 10 5
> exec /usr/sbin/pdns_server --daemon=no --guard
I've made a pair of simple Upstart scripts for controlling pdns &
pdns-recursor. For pdns -
/etc/init/pdns.conf
start on started mysql
respawn
respawn limit 10 5
exec /usr/sbin/pdns_server --daemon=no --guardian=no
This works without issues. Since mysql activates extremely early in the
boot
