From owner-freebsd-stable Tue Jul 18 1:36:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns.comrax.com (dns.comrax.com [194.90.246.124]) by hub.freebsd.org (Postfix) with ESMTP id AEEC137BB44 for ; Tue, 18 Jul 2000 01:36:36 -0700 (PDT) (envelope-from noor@comrax.com) Received: from NOOR (unknown [156.27.243.27]) by dns.comrax.com (Postfix) with SMTP id 09E3D1C982 for ; Tue, 18 Jul 2000 11:36:29 +0300 (IDT) From: "Noor Dawod" To: "FreeBSD-STABLE Mailing List" Subject: Bus error / Segmentation fault. Date: Tue, 18 Jul 2000 11:34:59 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Disposition-Notification-To: "Noor Dawod" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I've installed FreeBSD 4.1-RC this morning successfully, and it works perfectly. I've then isntalled mysqld with patches successfully, Apache + PHP. I'm doing all of that on a development server we have internally. Then, I've started benchmarking mysqld performance using RadView's WebLoad application, just to send requests to the Apache server which in turn uses connections to mysql databases. Using mysqld's startup parameters, and with 20 max servers of Apache (each can serve 50 connections max), the mysqld starts dying with "Bus error" and "Segmentation fault" errors, and then restarting from safe_mysqld. Now.. I've seen mysqld run on Solaris boxes and never dying even on high loads, which brings me to the question: who's killing mysqld? Is it FreeBSD that kills mysqld because it's taking more resources than normal, or is it mysqld that kills itself? If you have any idea, advises, and why mysqld dies on FreeBSD (and not on Solaris), please share it with us. Thanks... Noor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message