mysql.sock problem

Bitte loggen sie sich ein oder registrieren sie sich.

Einloggen mit Benutzername, Passwort und Sitzungslänge
Erweiterte Suche  

Autor Thema: mysql.sock problem  (Gelesen 8685 mal)

0 Mitglieder und 1 Gast betrachten dieses Thema.

Thagam

  • Grünschnabel
  • *
  • Offline Offline
  • Beiträge: 19
mysql.sock problem
« am: 13.Oktober 2009, 20:55:33 »

Ich hatte ein paar my.cnf Einstellungen getätigt und daraufhin den mysql ordner von /var/lib/mysql zu /data/mysql verschoben (via mv), hab es dannach aber wieder zurück verschoben.
Jedoch funktioniert nun mysql nicht mehr und beim Plesk Kontrollbereich kommt folgende Fehlermeldung:

ERROR: PleskFatalException
Unable to connect to database: mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)

0: common_func.php3:108
   psaerror(string 'Unable to connect to database: mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)')
1: auth.php3:93


Weiß einer was ich da tun muss? Höchstwahrscheinlich liegt es ja an der socket datei.
Falls nicht, würd ich gerne wisse wie ich die mysql Datenbanken per shell auf mein Pc exportieren kann.


Freue mich über Antworten.


MfG
Gespeichert


cmdLine

  • Gast
Re: mysql.sock problem
« Antwort #1 am: 13.Oktober 2009, 22:41:31 »

Dateirechte? Socket neu anlegen?
Gespeichert

Thagam

  • Grünschnabel
  • *
  • Offline Offline
  • Beiträge: 19
Re: mysql.sock problem
« Antwort #2 am: 13.Oktober 2009, 22:47:37 »

Ja, ich sehe gerade dass mir jetzt die mysql.sock fehlt.
Nur weiß ich nicht wie ich mir eine neue zulegen kann?


MfG Thagam


Edit:
Ich merk gerade, dass die mysl.sock beim hochfahren existiert und beim mysql runterfahren wieder gelöscht wird.
Aber woran könnte das Problem sonst liegen?

nochmal edit:
Jetzt sehe ich, dass die mysql.sock überhaupt nicht mehr angezeigt wird

Starting service MySQL warning: /var/lib/mysql/mysql.sock didn't appear within 30 seconds
« Letzte Änderung: 13.Oktober 2009, 22:56:57 von Thagam »
Gespeichert

Thagam

  • Grünschnabel
  • *
  • Offline Offline
  • Beiträge: 19
Re: mysql.sock problem
« Antwort #3 am: 14.Oktober 2009, 00:02:02 »

Mit dem Befehl:
mysqld_safe --skip-bdb

hab ich wieder die mysql.sock unter /var/lib/mysql, welche pink angezeigt wird.

jedoch funktioniert mysql immernoch nicht, obwohl e gestartet ist.
Es kommt nach wie vor diese Fehlermeldung von der mysql.sock
Gespeichert

cmdLine

  • Gast
Re: mysql.sock problem
« Antwort #4 am: 14.Oktober 2009, 00:03:05 »

Was sagen die Log-Files /var/log/mysqld.log bzw. /var/log/messages?
Gespeichert

Thagam

  • Grünschnabel
  • *
  • Offline Offline
  • Beiträge: 19
Re: mysql.sock problem
« Antwort #5 am: 14.Oktober 2009, 00:33:56 »

InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
091014  0:24:09  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
091014  0:24:09  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
091014  0:24:09 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
091014  0:24:09 [ERROR] Do you already have another mysqld server running on port: 3306 ?
091014  0:24:09 [ERROR] Aborting

091014  0:24:09 [Note] /usr/sbin/mysqld: Shutdown complete

091014 00:24:09  mysqld ended
Gespeichert

uname

  • Gast
Re: mysql.sock problem
« Antwort #6 am: 14.Oktober 2009, 08:33:33 »

An den Konfigurationen sollte man nicht unbedingt rumdrehen. Es haben sich Leute Gedanken gemacht, die mehr Ahnung von Linux haben als Du und ich.

Die Datei ist eigentlich (bei meinem Debian):

srwxrwxrwx 1 mysql mysql 0 16. Sep 13:01 /var/run/mysqld/mysqld.sock

Nun ist es so, dass vielleicht die Datei weg ist, der Dienst jedoch aufgrund der alten Einstellung noch läuft. Entweder neu booten (ok macht man nicht), oder den Dienst mit Gewalt beenden.

ps -ef |fgrep mysqld

root      2508     1  0 Sep16 ?        00:00:00 /bin/sh /usr/bin/mysqld_safe
mysql     2547  2508  0 Sep16 ?        00:48:28 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock
root      2549  2508  0 Sep16 ?        00:00:00 logger -p daemon.err -t mysqld_safe -i -t mysqld

In meinem Fall den Prozess "2508" beenden, der Rest hängt sowieso daran:

kill -9 2508
sollte reichen.
Gespeichert

Thagam

  • Grünschnabel
  • *
  • Offline Offline
  • Beiträge: 19
Re: mysql.sock problem
« Antwort #7 am: 14.Oktober 2009, 12:04:43 »

Danke erstmal für die Antworten

Zitat
root      3923     1  0 11:52 pts/1    00:00:00 /bin/sh /usr/bin/mysqld_safe --mysqld=mysqld --user=mysql --pid-file=/var/lib/mysql/mysqld.pid --socket=/var/lib/mysql/mysql.sock --datadir=/var/lib/mysql
mysql     3972  3923  0 11:52 pts/1    00:00:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid --skip-external-locking --port=3306 --socket=/var/lib/mysql/mysql.sock
root      4125  2986  0 11:53 pts/1    00:00:00 fgrep mysqld

Da beendete ich die beiden mysql prozesse mit kill -9 (vorher beendete ich auch apache)
Dannach startete ih mysql mit "sudo service mysql start" und "sudo service apache2 start"
Trotzdem kommt unter Plesk kontrollbereich die Socket fehlermeldung.
Auch mit mysqld_safe versuchte ich es.
Vllt mach ich auch ne falsche Reihenfolge, aber hab schon alles möglich versucht aber komm leider nicht weiter..


Ist es übrigens normal, dass ich unter /data meinen Datenbanknamen Ordner finde, indem meine datenbank tabellen sind? Müssen die nicht auf /var/lib/mysql sein? Also dem Ordner mit der socket?


MfG Thagam

Achja: Was mir noch weiterhelfen könnte:
könnt mir jemand den Inhalt der /etc/php5/apache2/php.ini posten?
und evtl sagen was unter dem mysql ordner (wo die msql.sock bei euch ist) aufgelistet wird?
Ich komm einfach nicht mehr weiter.
« Letzte Änderung: 14.Oktober 2009, 14:18:23 von Thagam »
Gespeichert

Phil-Ist-Online

  • Grünschnabel
  • *
  • Offline Offline
  • Beiträge: 7
Re: mysql.sock problem
« Antwort #8 am: 29.Mai 2010, 17:47:08 »

Hallo ihr lieben,

hier wurde zwar schon lange nicht mehr gepostet aber ich habe genau das gleiche Problem!

Wenn ich per Putty "mysql start" angebe, bekomme ich folgende meldung:

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


Komme nicht mehr in die Plesk Administratoroberfläche und habe das leider erst heute gemerkt!

Würde mich über Antwort freuen!

MfG
PhiL
Gespeichert
 

Seite erstellt in 0.049 Sekunden mit 22 Abfragen.