Solved

mysql is not connecting in solaris

Posted on 2009-07-09
10
1,320 Views
Last Modified: 2013-12-05
hi
i have installed the virtual solaris i have installed mysql on the solaris 10 and it was succesful but the problem is actually its not letting me connect
i am getting this error
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

please advice
0
Comment
Question by:mattibutt
  • 7
  • 3
10 Comments
 
LVL 11

Author Comment

by:mattibutt
ID: 24812245
this what i get when i issue the following command
 ps -ef | grep mysq
    root  2150  2075   0 20:08:59 pts/3       0:00 grep mysq
0
 
LVL 33

Accepted Solution

by:
snoyes_jw earned 500 total points
ID: 24813169
The MySQL server is not running. Start it.
0
 
LVL 11

Author Comment

by:mattibutt
ID: 24813219
how do i?
0
 
LVL 11

Author Comment

by:mattibutt
ID: 24813244
i am using coolstack but mysql is not working whatever i do its catching errors

=================

VERSION

==================

MySQL 5.1.25 32bit
 

=================

BUILD NOTES

==================

This directory contains pre-built, optimized binaries and libraries.

This 32-bit version is used by Apache/PHP for client-side access.

For the database server, we recommend using the 64-bit version, which 

is a seperate package. 
 

MySQL 5.1.25 32 bit is built with Sun Studio 12 on sparc and using gcc on

Solaris x86 as follows :
 

For sparc,

CXXFLAGS="-fast -xtarget=generic -fsimple=1 -fns=no -mt -DHAVE_RWLOCK"

For x86,

CXXFLAGS="-O3 -D_REENTRANT -fPIC"
 

CFLAGS="$CXXFLAGS"

export CFLAGS CXXFLAGS

INSTALLDIR=/opt/coolstack

gmake distclean
 

CFLAGS="$CFLAGS" CXXFLAGS="$CFLAGS" ./configure 

                --prefix=$INSTALLDIR/mysql_32bit 

                --localstatedir=$INSTALLDIR/mysql_32bit/data 

                --libexecdir=$INSTALLDIR/mysql_32bit/bin 

                --with-extra-charsets=complex 

                --with-archive-storage-engine 

                --with-blackhole-storage-engine 

                --with-csv-storage-engine 

                --with-example-storage-engine 

                --with-federated-storage-engine 

                --with-innodb 

                --with-readline 

                --enable-thread-safe-client 

                --enable-local-infile 

                --with-named-z-libs=no 

                --with-big-tables 

                --with-ndbcluster 

                --with-mysqld-libs="-lmtmalloc" 

                --enable-shared 

                --with-embedded-server 

                --with-pic 

                --with-server-suffix=-standard
 

gmake && gmake install
 

===================

CONFIGURATION NOTES

===================
 

a)create mysql user and group and change install directory ownership 
 

# groupadd mysql

# useradd -g mysql matti
 

b)Initialize the database tables

# /opt/coolstack/mysql_32bit/bin/mysql_install_db
 

If you don't have datadir set in the default configuration file my.cnf, this

will create two directories mysql and test in /opt/coolstack/mysql_32bit/data

directory.  mysql directory has the MySQL privilege tables. test has the "test"

database These two directories are needed for mysql to start. If you are using

a different data directory later, you need to copy these two directories over.
 

(c) Change the ownership of data directory.

# chown -R mysql:mysql /opt/coolstack/mysql_32bit/data
 

d)To start MySQL, run
 

# /opt/coolstack/mysql_32bit/bin/mysqld_safe & 
 

To shutdown MySQL, you can either run

# /opt/coolstack/mysql_32bit/bin/mysqladmin shut
 

The log file for MySQL is  by default at the data directory

/opt/coolstack/mysql_32bit/data/<hostname>.err unless you specify a different

data path. By monitoring this log file you can find out if failures occur and

why.
 

=============

SMF notes :

=============

* Before start using SMF, make sure DB_DIR is set correctly in

  /opt/coolstack/lib/svc/method/svc-cskmysql32. By default, the DB_DIR is set to

  /opt/coolstack/mysql_32bit/data

* Your data directory should be owned by mysql/mysql.

  # chown -R mysql:mysql <path_to_data_dir>
 

Once mysql is configured properly. 

To start mysql :

# svcadm enable mysql32-csk

To stop mysql

# svcadm disable mysql32-csk

To check the status whether mysql is running or not.

# svcs -a mysql32-csk

disabled       16:04:58 svc:/application/database/mysql:mysql32-csk
 

To put the service into maintenance mode.

# svcadm mark maintenance mysql32-csk
 

Files location:

--------------

SMF log file location :

/var/svc/log/application-database-mysql\:mysql32-csk.log
 

Mainfest file location : /var/svc/manifest/network/cskmysql32.xml
 

Shell script location which smf uses to start/stop :

/opt/coolstack/lib/svc/method/svc-cskmysql32
 
 

What to do if mysql failed to start :

-------------------------------------

   If mysql fails to start then SMF will be put into maintenance mode. Fix the

configuration errors.

Then first clear the maintenance mode e.g

# svcadm clear mysql32-csk
 

Then try to restart the service :

# svcadm enable mysql32-csk
 

====================

Performance tuning :

====================

Mysql performance tuning for Solaris 10 OS :

http://developers.sun.com/solaris/articles/mysql_perf_tune.html
 

==============

Documentation 

==============

For more information on mysql, look at mysql documentation.

http://dev.mysql.com/doc/refman/5.1/en/
 

Here is the link to mysql tutorial :

http://dev.mysql.com/doc/refman/5.1/en/tutorial.html
 

==============

Miscellaneous 

==============

mysqlhotcopy uses /opt/coolstack/bin/perl. So to use mysqlhotcopy, you need to

install CSKperl package. CSKperl is not a dependent package to CSKmysql.

Open in new window

0
 
LVL 11

Author Comment

by:mattibutt
ID: 24813249
THE BELOW IS THE INTERACTION I HAD SINCE I INSTALLED MYSQL

mysql: not found

# CXXFLAGS="-O3 -D_REENTRANT -fPIC

> mysql

> help

> ?

> show databases;

> useradd -g mysql matti

> ^C

# ^X^C

# useradd -g mysql matti

# /opt/coolstack/mysql_32bit/bin/mysql_install_db

Installing MySQL system tables...

OK

Filling help tables...

OK
 

To start mysqld at boot time you have to copy

support-files/mysql.server to the right place for your system
 

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !

To do so, start the server, then issue the following commands:
 

/opt/coolstack/mysql_32bit/bin/mysqladmin -u root password 'new-password'

/opt/coolstack/mysql_32bit/bin/mysqladmin -u root -h unknown password 'new-passw ord'
 

Alternatively you can run:

/opt/coolstack/mysql_32bit/bin/mysql_secure_installation
 

which will also give you the option of removing the test

databases and anonymous user created by default.  This is

strongly recommended for production servers.
 

See the manual for more instructions.
 

You can start the MySQL daemon with:

cd /opt/coolstack/mysql_32bit ; /opt/coolstack/mysql_32bit/bin/mysqld_safe &
 

You can test the MySQL daemon with mysql-test-run.pl

cd /opt/coolstack/mysql_32bit/mysql-test ; perl mysql-test-run.pl
 

Please report any problems with the /opt/coolstack/mysql_32bit/bin/mysqlbug scri pt!
 

The latest information about MySQL is available at http://www.mysql.com/

Support MySQL by buying support/licenses from http://shop.mysql.com/
 

# /opt/coolstack/mysql_32bit/bin/mysqld_safe &

2612

# 090708 22:32:28 mysqld_safe Logging to '/opt/coolstack/mysql_32bit/data/unknow n.err'.

090708 22:32:29 mysqld_safe Starting mysqld daemon with databases from /opt/cool stack/mysql_32bit/data

090708 22:32:29 mysqld_safe mysqld from pid file /opt/coolstack/mysql_32bit/data /unknown.pid ended

^C

# /opt/coolstack/mysql_32bit/bin/mysql_install_db

Installing MySQL system tables...

OK

Filling help tables...

OK
 

To start mysqld at boot time you have to copy

support-files/mysql.server to the right place for your system
 

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !

To do so, start the server, then issue the following commands:
 

/opt/coolstack/mysql_32bit/bin/mysqladmin -u root password 'new-password'

/opt/coolstack/mysql_32bit/bin/mysqladmin -u root -h unknown password 'new-passw ord'
 

Alternatively you can run:

/opt/coolstack/mysql_32bit/bin/mysql_secure_installation
 

which will also give you the option of removing the test

databases and anonymous user created by default.  This is

strongly recommended for production servers.
 

See the manual for more instructions.
 

You can start the MySQL daemon with:

cd /opt/coolstack/mysql_32bit ; /opt/coolstack/mysql_32bit/bin/mysqld_safe &
 

You can test the MySQL daemon with mysql-test-run.pl

cd /opt/coolstack/mysql_32bit/mysql-test ; perl mysql-test-run.pl
 

Please report any problems with the /opt/coolstack/mysql_32bit/bin/mysqlbug scri pt!
 

The latest information about MySQL is available at http://www.mysql.com/

Support MySQL by buying support/licenses from http://shop.mysql.com/
 

# /opt/coolstack/mysql_32bit/bin/mysqld_safe

090708 22:33:32 mysqld_safe Logging to '/opt/coolstack/mysql_32bit/data/unknown. err'.

090708 22:33:33 mysqld_safe Starting mysqld daemon with databases from /opt/cool stack/mysql_32bit/data

090708 22:33:33 mysqld_safe mysqld from pid file /opt/coolstack/mysql_32bit/data /unknown.pid ended

# svcadm enable mysql32-csk

# svcs -a mysql32-csk

svcs: -a ignored when used with arguments.

STATE          STIME    FMRI

maintenance    22:34:04 svc:/application/database/mysql:mysql32-csk

# mysql

mysql: not found

# mysql -u

mysql: not found

# /opt/coolstack/mysql_32bit/bin/mysqld_safe &

3386

# 090708 22:35:20 mysqld_safe Logging to '/opt/coolstack/mysql_32bit/data/unknown.err'.

090708 22:35:20 mysqld_safe Starting mysqld daemon with databases from /opt/coolstack/mysql_32bit/data

090708 22:35:20 mysqld_safe mysqld from pid file /opt/coolstack/mysql_32bit/data/unknown.pid ended

# /opt/coolstack/lib/svc/method/svc-cskmysql32
 

Usage: svc-cskmysql32 { start | stop | restart }
 

#  svc-cskmysql32 start

svc-cskmysql32: not found

# start

start: not found

#  svc-cskmysql32 { start}

svc-cskmysql32: not found

# chown -R mysql:mysql /opt/coolstack/mysql_32bit/data

# /opt/coolstack/mysql_32bit/bin/mysqld_safe &

3459

# 090708 22:37:26 mysqld_safe Logging to '/opt/coolstack/mysql_32bit/data/unknown.err'.

090708 22:37:26 mysqld_safe Starting mysqld daemon with databases from /opt/coolstack/mysql_32bit/data

^Z

#

Open in new window

0
Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 33

Expert Comment

by:snoyes_jw
ID: 24813278
Look in the error log. Usually mysql writes its own error log to the data dir; your distribution may have set errors to go to a system log instead.
0
 
LVL 11

Author Comment

by:mattibutt
ID: 24813313
this is whats in the error log
090708 22:32:29 mysqld_safe Starting mysqld daemon with databases from /opt/coolstack/mysql_32bit/data

/opt/coolstack/mysql_32bit/bin/mysqld: File './mysql-bin.index' not found (Errcode: 13)

090708 22:32:29 [ERROR] Aborting
 

090708 22:32:29 [Note] /opt/coolstack/mysql_32bit/bin/mysqld: Shutdown complete
 

090708 22:32:29 mysqld_safe mysqld from pid file /opt/coolstack/mysql_32bit/data/unknown.pid ended

090708 22:33:33 mysqld_safe Starting mysqld daemon with databases from /opt/coolstack/mysql_32bit/data

/opt/coolstack/mysql_32bit/bin/mysqld: File './mysql-bin.index' not found (Errcode: 13)

090708 22:33:33 [ERROR] Aborting
 

090708 22:33:33 [Note] /opt/coolstack/mysql_32bit/bin/mysqld: Shutdown complete
 

090708 22:33:33 mysqld_safe mysqld from pid file /opt/coolstack/mysql_32bit/data/unknown.pid ended

090708 22:35:20 mysqld_safe Starting mysqld daemon with databases from /opt/coolstack/mysql_32bit/data

/opt/coolstack/mysql_32bit/bin/mysqld: File './mysql-bin.index' not found (Errcode: 13)

090708 22:35:20 [ERROR] Aborting
 

090708 22:35:20 [Note] /opt/coolstack/mysql_32bit/bin/mysqld: Shutdown complete
 

090708 22:35:20 mysqld_safe mysqld from pid file /opt/coolstack/mysql_32bit/data/unknown.pid ended

090708 22:37:26 mysqld_safe Starting mysqld daemon with databases from /opt/coolstack/mysql_32bit/data

InnoDB: The first specified data file ./ibdata1 did not exist:

InnoDB: a new database to be created!

090708 22:37:26  InnoDB: Setting file ./ibdata1 size to 10 MB

InnoDB: Database physically writes the file full: wait...

090708 22:37:27  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...

090708 22:37:27  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

090708 22:37:27  InnoDB: Started; log sequence number 0 0

090708 22:37:27 [Note] Event Scheduler: Loaded 0 events

090708 22:37:27 [Note] /opt/coolstack/mysql_32bit/bin/mysqld: ready for connections.

Version: '5.1.25-rc-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

090708 22:41:16 mysqld_safe Starting mysqld daemon with databases from /opt/coolstack/mysql_32bit/data

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

090708 22:41:16  InnoDB: Retrying to lock the first data file

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to loc090708 22:44:22 mysqld_safe Starting mysqld daemon with databases from /opt/coolstack/mysql_32bit/data

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

090708 22:44:22  InnoDB: Retrying to lock the first data file

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

090708 22:46:03  InnoDB: Unable to open the first data file

InnoDB: Error in opening ./ibdata1

090708 22:46:03  InnoDB: Operating system error number 11 in a file operation.

InnoDB: Error number 11 means 'Resource temporarily unavailable'.

InnoDB: Some operating system error numbers are described at

InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html

InnoDB: Could not open or create data files.

InnoDB: If you tried to add new data files, and it failed here,

InnoDB: you should now edit innodb_data_file_path in my.cnf back

InnoDB: to what it was, and remove the new ibdata files InnoDB created

InnoDB: in this failed attempt. InnoDB only wrote those files full of

InnoDB: zeros, but did not yet use them in any way. But be careful: do not

InnoDB: remove old data files which contain your precious data!

090708 22:46:03 [ERROR] Plugin 'InnoDB' init function returned error.

090708 22:46:03 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

090708 22:46:03 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use

090708 22:46:03 [ERROR] Do you already have another mysqld server running on port: 3306 ?

090708 22:46:03 [ERROR] Aborting
 

090708 22:46:03 [Note] /opt/coolstack/mysql_32bit/bin/mysqld: Shutdown complete
 

090708 22:46:03 mysqld_safe mysqld from pid file /opt/coolstack/mysql_32bit/data/unknown.pid ended

Open in new window

0
 
LVL 33

Expert Comment

by:snoyes_jw
ID: 24813332
Those errors are fairly self-explanatory. Check what they tell you to.
0
 
LVL 11

Author Comment

by:mattibutt
ID: 24813354
hi
i know there is a problem with the port problem is this my first time ever when  using solaris 10
0
 
LVL 11

Author Closing Comment

by:mattibutt
ID: 31601505
thanks buddy
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

Both Easy and Powerful How easy is PHP? http://lmgtfy.com?q=how+easy+is+php (http://lmgtfy.com?q=how+easy+is+php)  Very easy.  It has been described as "a programming language even my grandmother can use." How powerful is PHP?  http://en.wikiped…
Password hashing is better than message digests or encryption, and you should be using it instead of message digests or encryption.  Find out why and how in this article, which supplements the original article on PHP Client Registration, Login, Logo…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
In a previous video, we went over how to export a DynamoDB table into Amazon S3.  In this video, we show how to load the export from S3 into a DynamoDB table.

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now