VectorLinux

The nuts and bolts => Installation & Updates => Topic started by: icedtea on December 12, 2007, 01:19:32 pm

Title: using MYSQL in VL 5.8
Post by: icedtea on December 12, 2007, 01:19:32 pm
hi. any idea how could i start using MYSQL ?

just installed the latest package.. then tried /usr/bin/mysql status : the output was

ERROR 2002 (HY000): Cant connect to local MySql server through socket '/var/run/mysql/mysql.sock' (2)
Title: Re: using MYSQL in VL 5.8
Post by: nightflier on December 12, 2007, 01:40:54 pm
You will need to initialize and configure your database. Do some search on post-install procedures.

Maybe start here: http://dev.mysql.com/doc/refman/5.0/en/unix-post-installation.html
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 12, 2007, 02:09:51 pm
You will need to initialize and configure your database. Do some search on post-install procedures.

Maybe start here: http://dev.mysql.com/doc/refman/5.0/en/unix-post-installation.html

ok thanks just bookmarked the page. . . il get back to this when i return to the offce. .btw got a little hard time installing 5.8 in Vmware. ..  process stops when i choose "yes" in the question/section:

"do you want to probe hardware settings (xorg)" --similar to that --- (this is the section BEFORE the default runlevel option is asked)


--the screen just leaves a black blank space after choosing "yes"--- in my third attempt of INSTALLATION i chose no.. then the rest was ok. ..
Title: Re: using MYSQL in VL 5.8
Post by: bigpaws on December 12, 2007, 02:12:07 pm
Goolge the problem:

/var/run/mysql/mysql.sock

Shows the third hit has the answer.

Bigpaws
Title: Re: using MYSQL in VL 5.8
Post by: rbistolfi on December 12, 2007, 02:16:22 pm
the hang in x configuration during the vmware install is a known issue, just choose no. Complete the install. If you can't login in gui mode, login in tui mode, as root do cp /etc/X11/xprg.conf-vesa /etc/X11/xorg.conf
Try to login in gui again. That should do it.
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 12, 2007, 02:26:40 pm
Goolge the problem:

/var/run/mysql/mysql.sock

Shows the third hit has the answer.

Bigpaws

yes actually i saw that already and i bookmarked it for review :)
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 12, 2007, 02:28:27 pm
the hang in x configuration during the vmware install is a known issue, just choose no. Complete the install. If you can't login in gui mode, login in tui mode, as root do cp /etc/X11/xprg.conf-vesa /etc/X11/xorg.conf
Try to login in gui again. That should do it.

it was ok during my 3rd attempt since i chose "NO" and now im using it to test my installed mysql database.
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 15, 2007, 11:35:13 pm
hi i am a bit confused. . does running / activating mysql needs an internet connection?  ??? ??? ??? ??? ???
Title: Re: using MYSQL in VL 5.8
Post by: nightflier on December 16, 2007, 06:01:43 am
mysql does not require an internet connection.

- You just need that to Google for the solutions -  :P
Title: Re: using MYSQL in VL 5.8
Post by: rbistolfi on December 16, 2007, 07:08:45 am
- You just need that to Google for the solutions -  :P

LOL.

Mysql is like a service, you can connect to a mysql database locally or through the internet if you want to. But is not a must. Actually this forum is using mysql, and this is an interface for the database, written in php.
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 17, 2007, 12:28:27 am
here are some of the OUTPUT that I encountered:

executing mysql_install_db using ROOT

Quote
Installing all prepared tables
Fill help tables

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:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h vector.linux.net password 'new-password'
See the manual for more instructions.

NOTE:  If you are upgrading from a MySQL <= 3.22.10 you should run
the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be
able to use the new GRANT command!

You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests

Please report any problems with the /usr/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at http://shop.mysql.com


CONTENTS OF SMALL.cnf

# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# 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 /var/lib/mysql) 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 passed to all MySQL clients
[client]
#password   = your_password
port      = 3306
socket      = /var/run/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port      = 3306
socket      = /var/run/mysql/mysql.sock
skip-locking
key_buffer = 16K
max_allowed_packet = 1M
table_cache = 4
sort_buffer_size = 64K
read_buffer_size = 256K
read_rnd_buffer_size = 256K
net_buffer_length = 2K
thread_stack = 64K

# 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
# (using the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
server-id   = 1

# Uncomment the following if you want to log updates
#log-bin=mysql-bin

# Uncomment the following if you are NOT using BDB tables
#skip-bdb

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#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 = 8M
sort_buffer_size = 8M

[myisamchk]
key_buffer = 8M
sort_buffer_size = 8M

[mysqlhotcopy]
interactive-timeout


CONTENTS of MEDIUM.cnf

# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# 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 /var/lib/mysql) 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 passed to all MySQL clients
[client]
#password   = your_password
port      = 3306
socket      = /var/run/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port      = 3306
socket      = /var/run/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

# 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_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> 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_PASSWORD='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 password in master-password 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 password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# 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 = 4M
#bdb_max_lock = 10000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#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 = 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


CONTENTS OF LARGE.cnf
# Example MySQL config file for large systems.
#
# This is for a large system with memory = 512M 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 /var/lib/mysql) 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 passed to all MySQL clients
[client]
#password   = your_password
port      = 3306
socket      = /var/run/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port      = 3306
socket      = /var/run/mysql/mysql.sock
skip-locking
key_buffer = 256M
max_allowed_packet = 1M
table_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# 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_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> 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_PASSWORD='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 password in master-password 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 password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# 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 = 64M
#bdb_max_lock = 100000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 256M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 64M
#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 = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

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

[mysqlhotcopy]
interactive-timeout


CONTENTS OF 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 /var/lib/mysql) 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 passed to all MySQL clients
[client]
#password   = your_password
port      = 3306
socket      = /var/run/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port      = 3306
socket      = /var/run/mysql/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_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> 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_PASSWORD='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 password in master-password 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 password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# 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 = /var/lib/mysql/
#innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
# 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









and still iam getting the error i posted above. . . i am thinking .. . do i need to change the socket in the .cnf file?
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 17, 2007, 01:12:36 am
tried the command :

mysqladmin version using ROOT and MYSQL user:

Quote


root:# /usr/bin/mysqladmin version
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/run/mysql/mysql.sock' exists!


Title: Re: using MYSQL in VL 5.8
Post by: bigpaws on December 17, 2007, 06:05:15 am
Did you do this?

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 /var/lib/mysql) or
 ~/.my.cnf to set user-specific options.

Bigpaws
Title: Re: using MYSQL in VL 5.8
Post by: Xeon on December 17, 2007, 06:23:10 am
High likely your service is not running
this can be easily fixed by running

./mysqld_safe --user=mysql &
inside the /bin folder of the mysql directory.
where you can make the user command a user you wish to use.
Since you created your database as root, u'd have to boot it as root however this is UNSAFE, so change the permissions on the database files.

also see
http://vectorlinux.com/wiki/doku.php?id=howtos:lamp
since i am writing a full lamp how to. The last 2 code boxes apply to you.
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 17, 2007, 11:14:19 pm
Did you do this?

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 /var/lib/mysql) or
 ~/.my.cnf to set user-specific options.

Bigpaws

hi Bigpaws, sorry for being ignorant. . but.. i have no "my.cnf" file in /etc only the small.cnf , medium.cnf, large and huge.cnf files. . .

Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 17, 2007, 11:16:30 pm
High likely your service is not running
this can be easily fixed by running

./mysqld_safe --user=mysql &
inside the /bin folder of the mysql directory.
where you can make the user command a user you wish to use.
Since you created your database as root, u'd have to boot it as root however this is UNSAFE, so change the permissions on the database files.

also see
http://vectorlinux.com/wiki/doku.php?id=howtos:lamp
since i am writing a full lamp how to. The last 2 code boxes apply to you.


hi Xeon. . hmm i have no

 /usr/local/mysql/scripts directory... :( is there something wrong?  PLUS also NO mysql dir in the /bin directory
Title: Re: using MYSQL in VL 5.8
Post by: newt on December 17, 2007, 11:30:05 pm
give: whereis mysql or whereis mysqld_safe a shot to see the install directory.
Title: Re: using MYSQL in VL 5.8
Post by: bigpaws on December 18, 2007, 03:28:22 am
Apparently something is being missed so lets start
from the beginning. You stated you installed the latest
package. Where did it come from? From there what did
you do to get MySQL running. What tutorials did you
use?

This way there is a starting point to solve the problem.

Bigpaws
Title: Re: using MYSQL in VL 5.8
Post by: Xeon on December 18, 2007, 08:03:46 am
bigpaws: from his huge quote i derived he installed the package, ran the mysql_install_db script and tries to change his root password on the mysql server, though he hasn't got his daemon running (missing mysql.sock is just not a spawned daemon.)

To be sure about it though:
icedtea do

pidof mysqld

as root in your console, and see if it gives any numbers back or not.
And as newtor suggested, locate the position of your mysqld_safe executable with his commands.

Xeon.
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 18, 2007, 01:24:11 pm
1.

$whereis mysql
mysql: /usr/bin/mysql /usr/lib/mysql /usr/include/mysql /usr/share/mysql /usr/man/man1/mysql.1.gz

$whereis mysqld_safe
mysqld_safe: /usr/bin/mysqld_safe /usr/man/man1/mysqld_safe.1.gz


2.

as root

pidof mysql -- blank result

pidof mysqld -- blank result
Title: Re: using MYSQL in VL 5.8
Post by: Xeon on December 18, 2007, 02:25:15 pm
as root write

mysqld_safe --user=mysql &

paste eventual error messages in here.
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 23, 2007, 10:52:04 pm
as root write

mysqld_safe --user=mysql &

paste eventual error messages in here.

after the command:


[1] 2964
root:# starting mysqld daemon with databases from /var/lib/mysql
STOPPING server from pid file /var/lib/mysql/vector.linux.net.pid
071224 09:42:37 mysqld ended

(cursor blinking)
Title: Re: using MYSQL in VL 5.8
Post by: newt on December 24, 2007, 08:19:35 am
IIRC, that's an ownership problem on the binaries.  Make sure they are owned by root (chown root:root /usr/bin/mysql*) and then try xeon's suggestion again.
Title: Re: using MYSQL in VL 5.8
Post by: icedtea on December 26, 2007, 11:16:14 pm
IIRC, that's an ownership problem on the binaries.  Make sure they are owned by root (chown root:root /usr/bin/mysql*) and then try xeon's suggestion again.

hi i did the exact instruction you said. . but still same output that i replied in xeon's suggestion. .