From owner-freebsd-stable@FreeBSD.ORG Wed Oct 1 12:54:42 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32B0F16A4B3 for ; Wed, 1 Oct 2003 12:54:42 -0700 (PDT) Received: from sv07e.atm-tzs.kmjeuro.com (sv07e.atm-tzs.kmjeuro.com [193.81.94.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41AC543F85 for ; Wed, 1 Oct 2003 12:54:40 -0700 (PDT) (envelope-from k.joch@kmjeuro.com) Received: from kmjeuro.com (adsl.sbg.kmjeuro.com [62.99.198.46]) (authenticated bits=0)h91JsN1V047193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 1 Oct 2003 21:54:24 +0200 (CEST) (envelope-from k.joch@kmjeuro.com) Message-ID: <3F7B30EF.4080306@kmjeuro.com> Date: Wed, 01 Oct 2003 21:54:23 +0200 From: "Karl M. Joch" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org References: <20031001180521.C9CDF16A4F2@hub.freebsd.org> <20031001190312.GC21705@wjv.com> <6.0.0.22.0.20031001150923.08460910@209.112.4.2> In-Reply-To: <6.0.0.22.0.20031001150923.08460910@209.112.4.2> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: please visit www.ctseuro.com for further instructions. Protected by www.ctseuro.com X-MailScanner: Found to be clean Subject: Re: panics on 24 hour boundaries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2003 19:54:42 -0000 Mike Tancsa wrote: > > Actually, one note on this, I had a server that was panicing similar to > this that DES was kind enough to look at a while ago. The problem was > never tracked down, but I found that taking INET6 out of the kernel > solved the problem. I asked michael@gargantuan.com if this was possible > to try, and he said they make heavy use of INET6 so they could not take > it out. The other user seeing similar crashes (tss@reflection.co.jp) > also makes use of INET6. It could of course be total coincidence and > have nothing to do with it. > > ---Mike > > At 03:03 PM 01/10/2003, Bill Vermillion wrote: > >> On Wed, Oct 01, 2003 at 11:05 , Men gasped, women >> fainted, and small children were reduced to tears as >> freebsd-stable-request@freebsd.org confessed to all: >> >> > Message: 18 >> > Date: Tue, 30 Sep 2003 23:19:34 -0400 >> > From: "Michael W. Oliver" >> > Subject: Re: panics on 24 hour boundaries >> >> [severly edited - wjv] >> >> > +--- On Tuesday, September 30, 2003 22:35 --- >> > | Robert Watson proclaimed: >> >> > | Initial reactions: panics on 24 hour boundaries are, in my >> > | experience, often associated with the daily event. Once a >> > | day, the daily scripts run find several times on your file >> > | systems, causing every file and directory to be inspected >> > | for changes in setuid scripts, etc. This can trigger certain >> > | classes of race conditions and resource limits that you might >> > | otherwise not hit in normal operation -- and conviently, they >> > | run 24 hours apart :-). To try and confirm this suspicion, >> > | it would be interesting to know what time of day exactly the >> > | panics take place, and whether you can reproduce the panic by >> > | manually running the daily or security script. >> >> > All of the panics happened in the evening hours, between 1800 >> > and 2200 EDT. I am also able to successfully run the daily >> > periodic scripts at any time of the day without issue. >> >> One part in this thread said the panics happened 24 hours after >> reboot and that would imply something in scripts that depend upon >> a length of time being powered up. >> >> However if all the pnaics occur in the 1800-2200 time frame >> this could be caused by an external event. >> >> It could be any large device on the same electric circuits you are >> on. By the 'same circuit' I mean anyone and/or anything connected >> to the same power transformer. In a residential area this could be >> several houses. >> >> Anything that could put a spike on the line could cuase this. >> And even if the computer if filter and on a UPS if any device >> connected to the computer is not also on the same filter those >> could be the culprits. I've seen [in the far past when I >> maintained many machines with serial terminal] terminals and also >> printers cause this. >> >> One place had contruction going on next door and that was alway >> in early afternoon when one piece of equipment was fired up. >> >> And one of the legendary stories is about the systems that paniced >> every day between noon and about 10 after. That was traced to a >> microwave in the lunchroom. >> >> It's been my experience that often time related crashes are >> external to the machines involved unless each and everything >> connected to the machine is coming from the same filterer/protected >> source, including all phone lines for DSL and or cable. >> >> Bill >> > End of freebsd-stable Digest, Vol 28, Issue 4 >> >> >> -- >> Bill Vermillion - bv @ wjv . com >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" i had one server crashing every 24 hours. was searching long time then recompiled mpd and the crashes was gone. but this was with 4.6 i think. not sure if this helps. -- Best regards / Mit freundlichen Gruessen, Karl M. Joch k.joch@ctseuro.com http://www.ctseuro.com