Zugriff auf die MySQL Datenbank Fehlgeschlagen

Nabend Wordpress Community,

als ich heute Xampp mit dem Apache und der MySQL neustartete und Wordpress nutzen wollte, bekam ich die Fehlermeldung das nicht auf die Datenbank zugegriffen werden kann. Nach mehreren Neustarts von Xampp und seinen Servern konnte ich weiterhin Wordpress nicht nutzen.

Der Zugriff auf PHPMyAdmin selbst funktioniert reibungslos. Auch eine Neuinstallation von Wordpress ist nicht möglich da weiterhin kein Zugriff möglich ist.
Eine weitere ausprobierte Mathode war xampp mit allen Daten zu deinstallieren und neu aufuzuspielen. Weitehin ohne Erfolg.

Login daten zur Datenbank sind auch inordung da der Fehler ja schon NACH einer erfolgreichen Installation plötzlich auftrat.

Kann mir einer den Grund für diesen Fehler sagen und mir vielleicht eine Lösung dafür geben.

MfG 3xill

Nutze es Lokal aufm Rechner was bis heute ohne probleme lief.

Apache Error log:

Zitat

[Mon Aug 26 23:07:11.442431 2013] [ssl:warn] [pid 8040:tid 244] AH01909: RSA certificate configured for http://www.example.com:443 does NOT include an ID which matches the server name
[Mon Aug 26 23:07:11.933459 2013] [ssl:warn] [pid 8040:tid 244] AH01909: RSA certificate configured for http://www.example.com:443 does NOT include an ID which matches the server name
[Mon Aug 26 23:07:12.044466 2013] [mpm_winnt:notice] [pid 8040:tid 244] AH00455: Apache/2.4.4 (Win32) OpenSSL/1.0.1e PHP/5.5.1 configured -- resuming normal operations
[Mon Aug 26 23:07:12.044466 2013] [mpm_winnt:notice] [pid 8040:tid 244] AH00456: Server built: Feb 23 2013 12:42:00
[Mon Aug 26 23:07:12.044466 2013] [core:notice] [pid 8040:tid 244] AH00094: Command line: 'c:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache'
[Mon Aug 26 23:07:12.048466 2013] [mpm_winnt:notice] [pid 8040:tid 244] AH00418: Parent: Created child process 6056
[Mon Aug 26 23:07:12.823510 2013] [ssl:warn] [pid 6056:tid 256] AH01909: RSA certificate configured for http://www.example.com:443 does NOT include an ID which matches the server name
[Mon Aug 26 23:07:13.339540 2013] [ssl:warn] [pid 6056:tid 256] AH01909: RSA certificate configured for http://www.example.com:443 does NOT include an ID which matches the server name
[Mon Aug 26 23:07:13.409544 2013] [mpm_winnt:notice] [pid 6056:tid 256] AH00354: Child: Starting 150 worker threads.
[Mon Aug 26 23:25:38.317741 2013] [ssl:warn] [pid 7772:tid 244] AH01909: RSA certificate configured for http://www.example.com:443 does NOT include an ID which matches the server name
[Mon Aug 26 23:25:38.409746 2013] [core:warn] [pid 7772:tid 244] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Aug 26 23:25:38.785768 2013] [ssl:warn] [pid 7772:tid 244] AH01909: RSA certificate configured for http://www.example.com:443 does NOT include an ID which matches the server name
[Mon Aug 26 23:25:38.856772 2013] [mpm_winnt:notice] [pid 7772:tid 244] AH00455: Apache/2.4.4 (Win32) OpenSSL/1.0.1e PHP/5.5.1 configured -- resuming normal operations
[Mon Aug 26 23:25:38.856772 2013] [mpm_winnt:notice] [pid 7772:tid 244] AH00456: Server built: Feb 23 2013 12:42:00
[Mon Aug 26 23:25:38.856772 2013] [core:notice] [pid 7772:tid 244] AH00094: Command line: 'c:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache'
[Mon Aug 26 23:25:38.862772 2013] [mpm_winnt:notice] [pid 7772:tid 244] AH00418: Parent: Created child process 8728
[Mon Aug 26 23:25:39.571813 2013] [ssl:warn] [pid 8728:tid 256] AH01909: RSA certificate configured for http://www.example.com:443 does NOT include an ID which matches the server name
[Mon Aug 26 23:25:39.975836 2013] [ssl:warn] [pid 8728:tid 256] AH01909: RSA certificate configured for http://www.example.com:443 does NOT include an ID which matches the server name
[Mon Aug 26 23:25:40.043840 2013] [mpm_winnt:notice] [pid 8728:tid 256] AH00354: Child: Starting 150 worker threads.

Alles anzeigen

MySQL Log:

Zitat

2013-08-26 23:07:16 8836 [Note] Plugin 'FEDERATED' is disabled.
2013-08-26 23:07:16 2044 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-08-26 23:07:16 8836 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-26 23:07:16 8836 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-26 23:07:16 8836 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-26 23:07:16 8836 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-26 23:07:16 8836 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-26 23:07:16 8836 [Note] InnoDB: Completed initialization of buffer pool
2013-08-26 23:07:16 8836 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-08-26 23:07:16 8836 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-08-26 23:07:16 8836 [Note] InnoDB: Database physically writes the file full: wait...
2013-08-26 23:07:17 8836 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-08-26 23:07:17 8836 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-08-26 23:07:17 8836 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-08-26 23:07:17 8836 [Warning] InnoDB: New log files created, LSN=45781
2013-08-26 23:07:17 8836 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-08-26 23:07:18 8836 [Note] InnoDB: Doublewrite buffer created
2013-08-26 23:07:19 8836 [Note] InnoDB: 128 rollback segment(s) are active.
2013-08-26 23:07:19 8836 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-08-26 23:07:19 8836 [Note] InnoDB: Foreign key constraint system tables created
2013-08-26 23:07:19 8836 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-08-26 23:07:19 8836 [Note] InnoDB: Tablespace and datafile system tables created.
2013-08-26 23:07:19 8836 [Note] InnoDB: Waiting for purge to start
2013-08-26 23:07:19 8836 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-08-26 23:07:19 8836 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 7e79878d-0e93-11e3-a1e8-00ff0068d1c9.
2013-08-26 23:07:19 8836 [Note] Server hostname (bind-address): '*'; port: 3306
2013-08-26 23:07:19 8836 [Note] IPv6 is available.
2013-08-26 23:07:19 8836 [Note] - '::' resolves to '::';
2013-08-26 23:07:19 8836 [Note] Server socket created on IP: '::'.
2013-08-26 23:07:19 8836 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:19 8836 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-08-26 23:07:19 8836 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:19 8836 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:19 8836 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-08-26 23:07:19 8836 [Note] Event Scheduler: Loaded 0 events
2013-08-26 23:07:19 8836 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-08-26 23:07:26 8836 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:26 8836 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:26 8836 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:26 8836 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:26 8836 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.

Alles anzeigen

Fortsetzung folgt

Weiterhin der SQL Log

Zitat

2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:28 8836 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:31 8836 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:31 8836 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:31 8836 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:31 8836 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:07:31 8836 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:25:37 8904 [Note] Plugin 'FEDERATED' is disabled.
2013-08-26 23:25:37 2164 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-08-26 23:25:37 8904 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-26 23:25:37 8904 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-26 23:25:37 8904 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-26 23:25:37 8904 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-26 23:25:37 8904 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-26 23:25:37 8904 [Note] InnoDB: Completed initialization of buffer pool
2013-08-26 23:25:37 8904 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-26 23:25:37 8904 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600614 in the ib_logfiles!
2013-08-26 23:25:37 8904 [Note] InnoDB: Database was not shutdown normally!
2013-08-26 23:25:37 8904 [Note] InnoDB: Starting crash recovery.
2013-08-26 23:25:37 8904 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-26 23:25:37 8904 [Note] InnoDB: Restoring possible half-written data pages
2013-08-26 23:25:37 8904 [Note] InnoDB: from the doublewrite buffer...
2013-08-26 23:25:38 8904 [Note] InnoDB: 128 rollback segment(s) are active.
2013-08-26 23:25:38 8904 [Note] InnoDB: Waiting for purge to start
2013-08-26 23:25:38 8904 [Note] InnoDB: 5.6.11 started; log sequence number 1600614
2013-08-26 23:25:38 8904 [Note] Server hostname (bind-address): '*'; port: 3306
2013-08-26 23:25:38 8904 [Note] IPv6 is available.
2013-08-26 23:25:38 8904 [Note] - '::' resolves to '::';
2013-08-26 23:25:38 8904 [Note] Server socket created on IP: '::'.
2013-08-26 23:25:38 8904 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:25:38 8904 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-08-26 23:25:38 8904 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:25:38 8904 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6…leshooting.html for how you can resolve the problem.
2013-08-26 23:25:38 8904 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-08-26 23:25:38 8904 [Note] Event Scheduler: Loaded 0 events
2013-08-26 23:25:38 8904 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)

Alles anzeigen

Backup nur von der htdocs leider, MySQL neu augesetzt.

Und Link aus der Log kontrollierte ich nicht

Das ist Richtig.

Im nachhinein überlegt eine unüberlegte Entscheidung.
Aber außer selbst erstellte Themes war bei Wordpress eh nicht drin.
Und bis auf ein fast blankes Wordpress nichts in der Datenbank

Zitat von Appendix

Das WP läuft nicht, ohne Datenbank. Selbst ohne Inhalte (Artikel/Seiten/etc) sind ja die ganzen Einstellungen in der DB gespeichert.

Ich Installierte komplett Xampp Plus MySQl neu und versuche gerade WP neu zu installieren. Da kommt mir aber weiterhin der Fehler in die quere das die datenbank nicht aufrufbar ist. Was aber mit PhpMyAdmin möglich ist und ich nicht begreifen kann warum WP das nicht kann

Zitat von Appendix

Stimmt denn auch der Datenbankname +User noch mir dem über ein, was du eingibst?

Ja Stimmen 1 zu 1 überein, mehre male Kontrolliert

Zitat von Appendix

Auch hier der Rat, Browsercache löschen, dann Installation ausführen.

Browsercache nach Tipp deinerseits gellert und erneut versucht, nachwievor kein Erfolg

Ich bekomme die Selbe meldungen wie vorhen bis garkeine meldung des Logs.

Der Datenbank selber nein und das User Password des Roots ist eingetragen

Die Installation ist aufrufbar. Ich kann alles für die Datenbank eintragen und wenn er versucht sich in die Datebbank aufzurufen kommt folgendes:

Zitat

[h=1]Fehler beim Aufbau der Datenbank-Verbindung[/h] Das bedeutet entweder, dass Benutzername oder Passwort in der Datei wp-config.php falsch sind oder der Datenbankserver localhost nicht erreichbar ist.

• Bist du sicher, dass Benutzername und Passwort stimmen?
• Bist du sicher, dass der Name des Datenbankservers stimmt?
• Bist du sicher, dass der Datenbankserver läuft?

Wenn du nicht sicher bist, woran es liegt, kontaktiere am besten deinen Hoster. Wenn du weitergehende Hilfe brauchst, kannst du dich jederzeit an das Support-Forum (en) wenden.

Und ja alle drei Punkte habe ich kontrolliert und es läuft nicht

Programm sind zuviele um es zu testen.
Alternativ hab ich ein Funpic Account, ist zwar umständlicher aber geht wenigstens.
Den test mit einer anderen Datenbank mache ich norgen mal