From owner-freebsd-bugs Tue Dec 18 8:30:11 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7B12737B43B for ; Tue, 18 Dec 2001 08:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fBIGU3a16238; Tue, 18 Dec 2001 08:30:03 -0800 (PST) (envelope-from gnats) Date: Tue, 18 Dec 2001 08:30:03 -0800 (PST) Message-Id: <200112181630.fBIGU3a16238@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Nevermind Subject: Re: bin/32740: ftpd segfaults after get Reply-To: Nevermind Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/32740; it has been noted by GNATS. From: Nevermind To: "Crist J . Clark" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/32740: ftpd segfaults after get Date: Mon, 17 Dec 2001 16:27:20 +0200 Hello, Crist J . Clark! On Mon, Dec 17, 2001 at 03:36:09AM -0800, you wrote: > > > pid 43138 (ftpd), uid 3033: exited on signal 11 > > > Dec 11 16:35:26 rabbit /kernel: pid 43138 (ftpd), uid 3033: exited on signal 11 > > > > uid 3033 is user atlon > > > > >How-To-Repeat: > > I cannot reproduce this error for sure, it happens according to very > > strange law... > > >Fix: > > > > Haven't find anything that could cause this on 'get' in sources. Maybe you > > will? > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11 > > Anything there look familiar? Is ftpd(8) the only on dying like this? I've checked URL, nothing looks familiar, I have not overclocked CPU, I have brand new Trascend memory, I have 400W power suppoly and ftpd(8) is the only one which is dying like this. No 11 signals except for ftpd. This server is pretty loaded with apache/mysql/postgresql, and nothing segfaults except for ftpd. > Do you have a better idea of how to reproduce this yet? No, unfortunately... I had this problem few times on different hardware known to be absolutely good. And the strange thing -- it does not leave core... -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message