Willkommen in der Webstatt Zum Webstatt Blog und Stories
Franky Franky am 05.06.06 15:23

Moin,

hab ein Problem mit dem Mysql Deamon. Der will nicht mehr starten. Er ist wohl komischerweise heute morgen abgeschmiert, warum weiß ich nicht, ich hab ihn jedenfalls nicht beendet.

Hab ihn daraufhin versucht neuzuinstallieren.
vs6609:~# apt-get install --reinstall mysql-server
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
mysql-server
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 3646kB of archives.
After unpacking 8544kB of additional disk space will be used.
Get:1 http://security.debian.org stable/updates/main mysql-server 4.0.24-10sarge2 [3646kB]
Fetched 3646kB in 1s (2310kB/s)
Preconfiguring packages ...
(Reading database ... 19539 files and directories currently installed.)
Unpacking mysql-server (from .../mysql-server_4.0.24-10sarge2_i386.deb) ...
Aborting downgrade from 4.1 to 4.0.
dpkg: error processing /var/cache/apt/archives/mysql-server_4.0.24-10sarge2_i386.deb (--unpack):
subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/mysql-server_4.0.24-10sarge2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Downgraden wollt ich net, hab also immer No gewählt..

vs6609:~# /etc/init.d/mysql start
vs6609:~# /etc/init.d/mysql
vs6609:~#

Warum gibt der nichts aus?

Komischerweise habe ich keine Logs in /var/log/ stehen...?


Könnt ihr mir helfen? Eigentlich könnte ich den (v)Server auch neu aufsetzen, aber ich brauch erst meine DB's wieder...kann ich die auch sonst iwie exportieren...ohne das der MySQL Server gestartet is'?

Gruss
Franky

//
Exportieren will er auch nicht...mhh
vs6609:~# mysqldump --opt -h localhost -u root -pXXXX --all-databases | gzip > localhost.sql.gz
mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) when trying to connect
vs6609:~#

netcup.de Warum gibt es hier Werbung?
Snake am 05.06.06 15:27

/var/log ist leer? ;(

such mal nach 'syslog'. der muss irgendwo sein...

Franky Franky am 05.06.06 15:38

/var/log/deamon.log:

Jun 4 23:54:01 vs6609 in.qpopper[19697]: connect from 80.145.223.173 (80.145.223.173)
Jun 5 01:32:01 vs6609 mysqld_safe[2806]: started
Jun 5 01:32:01 vs6609 mysqld[2811]: ^G/usr/sbin/mysqld: File '/var/log/mysql/mysql-bin.1' not found (Errcode: 2)
Jun 5 01:32:01 vs6609 mysqld[2811]: 060605 1:32:01 [ERROR] Could not use /var/log/mysql/mysql-bin for logging (error 2). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
Jun 5 01:32:01 vs6609 mysqld[2811]: 060605 1:32:01 [ERROR] Aborting
Jun 5 01:32:01 vs6609 mysqld[2811]:
Jun 5 01:32:01 vs6609 mysqld[2811]: 060605 1:32:01 [Note] /usr/sbin/mysqld: Shutdown complete
Jun 5 01:32:01 vs6609 mysqld[2811]:
Jun 5 01:32:01 vs6609 mysqld_safe[2818]: ended
Jun 5 01:32:07 vs6609 /etc/init.d/mysql[2889]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Jun 5 01:32:07 vs6609 /etc/init.d/mysql[2889]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Jun 5 01:32:07 vs6609 /etc/init.d/mysql[2889]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
Jun 5 01:32:07 vs6609 /etc/init.d/mysql[2889]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Jun 5 01:32:07 vs6609 /etc/init.d/mysql[2889]:


das ist wohl das wichtigste...was hat das zubedeuten?

Franky Franky am 05.06.06 15:43

WAS IST DAS?!
Jun 5 02:38:28 vs6609 sshd[18119]: Illegal user 1 from 222.68.192.15
Jun 5 02:38:28 vs6609 sshd[18119]: error: Could not get shadow information for NOUSER
Jun 5 02:38:28 vs6609 sshd[18119]: Failed password for illegal user 1 from 222.68.192.15 port 49773 ssh2
Jun 5 02:38:32 vs6609 sshd[18121]: Illegal user 1234 from 222.68.192.15
Jun 5 02:38:32 vs6609 sshd[18121]: error: Could not get shadow information for NOUSER
Jun 5 02:38:32 vs6609 sshd[18121]: Failed password for illegal user 1234 from 222.68.192.15 port 49815 ssh2
Jun 5 02:38:34 vs6609 sshd[18124]: Illegal user 3comcso from 222.68.192.15
Jun 5 02:38:34 vs6609 sshd[18124]: error: Could not get shadow information for NOUSER
Jun 5 02:38:34 vs6609 sshd[18124]: Failed password for illegal user 3comcso from 222.68.192.15 port 49874 ssh2
Jun 5 02:38:37 vs6609 sshd[18127]: Illegal user a from 222.68.192.15
Jun 5 02:38:37 vs6609 sshd[18127]: error: Could not get shadow information for NOUSER
Jun 5 02:38:37 vs6609 sshd[18127]: Failed password for illegal user a from 222.68.192.15 port 49917 ssh2
Jun 5 02:38:40 vs6609 sshd[18130]: Illegal user a from 222.68.192.15
Jun 5 02:38:40 vs6609 sshd[18130]: error: Could not get shadow information for NOUSER
Jun 5 02:38:40 vs6609 sshd[18130]: Failed password for illegal user a from 222.68.192.15 port 49964 ssh2
Jun 5 02:38:44 vs6609 sshd[18134]: Illegal user a from 222.68.192.15
Jun 5 02:38:44 vs6609 sshd[18134]: error: Could not get shadow information for NOUSER
Jun 5 02:38:44 vs6609 sshd[18134]: Failed password for illegal user a from 222.68.192.15 port 50012 ssh2
Jun 5 02:38:47 vs6609 sshd[18141]: Illegal user a1 from 222.68.192.15
Jun 5 02:38:47 vs6609 sshd[18141]: error: Could not get shadow information for NOUSER
Jun 5 02:38:47 vs6609 sshd[18141]: Failed password for illegal user a1 from 222.68.192.15 port 50066 ssh2
Jun 5 02:38:50 vs6609 sshd[18143]: Illegal user aa from 222.68.192.15
Jun 5 02:38:50 vs6609 sshd[18143]: error: Could not get shadow information for NOUSER
Jun 5 02:38:50 vs6609 sshd[18143]: Failed password for illegal user aa from 222.68.192.15 port 50116 ssh2
Jun 5 02:38:52 vs6609 sshd[18147]: Illegal user aaa from 222.68.192.15
Jun 5 02:38:52 vs6609 sshd[18147]: error: Could not get shadow information for NOUSER
Jun 5 02:38:52 vs6609 sshd[18147]: Failed password for illegal user aaa from 222.68.192.15 port 50165 ssh2
Jun 5 02:38:55 vs6609 sshd[18150]: Illegal user aaaa from 222.68.192.15
Jun 5 02:38:55 vs6609 sshd[18150]: error: Could not get shadow information for NOUSER
Jun 5 02:38:55 vs6609 sshd[18150]: Failed password for illegal user aaaa from 222.68.192.15 port 50208 ssh2
Jun 5 02:38:59 vs6609 sshd[18156]: Illegal user aabakken from 222.68.192.15
Jun 5 02:38:59 vs6609 sshd[18156]: error: Could not get shadow information for NOUSER
Jun 5 02:38:59 vs6609 sshd[18156]: Failed password for illegal user aabakken from 222.68.192.15 port 50257 ssh2

[....]
Jun 5 02:51:47 vs6609 sshd[19978]: Illegal user abildskov from 222.68.192.15
Jun 5 02:51:47 vs6609 sshd[19978]: error: Could not get shadow information for NOUSER
Jun 5 02:51:47 vs6609 sshd[19978]: Failed password for illegal user abildskov from 222.68.192.15 port 34510 ssh2
Jun 5 02:51:52 vs6609 sshd[19982]: Illegal user abilenki from 222.68.192.15
Jun 5 02:51:53 vs6609 sshd[19982]: error: Could not get shadow information for NOUSER
Jun 5 02:51:53 vs6609 sshd[19982]: Failed password for illegal user abilenki from 222.68.192.15 port 34560 ssh2
Jun 5 02:51:55 vs6609 sshd[19984]: Illegal user abilenki from 222.68.192.15
Jun 5 02:51:56 vs6609 sshd[19984]: error: Could not get shadow information for NOUSER
Jun 5 02:51:56 vs6609 sshd[19984]: Failed password for illegal user abilenki from 222.68.192.15 port 34643 ssh2
Jun 5 02:51:58 vs6609 sshd[19987]: Illegal user abilenki from 222.68.192.15
Jun 5 02:51:59 vs6609 sshd[19987]: error: Could not get shadow information for NOUSER
Jun 5 02:51:59 vs6609 sshd[19987]: Failed password for illegal user abilenki from 222.68.192.15 port 34693 ssh2
Jun 5 02:52:01 vs6609 CRON[19993]: (pam_unix) session opened for user web0 by (uid=0)
Jun 5 02:52:01 vs6609 CRON[19993]: (pam_unix) session closed for user web0
Jun 5 02:52:01 vs6609 sshd[19989]: Illegal user abilova from 222.68.192.15
Jun 5 02:52:06 vs6609 sshd[19989]: error: Could not get shadow information for NOUSER
Jun 5 02:52:06 vs6609 sshd[19989]: Failed password for illegal user abilova from 222.68.192.15 port 34739 ssh2

Snake am 05.06.06 16:26

also ich würde die ip sperren :D

iptables -I INPUT -s böse_IP -j DROP

und mysql...existiert der ordner "mysql" in /var/log?

Franky Franky am 05.06.06 23:24

Ah danke :D
Jap, der ist da, allerdings leer :(

und wegen dem backup...
In /var/lib/mysql sind meine datenbanken. erst die datenbanken als ordner und dann in den ordnern frm, MYD und MYI Dateien. Was kann ich damit anfangen? Wie bekomm ich da meinen Dump wieder raus?

Lg und danke :)
Franky

milahu milahu am 06.06.06 11:59

Was produziert denn folgender Befehl?
mysqld --console --verbose --basedir=/var/lib/mysql/
Mit dem basedir bin ich mir nicht ganz sicher, aber er wird sich schon rühren ;)

Hast eigentlich schonmal probiert, die Logfiles anzulegen? (touch /var/log/...)

Franky Franky am 06.06.06 14:17

Ach was schön..
vs6609:~# mysqld --console --verbose --basedir=/var/lib/mysql/
-bash: mysqld: command not found


Mit dem testen ob writeable,...das geht jap.
~~> http://board.star-hosting.de/thread.php?threadid=915

milahu milahu am 06.06.06 15:44

Probier mal den mysqld aus /usr/sbin/ ;)

Ich meinte, du sollst leere Logdateien anlegen -- mysqld meckert doch, er findet sie nicht.

Creative Commons Lizenzvertrag
Alle Inhalte des Webstatt-Archivs stehen unter einer Creative Commons Namensnennung - Weitergabe unter gleichen Bedingungen 3.0 Unported Lizenz.

Impressum & Kontakt