 |  |
all the crashing I experienced with 3.0 was due to corrupt zone files...
Re: QDNS still crashing
From: andrew
Date: Wednesday, December 20, 2000
Time: 3:56:41 pm
IMHO it would be the first place to look...are you logging everything, and,
if so, what's the last event before QDNS quits?
Actually, some of the crashing had to do with bad RAM, but it was the RAM
that was corrupting the zone files.
You could set the refresh on each zone, one at a time, to a very low number
and watch the logs (in detail mode) to see if other servers repeatedly
querying that zone crash it...what servers are providing secondary to this
one, and for which zones? The secondaries will probably hitting the corrupt
zone more often than everybody else.
You said it would take two days to recreate the zone files by hand...how
many are you talking about?
----- Original Message -----
From: "Mia's Virtual Post Office" <list@mia.net>
To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>;
<support@menandmice.com>
Sent: Wednesday, December 20, 2000 6:37 PM
Subject: QDNS still crashing
> Well, as you may all know, 3.0 was not working well for us so we moved
> back to 2.2.1. 2.2.1 is still crashing with type 1 errors.. It ran fine
> for about 2 days (which is longer than 3.0GM ran.)
>
> Here is what we have done thus far:
>
> 1. Reverted back to 2.2.1
> 2. Put QDNS on a different machine
> 3. Changed Ether Cables
> 4. Changed Switches
> 5. Reverted to a backup copy of the DATA file.
> 6. Are monitoring all in/out data to see if there are any high blasts of
> traffic to the server when it dies..
>
> Nothing out of the ordinary with traffic:
> http://stats.mia.net/~mrtg/r252/r252.html
>
> At the time it died, everything was normal.
>
> Now I am trying for the life of me to remember what the hell I might have
> done to cause this problem. Under 2.2.1 (prior to the 3.0 beta) we used
> QDNS just fine, though there was the occasional crash, ie., once every
> few months or so, but this is quite normal.
>
> Then we moved to the beta v4. Everything worked flawlessly.. In fact I
> emailed Men and Mice to tell them that I would be on holiday for a while,
> and needed to insure that the beta would not expire while I was gone.
> They confirmed that I had a few days left after I returned from holiday,
> so all would be fine with that.. Everything was fine.. The beta ran
> perfect for a grand total of 20 days I believe. Now it was on the 13th
> of December that I finally bought the upgrade (as the beta would expire
> the next day). I installed the full version, moved the data files, and
> started her up.. It has been hell ever since.
>
> I really do not know what to do at this point. I love QDNS, always have,
> but I cannot keep going on this way. I have eliminated hardware, ie.,
> the servers.. I have eliminated network problems, ie., network cables,
> switches, attacks, etc.. The only thing I am left with is a software
> problem, and or corrupt data files.
>
> At this point I am seriously thinking of installing a fresh copy of 3.0
> on a completely different box, then manually recreating every frigin'
> zone file by hand. I estimate it will take me a good day or two straight
> to get this done. From there, I would just set the IP of this Virgin box
> to the IP of our primary and shut the other one down. If this still
> yields the same results I am going to jump off of our building Christmas
> Day...(there is about 2 feet of snow on the ground, and our building is
> only 1 story in the front, so I should live through it.)
>
> Anyone care to take a stab at this one? Not my suicidal tendencies, but
> the QDNS crashing/deafness/good God almighty problem.
>
> jer
> www.hostdrive.com
> Colocate Your G4 Cube at cubelocation.com
>
>
> NetZero = What this company will "NET" --- "ZERO"
>
>
>
Messages In This Thread:
Return to Digital Point Solutions' Home Page