 |  |
well, QDNS quit again, after an hour...MacsBug reported a PowerPC illegal
Re: QDNS quitting...too much memory?
From: andrew
Date: Thursday, November 2, 2000
Time: 4:27:15 pm
instruction <sigh>...
I'll start running through the laundry list now. M&M, do you want me to send
you the MacsBug dump?
TIA, Andrew
----- Original Message -----
From: "Men & Mice Support" <cbuxton@menandmice.com>
To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
Sent: Thursday, November 02, 2000 5:59 PM
Subject: Re: QDNS quitting...too much memory?
> At 5:37 PM -0500 11/2/00, andrew wrote:
> >Well, QDNS just quit again after 15 minutes...sounds like TCP/IP prefs
are
> >corrupted? What should I do, trash, reboot and reconfigure?
>
> Try the usual:
>
> Check the hard drive - Disk First Aid and DiskWarrior are good choices.
> Rebuild the desktop.
> Reset the PRAM.
> Check the network connections - is the cable starting to short?
>
> If none of that works, try this:
> - Quit both QDNS Server and Admin.
> - Trash the QuickDNS Options file (in the QuickDNS Data folder).
> - Launch QuickDNS Admin to recreate the options file with default options.
> - Open the Server Preferences dialog and recreate and settings you had.
> - Launch the server.
>
> If that doesn't work, start looking at the various system settings
> and preference files.
> ____________________________________________________________________
> Chris Buxton Men & Mice
> cbuxton@menandmice.com We Make DNS Easy!
>
>
> >----- Original Message -----
> >From: "andrew" <andrew@ardentmicro.com>
> >To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> >Sent: Thursday, November 02, 2000 5:24 PM
> >Subject: QDNS quitting...too much memory?
> >
> >
> >> 2.2.1 on a 7250 WGS/OS8.6. It was running fine with an 8-meg RAM
> >> allocation. I recently added two 32-meg DIMMS and upped QDNS's
allocation
> >to
> >> 32000K...suddenly it starts quitting every hour.
> >>
> >> The server doesn't seem to be heavily loaded...usually only a few
thousand
> >> packets transfer before it quits. Could it be bad RAM? I've reduced it
> >back
> >> down to 8-meg and am waiting to see what happens.
> >>
> >> Should I install MacsBug? If it's a TCP/IP corruption problem, is
there
> >> anything to try to fix it?
> >>
> >> Andrew Kagan
> >>
> >>
> >>
>
>
Messages In This Thread:
Return to Digital Point Solutions' Home Page