Eu compilei o PHP 5.4.5 do código-fonte e instalei o nginx 1.2.1 e o mysql 5.1.63-0ubuntu0.11.04.1 do apt-get no meu servidor Ubuntu 11.04 LTS.
Eu instalei o nginx usando isto:
add-apt-repository ppa:nginx/stable
echo "deb http://ppa.launchpad.net/nginx/stable/ubuntu lucid main" > /etc/apt/sources.list.d/nginx-stable-lucid.list
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C300EE8C
apt-get update
apt-get install nginx
Eu compilei o PHP 5.4.5 com as seguintes configurações:
./configure --enable-fpm --with-mcrypt --with-zlib --enable-mbstring --with-openssl --with-gd --with-jpeg-dir=/usr/lib --with-png-dir=/usr/lib --enable-gd-native-ttf --with-curl --enable-ftp --with-mysql=mysqlnd --with-mysqli=mysqlnd --with-pdo-mysql=mysqlnd --enable-zip
Eu instalei o mysql usando isto:
apt-get install mysql-server mysql-common mysql-client
O arquivo mysql my.cnf é armazenado, os arquivos sock ainda estão localizados em /var/run/mysqld/mysqld.sock . Nginx e PHP usam o soquete em /var/run/php/php.sock .
Atualmente, parece que não consigo instalar o PHP no Connect para o servidor MySQL, ele sempre diz que eu tenho esse erro Connect Error (2002) No such file or directory.
Este é o meu arquivo php.ini:
[date]
date.default_latitude = "40.725314"
date.default_longitude = "-73.498986"
date.timezone = "America/New_York"
[mysql]
mysql.allow_local_infile = "On"
mysql.allow_persistent = "On"
mysql.connect_timeout = 60
mysql.default_host = "localhost"
mysql.default_password = "password"
mysql.default_port = "3306"
mysql.default_socket = "unix:/var/run/mysqld/mysqld.sock"
mysql.default_user = "username"
mysql.max_links = "16"
mysql.max_persistent = "8"
mysql.trace_mode = "Off"
[pdo]
pdo_mysql.default_socket = "unix:/var/run/mysqld/mysqld.sock"
Este é o meu arquivo my.cnf:
#
# 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
#
#
# * IMPORTANT
# If you make changes to these settings and your system uses apparmor, you may
# also need to also adjust /etc/apparmor.d/usr.sbin.mysqld.
#
user = mysql
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
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 = 192K
thread_cache_size = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover = BACKUP
#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.
# As of 5.1 you can enable the log at runtime!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
log_error = /var/log/mysql/error.log
# 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
#
# * 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!
#
# * 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
#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
Posso confirmar que o arquivo /var/run/mysqld/mysqld.sock está lá e tem exatamente a mesma configuração que o arquivo /var/run/php/php.sock que está em seu diretório-irmão, por isso não tenho idéia do motivo pelo qual um não pode se conectar ao outro. Qualquer idéia seria muito apreciada.
Eu tentei mysql.default_socket e pdo_mysql.default_socket como unix:/var/run/mysqld/mysqld.sock e /var/run/mysqld/mysqld.sock .
Como o www-data não pode conectar-se ao mysql com o cliente mysql-cli, suspeito que deve haver um problema de permissão.
Você poderia:
Verifique se o root pode se conectar ao mysql
# mysql -u root -p -S /var/run/mysqld/mysql.sock
Verifique onde o www-data tem um problema de permissão
# su - www-data -s /bin/bash
Então:
$ ls -l /var/run/mysqld/mysql.sock
$ ls -l /var/run/mysqld