Re: mysql.sock file exists, but still cannot connect to server
Okay, with the good help I was getting, and looking at the all clues MySQL was giving me, like Table 'mysql.host' doesn't exist and Can't find file: './mysql/host.frm', I concluded that the 4.1.9 installation conflicts with the default 4.0.18 installation. For instance, 4.0.18 expects files in /var/mysql and /usr/libexec, but 4.1.9 wants them in /usr/local/mysql, etc. There isn't a mysql/data directory anywhere at all for 4.0.18. The two seem incompatible (at least, it's beyond me...). So, I backed out my 4.1.9 installation, and was able to get things going again under 4.0.18. I guess I'll have to wait until Apple upgrades MySQL with OS X 10.3.8. Thanks to all! Alex -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql.sock file exists, but still cannot connect to server
I've upgraded to mysql 4.1.9 on Mac OS X 10.3.7, but now things won't start up. In the console I get these messages: The database cluster will be initialized with locale C. creating directory /var/db/RemoteManagement/RMDB/rmdb.data... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/base... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/global... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/pg_xlog... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/pg_clog... ok creating template1 database in /var/db/RemoteManagement/RMDB/rmdb.data/base/1... ok creating configuration files... ok initializing pg_shadow... ok enabling unlimited row size for system tables... ok initializing pg_depend... ok creating system views... ok loading pg_description... ok creating conversions... ok setting privileges on built-in objects... ok vacuuming database template1... ok copying template1 to template0... ok Success. You can now start the database server using: /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/postmaster -D /var/db/RemoteManagement/RMDB/rmdb.data or /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/pg_ctl -D /var/db/RemoteManagement/RMDB/rmdb.data -l logfile start LOG: database system was shut down at 2005-01-19 12:36:29 PST LOG: checkpoint record is at 0/71524 LOG: redo record is at 0/71524; undo record is at 0/0; shutdown TRUE LOG: next transaction id: 1744; next oid: 16766 LOG: database system is ready ERROR: To use passwords, you have to revoke permissions on pg_shadow so normal users cannot read the passwords. Try 'REVOKE ALL ON pg_shadow FROM PUBLIC'. MySQL seems to be running: 649 ?? S 0:00.02 /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/postmaster -D /var/db/RemoteManagement/RMDB/rmdb.data When I run MySQLManager, I get this error message: 2005-01-19 12:37:34.328 MySQLInfoTool[667] Initial attempt at db installation failed, probably due to bad hostname; trying again with force option. ERROR: 1064 You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 050119 12:37:34 Aborting 050119 12:37:34 /usr/libexec/mysqld: Shutdown Complete When I type mysql at the command line, I get: ERROR 2002: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) ...yet the file exists: srwxrwxrwx 1 mysql wheel0 19 Jan 12:35 mysql.sock Any ideas about what to do? I've reinstalled the mySQL package, but it didn't change things. Thanks! Alex -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql.sock file exists, but still cannot connect to server
Alex Majora wrote: I've upgraded to mysql 4.1.9 on Mac OS X 10.3.7, but now things won't start up. In the console I get these messages: The database cluster will be initialized with locale C. creating directory /var/db/RemoteManagement/RMDB/rmdb.data... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/base... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/global... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/pg_xlog... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/pg_clog... ok creating template1 database in /var/db/RemoteManagement/RMDB/rmdb.data/base/1... ok creating configuration files... ok initializing pg_shadow... ok enabling unlimited row size for system tables... ok initializing pg_depend... ok creating system views... ok loading pg_description... ok creating conversions... ok setting privileges on built-in objects... ok vacuuming database template1... ok copying template1 to template0... ok Success. You can now start the database server using: What is this? These messages do not appear to have come from mysql. There's something you haven't told us. What is RemoteManagement/RMDB? Is this something you run by hand, or something automated? /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/postmaster -D /var/db/RemoteManagement/RMDB/rmdb.data or /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/pg_ctl -D /var/db/RemoteManagement/RMDB/rmdb.data -l logfile start LOG: database system was shut down at 2005-01-19 12:36:29 PST LOG: checkpoint record is at 0/71524 LOG: redo record is at 0/71524; undo record is at 0/0; shutdown TRUE LOG: next transaction id: 1744; next oid: 16766 LOG: database system is ready ERROR: To use passwords, you have to revoke permissions on pg_shadow so normal users cannot read the passwords. Try 'REVOKE ALL ON pg_shadow FROM PUBLIC'. Have you tried doing what it says here? MySQL seems to be running: 649 ?? S 0:00.02 /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/postmaster -D /var/db/RemoteManagement/RMDB/rmdb.data That doesn't appear to be mysql. When I run MySQLManager, I get this error message: 2005-01-19 12:37:34.328 MySQLInfoTool[667] Initial attempt at db installation failed, probably due to bad hostname; trying again with force option. ERROR: 1064 You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 That certainly seems to be a message (syntax error) from mysql. 050119 12:37:34 Aborting 050119 12:37:34 /usr/libexec/mysqld: Shutdown Complete Not sure why, but mysqld just shut down. When I type mysql at the command line, I get: ERROR 2002: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) Are you sure mysqld is running? You got a shutdown message right before this. ...yet the file exists: srwxrwxrwx 1 mysql wheel0 19 Jan 12:35 mysql.sock Well, that should mean mysqld is running. Two things: 1) Use ps to make sure there's a mysqld process (ps -aux | grep mysqld). 2) Check the permissions on /tmp (actually, /private/tmp under OS X). Some OS X updates have changed /tmp permissions in the past. Any ideas about what to do? I've reinstalled the mySQL package, but it didn't change things. Thanks! Alex Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql.sock file exists, but still cannot connect to server
Michael Stassen wrote: That doesn't appear to be mysql. Now that I look closely, that must be a database for RMDB. Sorry I got the two confused. Are you sure mysqld is running? You got a shutdown message right before this. Apparently, it's not running, as there is no mysqld process running in the ps -aux listing. However, if I try to start mysqld up again, I get: 050119 14:48:43 Can't start server : Bind on unix socket: Address already in use 050119 14:48:43 Do you already have another mysqld server running on socket: /tmp/mysql.sock ? 050119 14:48:43 Aborting 050119 14:48:43 /usr/libexec/mysqld: Shutdown Complete Check the permissions on /tmp drwxrwxrwt 14 root wheel 476 19 Jan 14:43 /private/tmp Don't know if this is what it's supposed to be for /tmp. Thanks for your help! Alex -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql.sock file exists, but still cannot connect to server
The postmaster is a Postgres daemon, and pg_shadow is the user table for postgres. Clint From: Michael Stassen [EMAIL PROTECTED] To: Alex Majora [EMAIL PROTECTED] CC: mysql@lists.mysql.com Subject: Re: mysql.sock file exists, but still cannot connect to server Date: Wed, 19 Jan 2005 17:42:34 -0500 Alex Majora wrote: I've upgraded to mysql 4.1.9 on Mac OS X 10.3.7, but now things won't start up. In the console I get these messages: The database cluster will be initialized with locale C. creating directory /var/db/RemoteManagement/RMDB/rmdb.data... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/base... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/global... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/pg_xlog... ok creating directory /var/db/RemoteManagement/RMDB/rmdb.data/pg_clog... ok creating template1 database in /var/db/RemoteManagement/RMDB/rmdb.data/base/1... ok creating configuration files... ok initializing pg_shadow... ok enabling unlimited row size for system tables... ok initializing pg_depend... ok creating system views... ok loading pg_description... ok creating conversions... ok setting privileges on built-in objects... ok vacuuming database template1... ok copying template1 to template0... ok Success. You can now start the database server using: What is this? These messages do not appear to have come from mysql. There's something you haven't told us. What is RemoteManagement/RMDB? Is this something you run by hand, or something automated? /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/postmaster -D /var/db/RemoteManagement/RMDB/rmdb.data or /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/pg_ctl -D /var/db/RemoteManagement/RMDB/rmdb.data -l logfile start LOG: database system was shut down at 2005-01-19 12:36:29 PST LOG: checkpoint record is at 0/71524 LOG: redo record is at 0/71524; undo record is at 0/0; shutdown TRUE LOG: next transaction id: 1744; next oid: 16766 LOG: database system is ready ERROR: To use passwords, you have to revoke permissions on pg_shadow so normal users cannot read the passwords. Try 'REVOKE ALL ON pg_shadow FROM PUBLIC'. Have you tried doing what it says here? MySQL seems to be running: 649 ?? S 0:00.02 /System/Library/CoreServices/RemoteManagement/rmdb.bundle/bin/postmaster -D /var/db/RemoteManagement/RMDB/rmdb.data That doesn't appear to be mysql. When I run MySQLManager, I get this error message: 2005-01-19 12:37:34.328 MySQLInfoTool[667] Initial attempt at db installation failed, probably due to bad hostname; trying again with force option. ERROR: 1064 You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 That certainly seems to be a message (syntax error) from mysql. 050119 12:37:34 Aborting 050119 12:37:34 /usr/libexec/mysqld: Shutdown Complete Not sure why, but mysqld just shut down. When I type mysql at the command line, I get: ERROR 2002: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) Are you sure mysqld is running? You got a shutdown message right before this. ...yet the file exists: srwxrwxrwx 1 mysql wheel0 19 Jan 12:35 mysql.sock Well, that should mean mysqld is running. Two things: 1) Use ps to make sure there's a mysqld process (ps -aux | grep mysqld). 2) Check the permissions on /tmp (actually, /private/tmp under OS X). Some OS X updates have changed /tmp permissions in the past. Any ideas about what to do? I've reinstalled the mySQL package, but it didn't change things. Thanks! Alex Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql.sock file exists, but still cannot connect to server
Additionally, this is what I get when I try to launch mysqld manually: $ sudo ./bin/mysqld_safe [1] 2058 Starting mysqld daemon with databases from /usr/local/mysql/data STOPPING server from pid file /usr/local/mysql/data/whitestar.alpha.net.pid 050119 17:13:12 mysqld ended Is there a way to have mysqld issue more verbose error messages? Thanks! Alex -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql.sock file exists, but still cannot connect to server
Alex Majora wrote: Michael Stassen wrote: That doesn't appear to be mysql. Now that I look closely, that must be a database for RMDB. Sorry I got the two confused. Are you sure mysqld is running? You got a shutdown message right before this. Apparently, it's not running, as there is no mysqld process running in the ps -aux listing. However, if I try to start mysqld up again, I get: 050119 14:48:43 Can't start server : Bind on unix socket: Address already in use 050119 14:48:43 Do you already have another mysqld server running on socket: /tmp/mysql.sock ? 050119 14:48:43 Aborting 050119 14:48:43 /usr/libexec/mysqld: Shutdown Complete As you probably know, mysqld should create /tmp/mysql.sock on startup and destroy it on shutdown. As long as you are certain that mysqld is not running, that would mean that it wasn't shut down properly last time and left the socket file in the way. In that case, removing it manually with sudo rm /tmp/mysql.sock should allow mysqld to start. Check the permissions on /tmp drwxrwxrwt 14 root wheel 476 19 Jan 14:43 /private/tmp That's as it should be. Don't know if this is what it's supposed to be for /tmp. Thanks for your help! Alex Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql.sock file exists, but still cannot connect to server
Details should be in the .err file in the data directory (/usr/local/mysql/data/whitestar.alpha.net.err, in your case). Michael Alex Majora wrote: Additionally, this is what I get when I try to launch mysqld manually: $ sudo ./bin/mysqld_safe [1] 2058 Starting mysqld daemon with databases from /usr/local/mysql/data STOPPING server from pid file /usr/local/mysql/data/whitestar.alpha.net.pid 050119 17:13:12 mysqld ended Is there a way to have mysqld issue more verbose error messages? Thanks! Alex -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql.sock file exists, but still cannot connect to server
On Wednesday, January 19, 2005 9:14 PM Michael Stassen wrote: Details should be in the .err file in the data directory Here's the contents of the file: 050119 17:30:02 mysqld started 050119 17:30:02 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive 050119 17:30:02 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 050119 17:30:02 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 43634. InnoDB: Doing recovery: scanned up to log sequence number 0 43634 050119 17:30:02 InnoDB: Flushing modified pages from the buffer pool... 050119 17:30:02 InnoDB: Started; log sequence number 0 43634 050119 17:30:02 [ERROR] Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't exist 050119 17:30:02 mysqld ended It would seem that the issue about table 'mysql.host' is the problem. Is there a way to create this table outside of mysql? Or does this indicate no schema at all in the DB? Thanks! Alex -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
