 |  |
>From: "Jerry Pasker" <info@n-connect.net>
Re: QDNS still crashing
From: Peter Lalor
Date: Thursday, December 21, 2000
Time: 9:52:30 am
>
>>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.)
<snip>
>My solution;
>
>Give QDNS 64-90MB of RAM.
>Reboot before the free mem gets down to about half of what it started at.
>It's the only solution I have right now. I gave up trying to solve it. I
>was hoping someone else would run into the same thing, solve it, and I
>could just read the list, and hear with the solution was. I just reboot it
>a few times a week, between the hours of Midnight, and 3 AM.
>
>When the free ram starts to get low, the machine will just lock. That's
>the problem that I'm having. I've never been lucky enough to log the crash.
I'd strongly suggest running Tenon's autologging MacsBug (on any
server), so that crashes will get automatically logged and the
machine restarted without external intervention. That way you can
usually get a log to pass on, which is crucial for helping the vendor
to help you.
ftp://ftp.tenon.com/pub/Mac_Utilities/
>My guess is that there's a mem leak somewhere, and the mem gets corrupted,
>and when it tries to do a massive purge of the cache, it encounters the
>error and pukes big time.
We do not see this behavior, on a 6100 and a 7100 with 20 MB
allocated to QDNS 3.0. When the cache eventually fills up available
RAM, QDNS purges some and keeps on going.
--
Peter Lalor Infoasis
plalor@infoasis.com http://www.infoasis.com/
"Where's my burrito?" -- Homer
Messages In This Thread:
Return to Digital Point Solutions' Home Page