Webserver auf Debian 9 - Datenbankfehler

Wildcard

New Member
Hallöschen,

leider weiß ich nicht ganz ob ich hier richtig bin :/

heute habe ich mariadb , Apache, php, phpmyadmin usw. auf meinem Vserver installiert.

jedoch wurde ich bei der installation (+neuinstallation) von mariadb nicht nach der Vergabe eines Passworts gefragt. wenn ich mich mit dem root benutzer bei Mariadb einloggen will erscheint folgende fehlermeldung:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

phpmyadmin gibt den gleichen Fehler auf deutsch aus...

kann mir da jemand helfen ?

L.G
 

Wildcard

New Member
auf medium gestellt.

Fehler weiterhin ohne änderungen. mariadb client & server nochmal neuinstalliert. nichts
 

DjTom-i

Member
Daten sichern falls vorhanden.

Deinstallieren mit --purge

/etc/mysql
/var/lib/mysql

löschen falls noch etwas davon über bleibt nach dem purgen.

Neu installieren.
 

mr_brain

Registered User
Läuft mySQL überhaupt?
Was sagt das Log?

Zur Info: Bei den neuen Debian-Versionen mySQL-Installationen wird der System-root für den mySQL-Zugriff automatisch freigeschaltet.
 

Wildcard

New Member
sudo aptitude purge mariadb-server
sudo aptitude purge mariadb-client

Ordner nicht vorhanden;

apt-get install mariadb-client mariadb-server


wieder keine konfigurationsaufforderung :/

Code:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  mariadb-client mariadb-server
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/52.2 kB of archives.
After this operation, 127 kB of additional disk space will be used.
Selecting previously unselected package mariadb-client.
(Reading database ... 47959 files and directories currently installed.)
Preparing to unpack .../mariadb-client_10.1.26-0+deb9u1_all.deb ...
Unpacking mariadb-client (10.1.26-0+deb9u1) ...
Selecting previously unselected package mariadb-server.
Preparing to unpack .../mariadb-server_10.1.26-0+deb9u1_all.deb ...
Unpacking mariadb-server (10.1.26-0+deb9u1) ...
Setting up mariadb-client (10.1.26-0+deb9u1) ...
Setting up mariadb-server (10.1.26-0+deb9u1) ..
.

mehr kam nicht
 

Wildcard

New Member
Läuft mySQL überhaupt?
Was sagt das Log?

Zur Info: Bei den neuen Debian-Versionen mySQL-Installationen wird der System-root für den mySQL-Zugriff automatisch freigeschaltet.
Wo finde ich das log :eek: bin noch nicht zu erfahren im Bereich der Server
 

Wildcard

New Member
hab mysql versucht neu zu staren:

Code:
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.
 

Wildcard

New Member
~ # journalctl -xe
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mysql.service has begun starting up.
Aug 03 13:46:28 Teamspeak mysql-systemd-start[18405]: MySQL configuration not found at /etc/mysql/my.cnf. Please install one.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Control process exited, code=exited status=1
Aug 03 13:46:28 Teamspeak systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Unit entered failed state.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 03 13:46:28 Teamspeak systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mysql.service has finished shutting down.
Aug 03 13:46:28 Teamspeak systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mysql.service has begun starting up.
Aug 03 13:46:28 Teamspeak mysql-systemd-start[18442]: MySQL configuration not found at /etc/mysql/my.cnf. Please install one.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Control process exited, code=exited status=1
Aug 03 13:46:28 Teamspeak systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Unit entered failed state.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 03 13:46:28 Teamspeak systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mysql.service has finished shutting down.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Start request repeated too quickly.
Aug 03 13:46:28 Teamspeak systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Unit entered failed state.
Aug 03 13:46:28 Teamspeak systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 03 13:47:14 Teamspeak sshd[18481]: Did not receive identification string from 82.207.46.234 port 52016
Aug 03 13:47:14 Teamspeak sshd[18482]: Unable to negotiate with 82.207.46.234 port 63782: no matching cipher found. Their offer: aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc [preauth]
lines 2167-2228/2228 (END)
 
Top