 |  |
>just you and Jer <grin>...I've been able to stop crashing by matching my RAM
Re: QDNS still crashing
From: Jerry Pasker
Date: Wednesday, December 20, 2000
Time: 6:46:55 pm
>to my motherboard on a 7200/120.
>
>Have either of you guys considered running an Applescript once an hour to
>"restart" QDNS? This flushes the cache....and if your crashing stops, then
>it's the size of the memory partition that is somehow involved...have either
>of you tried setting QDNS's memory partition to 8-meg and seen what happens?
>
Yeah, I've tried adjusting it down to about 3 or 4 MB. The free mem is
much less, but the actual time between crashes doesn't really change. It's
as if it's related to the total number of recursive queries, but how many?
I don't know. I don't even know if it's related to total number of
lookups.
It's a problem that is *NOT* easily reproducible. As a matter of fact,
I've never been able to reproduce this type of crash. I can make it crash
in a few different ways (version 2.2.1) but never in the way that it's
crashing on its own.
I've seen it purge out ram, when I've processed several hundred megabyte
webserver log files, (3 G3s all running different 100+ MB files trying to
overload it) and it handled it like a champ. Two days later, it crashed.
Related event? Unrelated event? I don't know.
I'm out of ideas. All I know is that I've used a G3 Minitower, iMac 266,
and iMac 333, and Performa 6220 as primaries, and they've all had this
problem.
Furthermore, one day, not very long ago, I've seen (In this order) my
secondary QDNS crash, primary QDNS crash, NT server crash, and two Linux
boxes puke (co located boxes, they don't use my QDNS, or any other services
on my network) 4 times each within a 30 minute period. I couldn't track
much of anything down, because I was scrambling to reboot, restart, power
cycle, and get boxes up and running again. No log files, on any of the
boxes, had ANYTHING out of the ordinary. Oh, my mail server running SIMS
also hung up several times during that whole ordeal, but it unfroze after
about 20 or 30 seconds of being "hung."
My WebSTAR machine, or routers, or access servers weren't phased by that
particular incident.
So, there's also likely a DoS issue to deal with.
Trying to nail this down feels like I'm hunting UFOs. Lots of vague,
inconclusive, semi related events, with no real proof of anything. And,
it'd be easy for any nay sayer to debunk any of this.
-Jerry
Messages In This Thread:
Return to Digital Point Solutions' Home Page