From owner-freebsd-questions@FreeBSD.ORG Tue May 20 23:16:50 2003 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 F292737B401 for ; Tue, 20 May 2003 23:16:49 -0700 (PDT) Received: from perlpimp.codersluts.net (adsl-33-187-176.asm.bellsouth.net [67.33.187.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1083B43F3F for ; Tue, 20 May 2003 23:16:49 -0700 (PDT) (envelope-from sektie@codersluts.net) Received: from perlpimp.codersluts.net (localhost.codersluts.net [127.0.0.1]) h4L7GRKQ069303 for ; Wed, 21 May 2003 02:16:28 -0500 (EST) (envelope-from sektie@codersluts.net) From: "sektie" To: questions@freebsd.org Date: Wed, 21 May 2003 02:16:27 -0500 Message-Id: <20030521070607.M39829@codersluts.net> X-Mailer: Open WebMail 2.01 20030425 X-OriginatingIP: 63.96.153.123 (sektie) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: mysql/php/apache weirdness 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: Wed, 21 May 2003 06:16:50 -0000 This is on a fbsd-5 'puter. When mysql 3.23.56 first came out in the ports tree, I used portupgrade to install it the very next day. Previous to that, I believe I was running mysql 3.23.54. I was running a website that uses very simple php code that interfaces with my mysql db, but it just started dying with 3.23.56. dying bad. Any time the php script tried to do _anything_ with the db (like, um, opening it?), i'd get this in the mysql error logs: /usr/local/libexec/mysqld: ready for connections 030329 19:52:31 mysqld restarted Cannot initialize InnoDB as 'innodb_data_file_path' is not set. If you do not want to use transactional InnoDB tables, add a line skip-innodb to the [mysqld] section of init parameters in your my.cnf or my.ini. If you want to use InnoDB tables, add to the [mysqld] section, for example, innodb_data_file_path = ibdata1:10M:autoextend But to get good performance you should adjust for your hardware the InnoDB startup options listed in section 2 at http://www.innodb.com/ibman.html /usr/local/libexec/mysqld: ready for connections mysqld got signal This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail key_buffer_size=8388600 record_buffer=131072 sort_buffer=2097144 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K bytes of memory Hope that's ok, if not, decrease some variables in the equation The line that is causing all of this is: $db = mysql_connect("127.0.0.1", "","") The mysql console client (ie: 'mysql' at command line) works just fine. php/mysql/apache have all been compiled from ports. I have tried everything I could possibly think of, including recompiling php. No dice. I've not really heard much about anyone else having this problem. I could go back to using 3.23.54 and it would all work ok, but I'd really rather figure out what the problem is. The webpage that is having the issues (so you can see the problem firsthand) is http://perlpimp.codersluts.net/pics.php. Ugh. I hope someone here has an idea of what is going on, because I'm lost. Randi