phpBB : Critical Error Could not connect to the database

raf64flo · Le 13/04/2008, à 02:41

Bonsoir à tous.

J'ai un ami qui avait un forum, mais depuis quelques mois, ce forum est down :

phpBB : Critical Error 

Could not connect to the database

C'est toutes les informations qui sont renvoyées. Or, j'aimerais relancer le forum et tant qu'à faire mettre à jour les composants (PHPmyAdmin, MySQL, phpBB, etc...). Mon soucis, c'est que je n'y connais rien dans ce domaine et que personne d'autre ne peut s'en charger. C'est pourquoi, je viens à vous.

J'ai installé xampp en local pour essayer d'arranger le soucis, mais je ne vois pas trop quoi faire précisément. Si vous pouviez me conseiller, ce serait avec plaisir. Voici quelques informations qui pourraient être utiles, si il en manque, demandez quoi et précisez où trouver l'information svp.

Merci d'avance.

Online
Version du serveur: 3.23.47-log
Version du protocole: 10
Serveur: #######.sql-pro.online.net via TCP/IP
Utilisateur: #######@212.#.#.#
phpMyAdmin - 2.10.0.2
Version du client MySQL: 5.0.32
Extensions PHP utilisées: mysql
Moteurs de stockage Moteur de stockage
MyISAM
MERGE
HEAP
MEMORY
BDB
Gemini
InnoDB
ISAM

Voici le contenu de mon fichier config.php :

<?php


// phpBB 2.x auto-generated config file
// Do not change anything in this file!

$dbms = 'mysql';

$dbhost = 'sql.gentilhomme.org';
$dbname = 'gentilhomme.org';
$dbuser = 'gentilhomme.org';
$dbpasswd = '#####mon_mot_de_passe#####';

$table_prefix = 'vod_';

define('PHPBB_INSTALLED', true);

?>

Là, on a les variables et réglages du serveur :

Variable	Valeur 
back log	50
basedir	/usr/
bdb cache size	8 388 600
bdb log buffer size	2 097 152
bdb home	/var/lib/mysql/
bdb max lock	10 000
bdb logdir	
bdb shared data	OFF
bdb tmpdir	/tmp/
bdb version	Sleepycat Software: Berkeley DB 3.2.9a: (December 27, 2001)
binlog cache size	32 768
character set	latin1
character sets	latin1 big5 cp1251 cp1257 croat czech danish dec8 dos estonia euc_kr gb2312 gbk german1 greek hebrew hp8 hungarian koi8_ru koi8_ukr latin2 latin5 swe7 usa7 win1250 win1251 win1251ukr ujis sjis tis620
concurrent insert	ON
connect timeout	5
datadir	/var/lib/mysql/
delay key write	ON
delayed insert limit	50
delayed insert timeout	30
delayed queue size	100
flush	OFF
flush time	0
have bdb	YES
have gemini	NO
have innodb	DISABLED
have isam	YES
have raid	YES
have openssl	NO
init file	
innodb additional mem pool size	1 048 576
innodb buffer pool size	8 388 608
innodb data file path	
innodb data home dir	
innodb file io threads	4
innodb force recovery	0
innodb thread concurrency	8
innodb flush log at trx commit	OFF
innodb fast shutdown	OFF
innodb flush method	
innodb lock wait timeout	50
innodb log arch dir	
innodb log archive	OFF
innodb log buffer size	1 048 576
innodb log file size	5 242 880
innodb log files in group	2
innodb log group home dir	
innodb mirrored log groups	1
interactive timeout	120
join buffer size	131 072
key buffer size	268 431 360
language	/usr/share/mysql/english/
large files support	ON
locked in memory	OFF
log	OFF
log update	OFF
log bin	OFF
log slave updates	OFF
log long queries	ON
long query time	1
low priority updates	OFF
lower case table names	0
max allowed packet	1 047 552
max binlog cache size	4 294 967 295
max binlog size	1 073 741 824
max connections	512
max connect errors	1 000 000
max delayed threads	5
max heap table size	15 360
max join size	300 000
max sort length	1 024
max user connections	10
max tmp tables	32
max write lock count	4 294 967 295
myisam max extra sort file size	256
myisam max sort file size	2 047
myisam recover options	1
myisam sort buffer size	8 388 608
net buffer length	16 384
net read timeout	60
net retry count	10
net write timeout	30
open files limit	0
pid file	/var/run/mysqld/mysqld.pid
port	3 306
protocol version	10
record buffer	4 190 208
record rnd buffer	4 190 208
query buffer size	67 104 768
safe show database	OFF
server id	0
slave net timeout	3 600
skip locking	ON
skip networking	OFF
skip show database	ON
slow launch time	2
socket	/var/run/mysqld/mysqld.sock
sort buffer	2 097 144
sql mode	0
table cache	4 096
table type	MYISAM
thread cache size	1 024
thread stack	262 144
transaction isolation	READ-COMMITTED
timezone	CEST
tmp table size	4 194 304
tmpdir	/tmp/
version	3.23.47-log
wait timeout	120

Mon fichier my.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 /opt/lampp/var/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		= /opt/lampp/var/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port		= 3306
socket		= /opt/lampp/var/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 deactivated by default since XAMPP 1.4.11
#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

# Comment the following if you are using InnoDB tables
skip-innodb
innodb_data_home_dir = /opt/lampp/var/mysql/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /opt/lampp/var/mysql/
innodb_log_arch_dir = /opt/lampp/var/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

raf64flo · Le 15/04/2008, à 08:31

Quelqu'un a-t-il une idée ?:/

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 13/04/2008, à 02:41

phpBB : Critical Error Could not connect to the database

#2 Le 15/04/2008, à 08:31

Re : phpBB : Critical Error Could not connect to the database

Pied de page des forums