Go Back   Forum Care Forums > Development Reference Area > MySQL Discussion

Reply
 
LinkBack Thread Tools Display Modes
Can not start mysqld on Solaris 9
Old
  (#1)
Easy User
Guest
 
Posts: n/a
Default Can not start mysqld on Solaris 9 - 06-04-2007, 07:46 AM

Need your help on starting 5.0.24 on a Solaris 9 system.

Installed it from mysql-standard-5.0.24-solaris9-sparc-64bit.pkg,
then ran scripts/mysql_install_db but after that bin/mysqld_safe quits


I see that "data/myhost.err" has the following message:
[ERROR] Fatal error: Can't open and lock privilege tables: Table
'mysql.host' doesn't exist

For /etc/my.cnf, I used the sample my-huge.cnf and uncommented the
InnoDB lines.

What am I doing wrong?

Thanks for your help.

Here are the relevant output:

$ uname -a
SunOS myhost 5.9 Generic_117171-17 sun4u sparc SUNW,UltraAX-MP

$ bin/mysqld_safe
Starting mysqld daemon with databases from /opt/mysql/mysql/data
STOPPING server from pid file /opt/mysql/mysql/data/myhost.pid
070109 18:59:16 mysqld ended

$ ls -la data
total 41020
drwxr-xr-x 4 mysql mysql 512 Jan 9 18:18 .
drwxr-xr-x 14 root bin 512 Jan 9 18:16 ..
-rw-rw---- 1 mysql mysql 5242880 Jan 9 18:18 ib_logfile0
-rw-rw---- 1 mysql mysql 5242880 Jan 9 18:18 ib_logfile1
-rw-rw---- 1 mysql mysql 10485760 Jan 9 18:18 ibdata1
-rw-rw---- 1 mysql root 1025 Jan 9 18:18 myhost.err
drwxr-xr-x 2 mysql mysql 512 Jan 9 18:16 mysql
drwxr-xr-x 2 mysql mysql 512 Jan 9 18:16 test

btw, data/mysql and data/test are empty directories

$ pkginfo -l mysql
PKGINST: mysql
NAME: MySQL Community Edition - Standard (GPL)
CATEGORY: application
ARCH: sun4u
VERSION: 5.0.24
BASEDIR: /opt/mysql
VENDOR: MySQL AB
PSTAMP: MySQL AB Build Engineers
INSTDATE: Jan 09 2007 18:15
EMAIL: EMAIL REMOVED
STATUS: completely installed
FILES: 1693 installed pathnames
54 directories
100 executables
183787 blocks used (approx)

$ cat data/myhost.err
070109 18:18:51 mysqld started
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
070109 18:18:51 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
070109 18:18:52 InnoDB: Log file ./ib_logfile0 did not exist: new to
be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
070109 18:18:53 InnoDB: Log file ./ib_logfile1 did not exist: new to
be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
070109 18:18:54 InnoDB: Started; log sequence number 0 0
070109 18:18:54 [ERROR] Fatal error: Can't open and lock privilege
tables: Table 'mysql.host' doesn't exist
070109 18:18:54 mysqld ended


--- begin /etc/my.cnf, from my-huge.cnf --------------------
# Example MySQL config file for very large systems.
#
# This is for a large system with memory of 1G-2G where the system runs
mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be p***ed to all MySQL clients
[client]
#p***word = your_p***word
port = 3306
socket = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port = 3306
socket = /tmp/mysql.sock
skip-locking
key_buffer = 384M
max_allowed_packet = 1M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

# Don't listen on a TCP/IP port at all. This can be a security
enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named
pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_P***WORD=<p***word> ;
#
# where you replace <host>, <user>, <p***word> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_P***WORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method,
then
# start replication for the first time (even unsuccessfully, for
example
# if you mistyped the p***word in master-p***word and the slave
fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored
and
# overridden by the content of the master.info file, unless you
shutdown
# the slave server, delete master.info and restart the slaver
server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The p***word the slave will authenticate with when connecting to
# the master - required
#master-p***word = <p***word>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 384M
#bdb_max_lock = 100000

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /usr/local/mysql/data/
innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
innodb_log_group_home_dir = /usr/local/mysql/data/
innodb_log_arch_dir = /usr/local/mysql/data/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 384M
innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 100M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

--- end /etc/my.cnf, from my-huge.cnf ---------------------

   
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

Re: Can not start mysqld on Solaris 9
Old
  (#2)
Riemer Palstra
Guest
 
Posts: n/a
Default Re: Can not start mysqld on Solaris 9 - 06-04-2007, 07:46 AM

On 2007-01-10, Easy User <EMAIL REMOVED> wrote:
> Installed it from mysql-standard-5.0.24-solaris9-sparc-64bit.pkg, then
> ran scripts/mysql_install_db but after that bin/mysqld_safe quits


[ ... ]

> I see that "data/myhost.err" has the following message:
> [ERROR] Fatal error: Can't open and lock privilege tables: Table
> 'mysql.host' doesn't exist


> btw, data/mysql and data/test are empty directories


If the mysql.host table doesn't exist and the mysql subdirectory is
empty, I get the suspicion the mysql_install_db script did not run
correctly. What output did it give and can you try running it again?

--
Riemer Palstra Amsterdam, The Netherlands
EMAIL REMOVED http://www.palstra.com/
   
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Re: Can not start mysqld on Solaris 9
Old
  (#3)
Easy User
Guest
 
Posts: n/a
Default Re: Can not start mysqld on Solaris 9 - 06-04-2007, 07:46 AM

Thanks for your message.

The mysql_install_db did not show any error.

But instead of trying it again with the same version, I removed
the package, downloaded the pre-packaged 5.0.27 from sunfreeware.com,
installed it and the new mysqld is now up and running.

Thanks again.

Riemer Palstra wrote:
> On 2007-01-10, Easy User <EMAIL REMOVED> wrote:
> > Installed it from mysql-standard-5.0.24-solaris9-sparc-64bit.pkg, then
> > ran scripts/mysql_install_db but after that bin/mysqld_safe quits

>
> [ ... ]
>
> > I see that "data/myhost.err" has the following message:
> > [ERROR] Fatal error: Can't open and lock privilege tables: Table
> > 'mysql.host' doesn't exist

>
> > btw, data/mysql and data/test are empty directories

>
> If the mysql.host table doesn't exist and the mysql subdirectory is
> empty, I get the suspicion the mysql_install_db script did not run
> correctly. What output did it give and can you try running it again?
>
> --
> Riemer Palstra Amsterdam, The Netherlands
> EMAIL REMOVED http://www.palstra.com/


   
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Contact Us - Forum Care Forums - Archive - Top