MySQL Trouble need help
Antony Kipingor
kipingor at gmail.com
Thu Mar 27 07:02:45 GMT 2008
I thought that might be the problem Andrew but, I dont see anythinh wrong
with the my.cnf.....
take a look:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently
parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 128K
thread_cache_size = 8
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for
replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * BerkeleyDB
#
# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa
100MB.
#skip-innodb
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
[isamchk]
key_buffer = 16M
#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the NDB Data Nodes (ndbd processes)
# not from the NDB Management Nodes (ndb_mgmd processes).
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1
#
# * IMPORTANT: Additional settings that can override those from this file!
#
!includedir /etc/mysql/conf.d/
On Wed, Mar 26, 2008 at 7:58 PM, Andrew Mathenge <mathenge at gmail.com> wrote:
> This email is from a ubuntu-ke subscriber to other subscribers inluding
> you:)
> Your client is looking for the MySQL socket in /var/run/mysqld
>
> Check your my.cnf. In my installation, this file is in /etc/mysql
>
> Inside this file is a line that reads:
>
> socket = /var/run/mysqld/mysqld.sock
>
> Based on your installation this line may say something else.
>
> Something else you can do is search for the file my.cnf. You can
> use the following command to search for the file:
>
> find / -name "my.cnf" -print
>
> Let me know how many files are actually found. Depending (again)
> on your installation, your MySQL may be using a different my.cnf
> which is using a mysqld.sock that's in a different location.
>
> Hope that this makes sense.
>
> Andrew.
>
> On Wed, Mar 26, 2008 at 7:37 AM, Antony Kipingor <kipingor at gmail.com>
> wrote:
>
> > This email is from a ubuntu-ke subscriber to other subscribers inluding
> > you:)
> > Hi all,
> >
> > I hope you have been well, I resently attempted to upgrade Mysql server.
> > The
> > server is now giving me issues, I believe the root of the problem is the
> > my.cnf is a different version than the server itself.
> >
> > When I attempt to login i.e.
> > #mysql -u root -p
> > etc
> > I receive the following error message:
> > ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> > '/var/run/mysqld/mysqld.sock' (2)
> >
> > Can anyone help me
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
> >
> https://lists.ubuntu.com/archives/ubuntu-ke/attachments/20080326/0f43de26/attachment.htm
> > --
> > Ubuntu-ke mailing list
> > Ubuntu-ke at lists.ubuntu.com
> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-ke
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://lists.ubuntu.com/archives/ubuntu-ke/attachments/20080326/78c88692/attachment.htm
> --
> Ubuntu-ke mailing list
> Ubuntu-ke at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-ke
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-ke/attachments/20080327/ba57fa30/attachment.htm
More information about the Ubuntu-ke
mailing list