Mysql Rennt aber Trotzdem socket fehler.
Posted: 2006-03-11 10:46
Hallo Leute.
Ich habe folgendes Problem.
Der Mysql Server rennt Problemlos, aber gelegentlich gibt es beim aufrufen der Seite socket fehler.
Das Problem ist auch sie Serverload teilweise auf beiden cpus auf ueber 99% geht. Ich bin langsam ratlos woran es liegen kann.
hier meine my.cnf
Ich waere fuer jeden Tipp dankbar.
Gruss Martin
Ich habe folgendes Problem.
Der Mysql Server rennt Problemlos, aber gelegentlich gibt es beim aufrufen der Seite socket fehler.
Code: Select all
Warning: mysql_connect() [function.mysql-connect]: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (11) in /var/www/conneryweb/public_html/admin/config/class_db.inc on line 23
Database error in : Handle == false, connect failed
mysql error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (11)
mysql error number: 2002
Date: 11.03.2006 @ 10:20
Script: /adbanner.php?typ=1&sid=DEE936E8FBC73F56296EF9699666D24C
Referer: http://www.conneryweb.de/seite_home.php?betteln=
Code: Select all
p - 10:41:41 up 9:06, 1 user, load average: 23.86, 24.83, 22.11
Tasks: 119 total, 2 running, 117 sleeping, 0 stopped, 0 zombie
Cpu(s):sks: 127 total, 3 running, 124 sleeping, 0 stopped, 0 zombie
Cpu0 : 93.9% us, 6.1% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
Cpu1 : 87.8% us, 10.2% sy, 0.0% ni, 0.0% id, 0.0% wa, 2.0% hi, 0.0% si
Mem: 4052832k total, 1062808k used, 2990024k free, 6268k buffers
Swap: 1000440k total, 116340k used, 884100k free, 333144k cachedCode: Select all
# /etc/mysql/my.cnf: The global mysql configuration file.
# $Header: /var/cvsroot/gentoo-x86/dev-db/mysql/files/my.cnf-4.0.24-r1,v 1.1 2005/03/13 05:54:00 robbat2 Exp $
#
# This file can be simultaneously placed in three places:
# 1. /etc/mysql/my.cnf to set global options.
# 2. /var/lib/mysql/my.cnf to set server-specific options.
# 3. ~/.my.cnf to set user-specific options.
#
# One can use all long options that the program supports.
# Run the program with --help to get a list of them.
#
# The following values assume you have at least 64M RAM!
[client]
#password = my_password
port = 3306
socket = /var/run/mysqld/mysqld.sock
[safe_mysqld]
err-log = /var/log/mysql/mysql.err
[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
log-error = /var/log/mysql/mysqld.err
# If set, mysql logs all queries(general query log). This will be deprecated in
# 5.0. This logs all queries, even error queries and is slow.
# log = /var/log/mysql/mysql.log
#
# If you really need logging, use rather binary logging. Especially when doing
# replication. Read
# file:/usr/share/doc/mysql-*/manual.html.gz#Replication
# You can use PURGE MASTER LOGS TO '$hostname-bin.010' to get rid of old logs
# from $hostname-bin.01 up to $hostname-bin.09 while the slave server is
# running.
# Before doing that, check which logfile slave curently uses by running
# mysql> SHOW SLAVE STATUS
# To list logfiles on master do:
# mysql> SHOW MASTER LOGS
# Then use PURGE for those not needed anymore only! Never remove the files
# manually!
#
# Also consult RESET MASTER and RESET SLAVE commands before doing any changes
# mysql> RESET MASTER - Deletes all binary logs listed in the index
# file, resetting the binlog index file to be empty.
# mysql> RESET SLAVE - Makes the slave forget its replication position in
# the master logs.
# mysql> SET SQL_LOG_BIN=0 - this turns off logging (execute on MASTER only)
# mysql> SET SQL_LOG_BIN=1 - this turns on logging (execute on MASTER only)
#
# log-bin
# set-variable = binlog-do-db=non_existant
# set-variable = binlog-ignore-db=database_name
#
# server-id has to unique for each master or slave in your network,
# lets use last number from IP address
server-id = 207
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-locking
set-variable = key_buffer=350M
set-variable = max_allowed_packet=2M
#set-variable = thread_stack=128K
# keep secure by default!
bind-address = 127.0.0.1
port = 3306
# this can make it even more secure:
#skip-networking
#
# The following is the InnoDB configuration
# if you wish to disable innodb instead
# uncomment just the next line
#skip-innodb
#
# the rest of the innodb config follows:
# don't eat too much memory, we're trying to be safe on 64Mb boxes.
# you might want to bump this up a bit on boxes with more RAM
set-variable = innodb_buffer_pool_size=32M
# this is the default, increase if you have lots of tables
set-variable = innodb_additional_mem_pool_size=1M
#
# i'd like to use /var/lib/mysql/innodb, but that is seen as a database :-(
# and upstream wants things to be under /var/lib/mysql/, so that's the route
# we have to take for the moment
innodb_data_home_dir = /var/lib/mysql/
innodb_log_arch_dir = /var/lib/mysql/
innodb_log_group_home_dir = /var/lib/mysql/
# you may wish to change this size to be more suitable for your system
# the max is there to avoid run-away growth on your machine
innodb_data_file_path = ibdata1:10M:autoextend:max:128M
# we keep this at around 25% of of innodb_buffer_pool_size
# sensible values range from 1MB to (1/innodb_log_files_in_group*innodb_buffer_pool_size)
set-variable = innodb_log_file_size=8M
# this is the default, increase if you have very large transactions.
set-variable = innodb_log_buffer_size=1M
# this is the default, and won't hurt you.
# you shouldn't need to tweak it.
set-variable = innodb_log_files_in_group=2
# see the innodb config docs, the other options are not always safe
innodb_flush_log_at_trx_commit=1
[mysqldump]
quick
set-variable = max_allowed_packet=2M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
[isamchk]
#set-variable = key_buffer=128M
set-variable = table_cache=4068
set-variable = global_max_connections=800
set-variable = sort_buffer=15M
set-variable = wait_timeout=10
set-variable = interactive_timeout=100
set-variable = query_cache_size=64M
set-variable = query_cache_limit=512K
set-variable = query_cache_type=1
Ich waere fuer jeden Tipp dankbar.
Gruss Martin