keine-angst-vorm-pc.de » Software » sonstige Software Fragen » mysql

mysql

magicmatze
also hab noch ein fehler festgestellt und zwar stürt auf meinen mysql server andauern die exe ab hab schon versucht ne andere version von mysql zu benutzen klapt aber auch nicht stürtz immer wieder ab habe mir auch die .err datei angeguckt weiss aber trotzdem nicht woran das liegt ier die .err datei das steht dort drinne:


060111 12:50:45 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 100 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
060111 12:50:51 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 100 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
060111 12:50:58 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060111 12:50:59 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 4 2174102028.
InnoDB: Doing recovery: scanned up to log sequence number 4 2174102028
InnoDB: Last MySQL binlog file position 0 0, file name
060111 12:50:59 InnoDB: Started; log sequence number 4 2174102028
060111 12:50:59 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.9-beta-nt' socket: '' port: 3306 Official MySQL binary
060111 12:51:55 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

060111 12:51:56 InnoDB: Starting shutdown...
060111 12:52:00 InnoDB: Shutdown completed; log sequence number 4 2175092685
060111 12:52:00 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

060111 12:52:03 InnoDB: Started; log sequence number 4 2175092685
060111 12:52:03 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.9-beta-nt-max' socket: '' port: 3306 Official MySQL binary
060111 12:52:30 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Normal shutdown

060111 12:52:31 InnoDB: Starting shutdown...
060111 12:52:34 InnoDB: Shutdown completed; log sequence number 4 2175411542
060111 12:52:34 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Shutdown complete

060111 12:52:38 InnoDB: Started; log sequence number 4 2175411542
060111 12:52:38 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.9-beta-nt-max' socket: '' port: 3306 Official MySQL binary
060111 13:05:18 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060111 13:05:23 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 4 2188208883.
InnoDB: Doing recovery: scanned up to log sequence number 4 2188251760
060111 13:05:25 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 0, file name
060111 13:05:25 InnoDB: Started; log sequence number 4 2188251760
060111 13:05:26 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.9-beta-nt-max' socket: '' port: 3306 Official MySQL binary
060111 13:06:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Normal shutdown
GreenRover
Da ist nichts von zu sehen woran es liegt, das das ganze abgestürtzt ist.

Hast du noch andere logs ?
magicmatze
060111 20:48:14060111 20:48:14 [ERROR] Cannot find table mails/mail_hiphopboy87 from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

060111 20:48:14060111 20:48:14 [ERROR] Cannot find table mails/mail_hiphopboy87 from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

060111 20:48:14060111 20:48:14 [ERROR] Cannot find table mails/mail_hiphopboy87 from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

060111 20:48:14060111 20:48:14 [ERROR] Cannot find table mails/mail_hiphopboy87 from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

060111 20:48:14060111 20:48:14 [ERROR] Cannot find table mails/mail_hiphopboy87 from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

060111 20:48:14060111 20:48:14 [ERROR] Cannot find table mails/mail_hiphopboy87 from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

060111 23:08:35 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Normal shutdown

060111 23:08:37 InnoDB: Starting shutdown...
060111 23:08:39 InnoDB: Shutdown completed; log sequence number 4 2459162360
060111 23:08:39 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Shutdown complete

060111 23:08:43 InnoDB: Started; log sequence number 4 2459162360
060111 23:08:43 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.18-nt-max' socket: '' port: 3306 MySQL Community Edition (GPL)
060112 15:50:44 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Normal shutdown

060112 15:50:46 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Forcing close of thread 128032 user: ''

060112 15:50:46 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Forcing close of thread 128029 user: 'root'

060112 15:50:46 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Forcing close of thread 128026 user: ''

060112 15:50:46 InnoDB: Starting shutdown...
060112 15:50:51 InnoDB: Shutdown completed; log sequence number 4 2618582549
060112 15:50:51 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Shutdown complete

060112 15:51:23 InnoDB: Started; log sequence number 4 2618582549
060112 15:51:23 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.18-nt-max' socket: '' port: 3306 MySQL Community Edition (GPL)
magicmatze
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:29:44 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:29:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:29:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:29:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:29:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:29:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:29:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:29:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:29:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:30:03 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:30:03 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:30:03 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:30:03 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:30:03 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:30:03 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\freunde\kurdin<img src=.frm' (errno: 22)
060111 18:30:03 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
060111 18:30:03 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max: Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)
GreenRover
joa ich kann dir bestätigen das du dein DBMS schön zerlegt hast.

Herzlichen glückwunsch und lass am besten die Finger von der Servertechnick. Oder lass dir zeigen wie es geht.
magicmatze
was hab ich gemacht ?
GreenRover
Can't find file: '.\mails\mail_kurdin<img src=.frm' (errno: 22)

<img src= ist html und keine dateinamens bezeichnung.

Ka wie du das geschafft hast. Aber das sollte dein Problem erklären.
magicmatze
kann das vielleicht drana liegen das in der db html scripts gespeichert werden?
GreenRover
nee, sei den die db bezeichnung ist schon html. aber das währe ja schwachhsinn.

da db und tabellen bezeichnungen ja meist vordefiniert werden.
magicmatze
aber wie ist es möglich also bei der anemeldung erstellt er eine db nach den nicknamen und man kan nur a-z und 0-9 in seinen nicknamen verwenden wie kan es sein das er dan dieses <img.. da rein macht?
GreenRover
JA die Frage kannst glaube ich nicht beantworten, das kannst nur du.

Aber auf jeden fall ist deine DB schrott, was das DBMS zum absturtz bringt.

das heist sichern was geht alle datenabnken löschen und dann komplett neu aufbauen
magicmatze
kopiert er dan nicht die fehler mit wen ich ein backup mache?
magicmatze
und liegt es vielleicvht daran das meine mysql hackt?
GreenRover
eigentlich nicht, also ein mysql dump backup und dann alles manuell durchsehen .... also alle CRAETE TABLE und CREATE DATABASE und die für die user rechte.

Alle begutachten und auf solche fehler checken.

... Vorher den server blanko, also ohne irgent welche datenabnken min ! studnel aufen lassen zum testen.
magicmatze
habe nochmal eine frage und zwar was hat das zu bedeuten?


060113 11:50:12 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 4 2878096411.
InnoDB: Doing recovery: scanned up to log sequence number 4 2878096411
InnoDB: Last MySQL binlog file position 0 0, file name
060113 11:50:13 InnoDB: Started; log sequence number 4 2878096411
060113 11:50:13 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.18-nt-max' socket: '' port: 3306 MySQL Community Edition (GPL)
060113 11:54:26 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060113 11:54:35 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 4 2878096411.
InnoDB: Doing recovery: scanned up to log sequence number 4 2878096411
InnoDB: Last MySQL binlog file position 0 0, file name
060113 11:54:36 InnoDB: Started; log sequence number 4 2878096411
060113 11:54:37 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.18-nt-max' socket: '' port: 3306 MySQL Community Edition (GPL)
060113 12:00:09 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060113 12:00:18 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 4 2878096411.
InnoDB: Doing recovery: scanned up to log sequence number 4 2878096411
InnoDB: Last MySQL binlog file position 0 0, file name
060113 12:00:19 InnoDB: Started; log sequence number 4 2878096411
060113 12:00:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.18-nt-max' socket: '' port: 3306 MySQL Community Edition (GPL)
GreenRover
Was meisnt du genau ??

Also das ist immer ein absatz:


code: 
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:

060113 11:54:35 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 4 2878096411.
InnoDB: Doing recovery: scanned up to log sequence number 4 2878096411
InnoDB: Last MySQL binlog file position 0 0, file name
060113 11:54:36 InnoDB: Started; log sequence number 4 2878096411
060113 11:54:37 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.18-nt-max' socket: '' port: 3306 MySQL Community Edition (GPL)
060113 12:00:09 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...


also server hochfahren festellen das er beim letzten mal abgeschmiert ist und versuchen es zu kompensieren.
magicmatze
so habe es endlich hinbekommen stürtz nicht mehr ab aber nur habe ich noch ein problem und zwar bei der function mysql_num_rows() er zeigt nie die genau anzahl an ist immer unterschiedlich woran liegt das?
magicmatze
habe festgestllt das es daran liegt das meine db eine innodb ist!

und das er nie die daten aktualiesiert oder speicher nie richtig wie kan ich das unterdrücken ?
GreenRover
wie jetzt ???

auf jeden fall halt keien innoDB verwenden.

Dann meinst du wohl das er fast alle daten im ram hat und nicht auf der HDD ablegt oder wie?
magicmatze
ja gneau und dann nach einiger zeit löscht er das ausn ram und nimmt das gleiche wieder auser hdd
nächste Seite