Eugene,
I can't speak for the first, but:
Exception: unknown escape sequence
was a real performance killer for us, causing pdns to have to do some sort of
internal reload (it reset its uptime, at least) and not serve queries for a
couple of seconds.
Evidently -- at least with a mysql backend
Hi folks,
What could this error message mean?
Jun 5 21:28:53 ns2 pdns[5778]: TCP nameserver had error, cycling backend:
Reading data: Connection reset by peer
They are numerous indeed. I believe they affect the overall performance.
And why would this stats show up in the log:
Jun 5 21:44:33 n
Bert,
Unfortunately that was the entirety of the relevant segment, afaik-
Jun 4 22:55:35 pdnsNN pdns[18626]: Exception: Parsing record content: r:
Everything surrounding it was minutes away and "typical" (i.e. not to worry
about, from what we understand) "errors":
Jun 4 22:52:19 pdnsNN pdns
On Wed, Jun 04, 2008 at 11:41:46PM -0700, Daniel Greene - (mt) Media Temple
wrote:
> Second, this afternoon we began seeing an "Exception: Parsing record
> content: r:" error in the pdns logs. We've seen a few record content
> exceptions in the past, but they've typically been quite a bit more
>
