From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 4 00:12:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC8B916A4CE for ; Sat, 4 Sep 2004 00:12:11 +0000 (GMT) Received: from beer.ux6.net (beer.ux6.net [64.62.253.29]) by mx1.FreeBSD.org (Postfix) with SMTP id C9AE543D41 for ; Sat, 4 Sep 2004 00:12:11 +0000 (GMT) (envelope-from miha@ghuug.org) Received: (qmail 52642 invoked by uid 113); 3 Sep 2004 17:12:11 -0700 Received: from miha@ghuug.org by beer.ux6.net by uid 112 with qmail-scanner-1.22 Clear:RC:0(205.177.65.128):SA:0(0.0/6.0):. Processed in 2.117062 secs); 04 Sep 2004 00:12:11 -0000 X-Spam-Status: No, hits=0.0 required=6.0 Received: from unknown (HELO ?192.168.0.3?) (miha@beer.ux6.net@205.177.65.128) by localhost with SMTP; 3 Sep 2004 17:12:09 -0700 From: "Mikhail P." Organization: Ghana Unix Users Group To: freebsd-amd64@freebsd.org Date: Sat, 4 Sep 2004 00:12:02 +0000 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200409040012.02989.miha@ghuug.org> Subject: mysql refuses to work with outside network connections.. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: miha@ghuug.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2004 00:12:12 -0000 Dear AMD64 Users, This post is probably my last resort to get mysql working on AMD64.. Ok, so we've got new AMD64 box today. The role of the box is to be dedicated MySQL server for one site (php/mysql driven). FreeBSD-5.2.1 amd64 was installed on it, so basically it all started as clean install. First thing I did - upgraded system to "-p9" and cvsup'ed ports tree. Next, I installed mysql port (database/mysql40-server) as usual (the only option passed to make - "WITH_XCHARSET=all"). So far so good - mysql build complete in few minutes, and I started mysql server (/usr/local/etc/rc.d/mysql-server.sh start); created database and then imported mysql data from file into mysql - cheers, mysql runs fine. what next? I need to connect to created mysql database from another server, so basically mysql to be used from network rather from local socket. That's where all problems pop-up - content server cannot connect to MySQL server. I went to check logs, and found a lot of the following in /var/log/messages: Sep 3 16:51:20 amd mysqld[60076]: warning: can't get client address: Bad file descriptor next I went to check mysql's log in /var/db/mysql, and here's what was there (a lot of entries - on every connect from network) - mysqld got signal 11; 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=16777216 read_buffer_size=258048 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Number of processes running now: 0 040903 16:40:58 mysqld restarted -------------------------- So basically mysql wasn't usable from network. after playing with my.cnf, trying various mysql versions (mysql41-server), playing with network and everything I could suspect, I did not find what is the problem.. To summarize - MySQL works from localhost via mysql.sock, but does not from network. mysql client from content server shows: [miha]@[beer]:~> mysql -h 192.168.200.3 -u vh1 ERROR 2013: Lost connection to MySQL server during query [miha]@[beer]:~> and these logs appear on mysql server. I'm totally lost to this point - I've read mailing lists, and I see a lot of people run MySQL on AMD64.. Here's hardware details (if that makes any sence at all): CPU: AMD Athlon(tm) 64 Processor 3400+ RAM: 1.5GB Motherboard: ASUS KV8 SE deluxe SCSI Controller: ahd0: port 0xb000-0xb0ff,0xb400-0xb4ff mem 0xf3d00000-0xf3d01fff irq 10 at device 12.0 on pci0 aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs SCSI drive: SeaGate 15k RPM SCSI, 18GB Because machine has 1.5GB of available RAM, I don't think that: "It is possible that mysqld could use up to 92783 Kbytes of memory" log entries hold any truth. I have attached current my.cnf (which is basically taken from /usr/local/share/mysql/my-medium.cnf). I would *greatly* appreciate any pointers on this issue - I have searched google, all mailing lists, but could not find anything similar to my problem.. kind regards, M. ======== my.cnf ============ [client] port = 3306 socket = /var/db/mysql/mysql.sock [mysqld] port = 3306 socket = /var/db/mysql/mysql.sock skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M skip-innodb log-bin server-id = 1 [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash [isamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout