From owner-freebsd-questions@FreeBSD.ORG Thu Mar 4 08:26:25 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8ECEF16A4CE for ; Thu, 4 Mar 2004 08:26:25 -0800 (PST) Received: from smtp.foto-album.com (ip503c114d.speed.planet.nl [80.60.17.77]) by mx1.FreeBSD.org (Postfix) with SMTP id B583643D4C for ; Thu, 4 Mar 2004 08:26:24 -0800 (PST) (envelope-from a.buurman@wxs.nl) Received: (qmail 49620 invoked from network); 4 Mar 2004 16:26:50 -0000 Received: from arnoud-2000.nt.klote.com (HELO arnoud2000) (192.168.0.252) by dns.nt.klote.com with SMTP; 4 Mar 2004 16:26:50 -0000 From: "Arnoud" To: Date: Thu, 4 Mar 2004 17:30:59 +0100 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 V6.00.2800.1165 Importance: Normal Subject: Reload of Mysql-server 4.0 on 5.2.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 16:26:25 -0000 Hi, Once again, my question, who should I bugger with this question? I'm having quite a strange problem with mysql on 5.2.1 (releng_5_2) mysql-server (40, latest cvs port) keeps on reloading when snort is connecting. When I put on logging, no query reached the engine before the reload. Well, I put on tcpdump, and guess what I find. only 7 packets. Yes, 3 way handshake en 4 way teardown. No data passes, and the server is the one starting the teardown. So I rebuilded mysql with debug, as per the mysql instructions and guess what? problem no longer occurs. According to the mysql handbook "If mysqld stops crashing when you compile it with --with-debug, you have probably found a compiler bug or a timing bug within MySQL" Any guess how to tackle this? Ofcourse running with a debuging mysql is not a good way forward. Sincerly, Arnoud Buurman