Re: can't start daemon
Anthony Ettinger wrote: i actually don't have anything valuable in my database, it's on my home pc. I upgraded with the standard procedure. On 6/17/06, Dan Trainor [EMAIL PROTECTED] wrote: Anthony Ettinger wrote: I just upgraded to mysql 5, and can't restart the daemon. 060617 11:57:22 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=spring-bin' to avoid this problem. InnoDB: Error: log file ./ib_logfile0 is of different size 0 8388608 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 060617 11:57:23 [Warning] './mysql/host' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [Warning] './mysql/user' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [Warning] './mysql/db' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. 060617 11:57:43 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=spring-bin' to avoid this problem. InnoDB: Error: log file ./ib_logfile0 is of different size 0 8388608 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 060617 11:57:43 [Warning] './mysql/host' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [Warning] './mysql/user' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [Warning] './mysql/db' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. Hi - Which version did you upgrade to? Did you follow the appropriate upgrade guides? Thanks -dant Hi - Please don't top-post. Which version did you upgrade from, and which upgrade procedure did you follow? Thanks -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: can't start daemon
Anthony Ettinger wrote: I just upgraded to mysql 5, and can't restart the daemon. 060617 11:57:22 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=spring-bin' to avoid this problem. InnoDB: Error: log file ./ib_logfile0 is of different size 0 8388608 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 060617 11:57:23 [Warning] './mysql/host' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [Warning] './mysql/user' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [Warning] './mysql/db' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. 060617 11:57:43 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=spring-bin' to avoid this problem. InnoDB: Error: log file ./ib_logfile0 is of different size 0 8388608 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 060617 11:57:43 [Warning] './mysql/host' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [Warning] './mysql/user' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [Warning] './mysql/db' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. Hi - Which version did you upgrade to? Did you follow the appropriate upgrade guides? Thanks -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: can't start daemon
i actually don't have anything valuable in my database, it's on my home pc. I upgraded with the standard procedure. On 6/17/06, Dan Trainor [EMAIL PROTECTED] wrote: Anthony Ettinger wrote: I just upgraded to mysql 5, and can't restart the daemon. 060617 11:57:22 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=spring-bin' to avoid this problem. InnoDB: Error: log file ./ib_logfile0 is of different size 0 8388608 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 060617 11:57:23 [Warning] './mysql/host' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [Warning] './mysql/user' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [Warning] './mysql/db' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:23 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. 060617 11:57:43 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=spring-bin' to avoid this problem. InnoDB: Error: log file ./ib_logfile0 is of different size 0 8388608 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 060617 11:57:43 [Warning] './mysql/host' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [Warning] './mysql/user' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [Warning] './mysql/db' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed 060617 11:57:43 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. Hi - Which version did you upgrade to? Did you follow the appropriate upgrade guides? Thanks -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- Anthony Ettinger Signature: http://chovy.dyndns.org/hcard.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: can't start daemon after reboot (after initial install)
Bill, Tuesday, September 03, 2002, 6:08:57 AM, you wrote: BF I installed 3.23.52 on a RedHat 7.3 machine. Everything was just fine until I BF rebooted later for another reason. Now I can't start the daemon. I tried BF deleting /var/lib/mysql/mysql.sock as root. It deleted, but to no avail. Any BF idea what I have done wrong? I don't understand sockets. They're magic to me. BF ps shows no daemon running. mysqladmin also show no daemon and won't ping BF ...Bill BF -- BF [username $] /usr/sbin/mysqld BF 020902 20:58:00 Can't start server : Bind on unix socket: Permission denied BF 020902 20:58:00 Do you already have another mysqld server running on socket: BF /var/lib/mysql/mysql.sock ? BF 020902 20:58:00 Aborting BF 020902 20:58:00 /usr/sbin/mysqld: Shutdown Complete Check if there is another MySQL server running. Check permissions on the MySQL data dir. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
