From: Paul J. Smith <pjsmith@mt...> - 2004-12-14 08:12:17
It happened again last night. Mydns simply stopped answering queries,
though it was still running.
Stopping it, then starting it (after a couple seconds) resulted in a
port already in use error. Stopping it, wait a while, then start it
again got it running.
I guess the TCP errors are because I have TCP and zone transfers
enabled. This is because I have some large zones on non-mydns servers
(I didn't want to migrate all at once in case there were issues like
this). How can I increase the amount of zone transfer requests mydns
can handle? I guess it can only handle a few at a time by default?
No other errors in the log as to while it stopped answering queries
though. Platform is a clean fedora fc-3 build.
[mailto:mydns-users-admin@...] On Behalf Of Paul J.
Sent: 13 December 2004 10:12
Subject: [mydns-users] MyDNS just quit on me.
I've been running mydns for a week no problem, but as I'm sitting
starting at my terminal, it just stopped answering queries on me. After
a couple stop's/start's it is running again, but I need to fin out why
this has happened.
In the log there are lots of
mydns: pid 15693 exited due to signal 11
Is this normal?
I also got
mydns: accept (TCP): Resource temporarily unavailable
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.=20
mydns-users mailing list