CONNEXION
  • RetourJeux
    • Sorties
    • Hit Parade
    • Les + populaires
    • Les + attendus
    • Soluces
    • Tous les Jeux
    • Gaming
  • RetourActu Gaming
    • News
    • Astuces
    • Tests
    • Previews
    • Toute l'actu gaming
  • RetourBons plans
    • Bons plans
    • Bons plans Smartphone
    • Bons plans Hardware
    • Bons plans Image et Son
    • Bons plans Amazon
    • Bons plans Cdiscount
    • Bons plans Decathlon
    • Bons plans Fnac
    • Tous les Bons plans
  • RetourJVTech
    • Actus High-Tech
    • Intelligence Artificielle
    • Smartphones
    • Mobilité urbaine
    • Hardware
    • Image et son
    • Tutoriels
    • Tests produits High-Tech
    • Guides d'achat High-Tech
    • JVTech
  • RetourCulture
    • Actus Culture
    • Culture
  • RetourVidéos
    • A la une
    • Gaming Live
    • Vidéos Tests
    • Vidéos Previews
    • Gameplay
    • Trailers
    • Chroniques
    • Replay Web TV
    • Toutes les vidéos
  • RetourForums
    • Hardware PC
    • PS5
    • Switch 2
    • Xbox Series
    • Switch
    • Pokemon pocket
    • FC 25 Ultimate Team
    • League of Legends
    • Tous les Forums
  • PC
  • PS5
  • Xbox Series
  • Switch 2
  • PS4
  • One
  • Switch
  • iOS
  • Android
  • MMO
  • RPG
  • FPS
En ce moment Genshin Impact Valhalla Breath of the wild Animal Crossing GTA 5 Red dead 2
Liste des sujets

Problème mysql / phpmyadmin

Wolveryne2
Wolveryne2
Niveau 7
04 juin 2011 à 03:19:58

:salut:

Donc voilà le truc, hier j'ai installé Mysql, Phpmyadmin, php5 et tout ce qui va avec.
Je commence mon site (en local) et tout marche.
Aujourd'hui impossible d'y accéder. :mort:

Impossible aussi d'accéder à phpmyadmin :

  1. 2002 Connexion au serveur MySQL non permise

La connexion au controluser tel que défini dans votre configuration a échoué.

Et pareil pour Mysql administrator :
Could not connect to host 'localhost'.
MySQL Error Nr. 2002
Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

:svp: Quelqu'un a déjà eu ce problème ? Je n'ai pourtant touché à rien d'autre depuis hier.

godrik
godrik
Niveau 30
04 juin 2011 à 04:57:32

est ce que les daemons sont correctement demarres ?

Wolveryne2
Wolveryne2
Niveau 7
04 juin 2011 à 11:11:52

Je sais pas si je me trompe ou pas mais en faisant "service mysql start" j'ai :
start: Job is already running: mysql

Donc logiquement il est en route, et pourtant rien ne marche.

aodren
aodren
Niveau 10
05 juin 2011 à 06:55:38

essai "service mysql reload" ou restart

après as-tu touché un réglage ?

Wolveryne2
Wolveryne2
Niveau 7
05 juin 2011 à 15:07:31

service mysql reload
reload: Inactif

service mysql restart
mysql start/running

Mais en essayant de me connecter à phpmyadmin ou à mysql ça ne marche toujours pas et j'ai toujours les memes erreurs.

Wolveryne2
Wolveryne2
Niveau 7
06 juin 2011 à 13:31:25

:svp:

deepblue
deepblue
Niveau 16
06 juin 2011 à 16:24:01

Minute papillon...

Relances mysql et fait un

  1. tail -n 20 /var/log/syslog

et donne le résultat

Wolveryne2
Wolveryne2
Niveau 7
06 juin 2011 à 16:59:57

Voilà ce que j'ai :

Jun 6 16:52:46 WOLVY kernel: [14739.831092] type=1400 audit(1307371966.011:505): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=18709 comm="apparmor_parser"
Jun 6 16:52:46 WOLVY init: mysql main process (18713) terminated with status 1
Jun 6 16:52:46 WOLVY init: mysql main process ended, respawning
Jun 6 16:53:16 WOLVY init: mysql post-start process (18714) terminated with status 1
Jun 6 16:53:16 WOLVY kernel: [14770.082625] type=1400 audit(1307371996.263:506): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=18798 comm="apparmor_parser"
Jun 6 16:53:16 WOLVY init: mysql main process (18802) terminated with status 1
Jun 6 16:53:16 WOLVY init: mysql main process ended, respawning
Jun 6 16:53:46 WOLVY init: mysql post-start process (18803) terminated with status 1
Jun 6 16:53:46 WOLVY kernel: [14800.325936] type=1400 audit(1307372026.507:507): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=18887 comm="apparmor_parser"
Jun 6 16:53:46 WOLVY init: mysql main process (18891) terminated with status 1
Jun 6 16:53:46 WOLVY init: mysql main process ended, respawning
Jun 6 16:54:16 WOLVY init: mysql post-start process (18892) terminated with status 1
Jun 6 16:54:16 WOLVY kernel: [14830.570299] type=1400 audit(1307372056.751:508): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=18977 comm="apparmor_parser"
Jun 6 16:54:16 WOLVY init: mysql main process (18981) terminated with status 1
Jun 6 16:54:16 WOLVY init: mysql main process ended, respawning
Jun 6 16:54:46 WOLVY init: mysql post-start process (18982) terminated with status 1
Jun 6 16:54:46 WOLVY kernel: [14860.790120] type=1400 audit(1307372086.972:509): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=19089 comm="apparmor_parser"
Jun 6 16:54:47 WOLVY init: mysql main process (19093) terminated with status 1
Jun 6 16:54:47 WOLVY init: mysql main process ended, respawning
Jun 6 16:55:17 WOLVY init: mysql post-start process (19094) terminated with status 1

deepblue
deepblue
Niveau 16
06 juin 2011 à 21:32:26

$ mysql -u"ton login" -p"ton mot de passe"
ça donne quoi ?

Wolveryne2
Wolveryne2
Niveau 7
07 juin 2011 à 00:47:24

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

deepblue
deepblue
Niveau 16
07 juin 2011 à 09:10:36

tu peux me donner le contenu de /etc/mysql/my.cnf stp ?

Wolveryne2
Wolveryne2
Niveau 7
07 juin 2011 à 12:07:39

Le voilà :

:d)

#

  1. The MySQL database server configuration file.

#

  1. You can copy this to one of:
  2. - "/etc/mysql/my.cnf" to set global options,
  3. - "~/.my.cnf" to set user-specific options.
  4. One can use all long options that the program supports.
  5. Run program with --help to get a list of available options and with
  6. --print-defaults to see which it would actually understand and use.

#

  1. For explanations see
  2. http://dev.mysql.com/doc/mysql/en/server-system-variables.html
  1. This will be passed to all mysql clients
  2. It has been reported that passwords should be enclosed with ticks/quotes
  3. escpecially if they contain "#" chars...
  4. Remember to edit /etc/mysql/debian.cnf when changing the socket location.

[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

  1. Here is entries for some specific programs
  2. The following values assume you have at least 32M ram
  1. 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
  1. If you make changes to these settings and your system uses apparmor, you may
  2. 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

#

  1. Instead of skip-networking the default is now to listen only on
  2. 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

  1. This replaces the startup script and checks MyISAM tables if needed
  2. the first time they are touched

myisam-recover = BACKUP

  1. max_connections = 100
  2. table_cache = 64
  3. thread_concurrency = 10

#

    • Query Cache Configuration

#

query_cache_limit = 1M
query_cache_size = 16M

#

    • Logging and Replication

#

  1. Both location gets rotated by the cronjob.
  2. Be aware that this log type is a performance killer.
  3. As of 5.1 you can enable the log at runtime!
  4. general_log_file = /var/log/mysql/mysql.log
  5. general_log = 1

log_error = /var/log/mysql/error.log

  1. Here you can see queries with especially long duration
  2. log_slow_queries = /var/log/mysql/mysql-slow.log
  3. long_query_time = 2
  4. log-queries-not-using-indexes

#

  1. The following can be used as easy to replay backup logs or for replication.
  2. note: if you are setting up a replication slave, see README.Debian about
  3. other settings you may need to change.
  4. server-id = 1
  5. log_bin = /var/log/mysql/mysql-bin.log

expire_logs_days = 10
max_binlog_size = 100M

  1. binlog_do_db = include_database_name
  2. binlog_ignore_db = include_database_name

#

    • InnoDB

#

  1. InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
  2. Read the manual for more InnoDB related options. There are many!

#

    • Security Features

#

  1. Read the manual, too, if you want chroot!
  2. chroot = /var/lib/mysql/

#

  1. For generating SSL certificates I recommend the OpenSSL GUI "tinyca".

#

  1. ssl-ca=/etc/mysql/cacert.pem
  2. ssl-cert=/etc/mysql/server-cert.pem
  3. ssl-key=/etc/mysql/server-key.pem

[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]

  1. 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!
  1. The files must end with '.cnf', otherwise they'll be ignored.

#

!includedir /etc/mysql/conf.d/

Wolveryne2
Wolveryne2
Niveau 7
09 juin 2011 à 19:25:01

:up:

Wolveryne2
Wolveryne2
Niveau 7
10 juin 2011 à 02:15:42

J'ai finalement fait un
"sudo dpkg-reconfigure mysql-server-5.1" j'ai pu redéfinir le mdp et ça remarche.
Par contre je comprends pas pourquoi le mdp aurait changé d'un jour à l'autre alors que j'ai rien touché.

Sous forums
  • Aide à l'achat Mac
  • Création de Jeux
  • Linux
  • Création de sites web
  • Programmation
  • Internet
  • Steam Deck
  • Macintosh
  • Hardware