Apache,php,mysql,phpmyadmin
Résolu/Fermé
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
-
13 mai 2008 à 14:00
PhP Messages postés 1770 Date d'inscription lundi 11 décembre 2000 Statut Membre Dernière intervention 23 décembre 2009 - 26 mai 2008 à 16:10
PhP Messages postés 1770 Date d'inscription lundi 11 décembre 2000 Statut Membre Dernière intervention 23 décembre 2009 - 26 mai 2008 à 16:10
A voir également:
- Apache,php,mysql,phpmyadmin
- Apache open office gratuit - Télécharger - Suite bureautique
- Easy php - Télécharger - Divers Web & Internet
- Mysql community server - Télécharger - Bases de données
- Localhost/phpmyadmin ✓ - Forum PHP
- Clé étrangère phpmyadmin ✓ - Forum MySQL
54 réponses
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
19 mai 2008 à 18:04
19 mai 2008 à 18:04
Bjr
ben il te dit que ton username + mot de passe est invalide
Lorsque tu as installé MySQL est-ce que tu as touché à Modify Security Settings ?
Espèrons que non (décocher cette case était préférable ...), sinon j'espère que tu te souviens du mot de passe que tu as donné à root
ben il te dit que ton username + mot de passe est invalide
Lorsque tu as installé MySQL est-ce que tu as touché à Modify Security Settings ?
Espèrons que non (décocher cette case était préférable ...), sinon j'espère que tu te souviens du mot de passe que tu as donné à root
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
19 mai 2008 à 20:56
19 mai 2008 à 20:56
Je comprends pas bien ... Tu as réinstalllé MySQL ou bien était-il déjà installé ?
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
19 mai 2008 à 21:38
19 mai 2008 à 21:38
j'ai tout réinstaller avec les paramètre de l'ancien webmaster
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
19 mai 2008 à 21:52
19 mai 2008 à 21:52
Tu es sûr de tes identifiants ?
Lance un fenêtre de cde puis place toi dans le répertoire où tu as installé MySQL par ex
Dans le répertoire
Ca se connecte ou pas ?
Essai avec root et aucun mot de passe
Autrement ce lien devrait t'intéresser : http://www.ruas-blog.com/index.php/2005/12/15/30-reinitialiser-le-mot-de-passe-root-mysql
Lance un fenêtre de cde puis place toi dans le répertoire où tu as installé MySQL par ex
C:\Program Files\mysql\bin
Dans le répertoire
./binlance mysql --user=xxxxx --password=yyyy
Ca se connecte ou pas ?
Essai avec root et aucun mot de passe
Autrement ce lien devrait t'intéresser : http://www.ruas-blog.com/index.php/2005/12/15/30-reinitialiser-le-mot-de-passe-root-mysql
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 08:06
20 mai 2008 à 08:06
le lien : http://www.ruas-blog.com/ ne fonctionne pas et quand je lance les commande il me fait la meme erreur
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 08:35
20 mai 2008 à 08:35
Good morning,
Bizarre chez moi le lien fonctionne
Si tu es sous Windows voici ce que le lien indique de faire :
Sous Windows :
1. Arrêter le service MySQL dans le gestionnaire de services Windows. Si MySQL ne tourne pas en tant que service, arrêter le processus dans le gestionnaire de tâches.
2. Ouvrir une console MsDOS.
3. En supposant que MySQL est insallé dans c:\mysql, lancer la commande suivante :
C:\mysql\bin\mysqld-nt --skip-grant-tables
4. Taper les commandes suivantes :
C:\mysql\bin\mysqladmin -u root
flush-privileges password "nouveau_mot_de_passe"
C:\mysql\bin\mysqladmin -u root -p shutdown
5. Stopper le service MySQL puis le relancer comme d'habitude soit par le service, soit par la commande habituelle.
Ensuite tu dois pouvoir te connecter avec root et le nouveau mot de passe
Bizarre chez moi le lien fonctionne
Si tu es sous Windows voici ce que le lien indique de faire :
Sous Windows :
1. Arrêter le service MySQL dans le gestionnaire de services Windows. Si MySQL ne tourne pas en tant que service, arrêter le processus dans le gestionnaire de tâches.
2. Ouvrir une console MsDOS.
3. En supposant que MySQL est insallé dans c:\mysql, lancer la commande suivante :
C:\mysql\bin\mysqld-nt --skip-grant-tables
4. Taper les commandes suivantes :
C:\mysql\bin\mysqladmin -u root
flush-privileges password "nouveau_mot_de_passe"
C:\mysql\bin\mysqladmin -u root -p shutdown
5. Stopper le service MySQL puis le relancer comme d'habitude soit par le service, soit par la commande habituelle.
Ensuite tu dois pouvoir te connecter avec root et le nouveau mot de passe
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 08:43
20 mai 2008 à 08:43
j'ai trouvé une partie de réponce pour réinitialiser le mot de passe sur ce topic de ccm:
mysql help
mais la solution ne marche pas au niveau du flush-privileges
---
enfin mon macbook sous léopard
mysql help
mais la solution ne marche pas au niveau du flush-privileges
---
enfin mon macbook sous léopard
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 10:02
20 mai 2008 à 10:02
T'Oh ! Décidemment ! :-(
Ben tu sauvegardes tes bases MySQL (elles se trouvent sous ...\MySQL\data )
Tu déinstalles MySQL
Tu réinstalles MySQL sans attribuer de mot de passe à root
Tu recopies tes bases de données sous ...\MySQL\data sauf la base mysql elle-même bien sûr
PhP
Il y a 10 types de personnes dans le monde : ceux qui comprennent le binaire et les autres ...
Ben tu sauvegardes tes bases MySQL (elles se trouvent sous ...\MySQL\data )
Tu déinstalles MySQL
Tu réinstalles MySQL sans attribuer de mot de passe à root
Tu recopies tes bases de données sous ...\MySQL\data sauf la base mysql elle-même bien sûr
PhP
Il y a 10 types de personnes dans le monde : ceux qui comprennent le binaire et les autres ...
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 10:33
20 mai 2008 à 10:33
maintenant pjpmyadmin me dit que le serveur ne répond pas pourtant j'ai réinstaller relancer apache et quand je lance mysqladmin en ligne de command il plante aussi
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 10:42
20 mai 2008 à 10:42
Nomalement lorsque tu résinstalles MySQL ton serveur ne contient que la base mysql sous ...\data tu devrais pouvoir t'y connecter manuellement même sans Apache même sans PHP par la ligne de cde.
Tu es sûr que tu n'as pas un autre service MySQL qui tourne ou un autre process ?
Au pire reboot et reteste en ligne de cde
Tu es sûr que tu n'as pas un autre service MySQL qui tourne ou un autre process ?
Au pire reboot et reteste en ligne de cde
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 10:57
20 mai 2008 à 10:57
quand je relance après reboot il m'affiche:
mysqladmin: connect to server at 'localhost' falied
error: 'Can't connect to MySQL server on 'localhost' <10061>'
check that mysqld is running on localhost and that the port is 3306.
You can check this by doing telnet localhost 3306'
mysqladmin: connect to server at 'localhost' falied
error: 'Can't connect to MySQL server on 'localhost' <10061>'
check that mysqld is running on localhost and that the port is 3306.
You can check this by doing telnet localhost 3306'
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 11:31
20 mai 2008 à 11:31
vérifie que le service mysql est bien démarré
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 11:33
20 mai 2008 à 11:33
il l'est c'est ça le bug dans l'histoire
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 11:37
20 mai 2008 à 11:37
vérifie qu'il n'y a pas un autre process mysqld qui tourne alt+ctrl+suppr si oui supprime le
vérifie si un fichier my.ini ne traine pas sous c:\windows si oui regarde sa config ou poste le
recherche tous les my.ini sur ton disque
vérifie si un fichier my.ini ne traine pas sous c:\windows si oui regarde sa config ou poste le
recherche tous les my.ini sur ton disque
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 11:44
20 mai 2008 à 11:44
voila le my.ini mais il ce trouve dans le dossier de MySQL:
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]
pipe
socket=mysql
[mysql]
default-character-set=latin1
# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]
skip-networking
enable-named-pipe
# The Pipe the MySQL Server will use
socket=mysql
#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 4.1/"
#Path to the database root
datadir="C:/Program Files/MySQL/MySQL Server 4.1/Data/"
# The default character set that will be used when a new schema or table is
# created and no character set is defined
default-character-set=latin1
# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100
# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256
# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=26M
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=51M
# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=40M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K
# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb
# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M
# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1
# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=76M
# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=38M
# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]
pipe
socket=mysql
[mysql]
default-character-set=latin1
# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]
skip-networking
enable-named-pipe
# The Pipe the MySQL Server will use
socket=mysql
#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 4.1/"
#Path to the database root
datadir="C:/Program Files/MySQL/MySQL Server 4.1/Data/"
# The default character set that will be used when a new schema or table is
# created and no character set is defined
default-character-set=latin1
# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100
# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256
# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=26M
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=51M
# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=40M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K
# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb
# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M
# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1
# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=76M
# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=38M
# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 11:53
20 mai 2008 à 11:53
Bizarre ça skip-networking ?
A tout hasard fait un backup de my.ini puis
Remplace
[mysqld]
skip-networking
par
[mysqld]
port= 3306
bind-address = 127.0.0.1
#skip-networking
Redémarre le service mysql
et test C:/Program Files/MySQL/MySQL Server 4.1/bin/mysql --user=root
A tout hasard fait un backup de my.ini puis
Remplace
[mysqld]
skip-networking
par
[mysqld]
port= 3306
bind-address = 127.0.0.1
#skip-networking
Redémarre le service mysql
et test C:/Program Files/MySQL/MySQL Server 4.1/bin/mysql --user=root
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 12:01
20 mai 2008 à 12:01
j'optien une erreur 2003 quand je lance mysql par ligne de commande
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
>
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
20 mai 2008 à 13:37
20 mai 2008 à 13:37
ça peut paraitre lourd de ma part mais je ne voie pas comment faire
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 15:41
20 mai 2008 à 15:41
Bon alors j'ai installé une version MySQL 4.1 et voici le my.ini que j'obtiens
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server 4.1). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQL41 --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQL41
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]
port=3306
# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
#Path to installation directory. All paths are usually resolved relative to this.
basedir=C:/Program Files/MySQL/MySQL Server 4.1/
#Path to the database root
datadir=C:/Program Files/MySQL/MySQL Server 4.1/Data/
# The default character set that will be used when a new schema or table is
# created and no character set is defined
default-character-set=latin1
# The default storage engine that will be used when create new tables when
default-storage-engine=MYISAM
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100
# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256
# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=9M
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache=8
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=18M
# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=21M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K
# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
skip-innodb
# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M
# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1
# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=8M
# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=10M
# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8
Sans définir de mot de passe pour root ben ça fonctionne du premier coup
Dans ta section client arrange toi pour avoir
[client]
port=3306
et mysql
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
vire tout ce qui concerne les pipes & socket
Et relance le service
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server 4.1). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQL41 --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQL41
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]
port=3306
# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
#Path to installation directory. All paths are usually resolved relative to this.
basedir=C:/Program Files/MySQL/MySQL Server 4.1/
#Path to the database root
datadir=C:/Program Files/MySQL/MySQL Server 4.1/Data/
# The default character set that will be used when a new schema or table is
# created and no character set is defined
default-character-set=latin1
# The default storage engine that will be used when create new tables when
default-storage-engine=MYISAM
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100
# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256
# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=9M
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache=8
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=18M
# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=21M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K
# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
skip-innodb
# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M
# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1
# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=8M
# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=10M
# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8
Sans définir de mot de passe pour root ben ça fonctionne du premier coup
Dans ta section client arrange toi pour avoir
[client]
port=3306
et mysql
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
vire tout ce qui concerne les pipes & socket
Et relance le service
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 15:54
20 mai 2008 à 15:54
toujour l'erreur de serveur sans réponce mais je verais demain matin si en relancant ça marche.pour aujourd'hui j'ai fini ma journée.mais j'ai quand mm vite essaier et ça plante toujour encore
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 16:34
20 mai 2008 à 16:34
T'es maudit ! ;-)
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
20 mai 2008 à 18:16
20 mai 2008 à 18:16
surement
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
20 mai 2008 à 18:25
20 mai 2008 à 18:25
Dernier truc auquel je pense après j'ai plus trop d'idée
dans les services sur le service MySQL vérifie dans les propriétés que le chemin du service lancé ainsi que les paramètres vers le fichier ini sont correctes
Chez moi ca donne : "C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini" MySQL--
PhP
Il y a 10 types de personnes dans le monde : ceux qui comprennent le binaire et les autres ...
dans les services sur le service MySQL vérifie dans les propriétés que le chemin du service lancé ainsi que les paramètres vers le fichier ini sont correctes
Chez moi ca donne : "C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini" MySQL--
PhP
Il y a 10 types de personnes dans le monde : ceux qui comprennent le binaire et les autres ...
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
21 mai 2008 à 08:08
21 mai 2008 à 08:08
je vien de vérifier le chemin et c'est celui ci:
"C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini" MySQL41
"C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini" MySQL41
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
>
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
21 mai 2008 à 09:24
21 mai 2008 à 09:24
j'ai oublier de preciser aussi PhpMyAdmin m'indique en plus de l'erreur 1045 ou 2003 pour mysql ,le problème suivant:PHP ne peut charger l'extension mcrypt,
veuillez vérifier votre configuration de PHP; et pourtant il est bien dans mes extension et décompenté dans le php.ini
veuillez vérifier votre configuration de PHP; et pourtant il est bien dans mes extension et décompenté dans le php.ini
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
>
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
21 mai 2008 à 10:07
21 mai 2008 à 10:07
J'ai l'impression que c'est vraiment qu'une histoire de mot de passe si rien d'autre ne fonctionne et j'aurais voulus savoir si c'était unique ment dans config.inc.php que l'on trouvais le mot de passe de Mysql ou PhpMyAdmin pour le changer a la manuellement
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
21 mai 2008 à 10:26
21 mai 2008 à 10:26
Bjr
Non en fait le mot de passe de MySQL se trouve crypté dans la base mysql table user
C'est pourquoi normalement tu devrais au moins pouvoir te connecter à MySQL depuis la ligne de cde même si ton serveur Apache est éteint du moment que tu précises le bon user et le bon password
Donc dans un premier temps ne teste pas PHPMyAdmin mais uniquement MySQL en ligne de cde
Non en fait le mot de passe de MySQL se trouve crypté dans la base mysql table user
C'est pourquoi normalement tu devrais au moins pouvoir te connecter à MySQL depuis la ligne de cde même si ton serveur Apache est éteint du moment que tu précises le bon user et le bon password
Donc dans un premier temps ne teste pas PHPMyAdmin mais uniquement MySQL en ligne de cde
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
21 mai 2008 à 10:34
21 mai 2008 à 10:34
au niveau des erreur se sont les même et je ne c pas quel est la table user dans mysql j'ai trois user un en .frm,un autre en .MYD et un troisieme en .MYI
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
>
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
21 mai 2008 à 13:22
21 mai 2008 à 13:22
trouvé une partie de ma reponse j'ai tester de me connecter a root avec c:\program files\mysql\mysql server 4.1\bin>mysql -u root -p et il ce connect au root, mais toujour une erreir 1045 sous phpmyadmin qui temps qu'il ne fonctionne pas me permet pas de passer au plus important c'est a dire SPIP
---
enfin mon macbook sous léopard
---
enfin mon macbook sous léopard
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
>
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
21 mai 2008 à 15:03
21 mai 2008 à 15:03
maintenant la manipulation que j'ai donner précedement ne marche meme plus : `(
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
21 mai 2008 à 17:52
21 mai 2008 à 17:52
Ca fonctionne la connexion a MySQL ou pas au final ?
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
22 mai 2008 à 08:10
22 mai 2008 à 08:10
je vien de retester ce matin et ça marche toujours pas et les erreur jongle entre la 1045 et la 2003 quand je lance mysql en ligne de commande
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
22 mai 2008 à 10:16
22 mai 2008 à 10:16
Bjr
Récalcitrant ton pb dit donc ! j'ai jamais eu autant de soucis avec MySQL
lorsque tu tentes : mysql -u root
tu as l'erreur
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Y'a quoi dans ton fichier mysql.err ?
Le pare feu de Windows est-il activé ?
Récalcitrant ton pb dit donc ! j'ai jamais eu autant de soucis avec MySQL
lorsque tu tentes : mysql -u root
tu as l'erreur
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Y'a quoi dans ton fichier mysql.err ?
Le pare feu de Windows est-il activé ?
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
22 mai 2008 à 10:21
22 mai 2008 à 10:21
non, mais je pense qu'il y a un par-feu quel que par sur le reseaux du lycée qui me bloque peut etre
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
>
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
22 mai 2008 à 11:18
22 mai 2008 à 11:18
je vien de relancer un mysql -u root -pet joptien bien une erreur 1045 ,j'ai tester en plus pour voir si il m'affichais la meme erreur le phpmyadmin mais lui m'affiche une erreur 1251
PhP
Messages postés
1770
Date d'inscription
lundi 11 décembre 2000
Statut
Membre
Dernière intervention
23 décembre 2009
606
22 mai 2008 à 11:52
22 mai 2008 à 11:52
Inutile de tester avec PhpMyAdmin tant que la ligne de cde de MySQL ne fonctionne pas ca ne marchera jamais
Pour le firewall du réseau il ne devrait pas t'empêcher de te connecter localement.
J'avoue que je ne comprends pas ...
Pour le firewall du réseau il ne devrait pas t'empêcher de te connecter localement.
J'avoue que je ne comprends pas ...
zangetsu68
Messages postés
509
Date d'inscription
lundi 21 mai 2007
Statut
Membre
Dernière intervention
5 juin 2010
17
22 mai 2008 à 12:02
22 mai 2008 à 12:02
j'utilise un compte réseaux et pas local pour ma machine
19 mai 2008 à 19:30