From owner-freebsd-security Tue May 22 13:36:52 2001 Delivered-To: freebsd-security@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id 53A1837B43C for ; Tue, 22 May 2001 13:36:48 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from HP2500B (fuggle.veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id 48ACCBAA7; Tue, 22 May 2001 15:36:47 -0500 (CDT) Message-ID: <019b01c0e2fe$eb384d40$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: "Michael Tang Helmeste" , References: Subject: Re: Qmail + FreeBSD 4.3 Date: Tue, 22 May 2001 15:36:45 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Swap memory and see. I had the same problem (different program). Apache kept dying was my first symptom. Then postfix died occassionally. MySQL dumped when used. A few things like that. It started happening on a system that had been working for the better part of a year. It was the CPU. Sig 11 more often than not is a hardware problem. There is only one case I know of that I can reproducibly create a sig 11 when it is not hardware. If you run ncftp3 against a server and download a large directory using the "tar on the fly option", it will often dump core. This could be the case with qmail, but I have not seen it reported, thus I think he should check his hardware. Tom Veldhouse ----- Original Message ----- From: "Michael Tang Helmeste" To: "Thomas T. Veldhouse" ; Sent: Tuesday, May 22, 2001 3:31 PM Subject: RE: Qmail + FreeBSD 4.3 > Well bad hardware is less likely than its trying to overwrite memory it > doesn't own. If he is being attacked, and it is a buffer overflow exploit, > than overwriting memory it doesn't own is more likely than it being > repeatidly hardware, especially after his system has been working fine all > this time. > > -----Original Message----- > From: Thomas T. Veldhouse [mailto:veldy@veldy.net] > Sent: Tuesday, May 22, 2001 9:16 AM > To: Michael Tang Helmeste > Subject: Re: Qmail + FreeBSD 4.3 > > > Signal 11 (and often10) very often signal bad hardware. Memory and/or CPU > are usually the cause, followed by the main board. Corruption occurs in > memory and a signal 11 results. > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "Michael Tang Helmeste" > To: > Sent: Monday, May 21, 2001 8:35 PM > Subject: RE: Qmail + FreeBSD 4.3 > > > > actually it just means segmentation fault > > > > it happens when a program accesses some memory that it doesn't own > > > > -----Original Message----- > > From: owner-freebsd-security@FreeBSD.ORG > > [mailto:owner-freebsd-security@FreeBSD.ORG]On Behalf Of Olivier Nicole > > Sent: Monday, May 21, 2001 9:17 PM > > To: subscribed@de-net.org > > Cc: freebsd-security@FreeBSD.ORG > > Subject: Re: Qmail + FreeBSD 4.3 > > > > > > Hi Dan, > > > > Signa 11 often denotes some hardware problem I guess, something like > > overheating. > > > > Olivier > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-security" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-security" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message