Search found 7123 matches: mysql can't start

Searched query: +mysql +can't +start

Return to advanced search

Tables not showing on Database

Hi,

I had a xampp on my local drive of pc, before some days, for some reasons I have to format my whole pc. I backup my xampp folder to my external drive. Then I install portable xampp on my external drive.

Then I copy all folders from htdocs to take my projects on new xampp. Then I copy whole data folder of mysql folder to new mysql data folder. After I start my xampp and go to phpmyadmin, what I am seeing is I got all databases but some of databases missing all tables and some of databases have 1 or 2 tables, I didn't got all tables into none of database.

I also tried to copy one by one folder from old data table to new data folder but not worked. I also tried to first make the database on new xampp then copy only files of particular database folder to new database folder but that not worked too. :roll:

Please help me to recover my all tables of all databases. :( Its urgent, I am running out of time for deadline of my project. :| :(

Thanks for the help.

Regards,
Palak
by pbcomput
13. October 2013 04:21
 
Forum: XAMPP for Windows
Topic: Tables not showing on Database
Replies: 6
Views: 3572

MYSQL startet nicht mehr

Hallo an alle, mein MYSQL startet nicht mehr, hoffe ihr könnt mir helfen.

Hier die mysql_error:

Code: Select all
2013-10-11 01:11:47 6028 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 01:11:47 2698 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-10-11 01:11:47 6028 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 01:11:47 6028 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 01:11:47 6028 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 01:11:47 6028 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 01:11:47 6028 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 01:11:47 6028 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 01:11:47 6028 [Note] InnoDB: The first specified data file \xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-10-11 01:11:47 6028 [Note] InnoDB: Setting file \xampp\mysql\data\ibdata1 size to 10 MB
2013-10-11 01:11:47 6028 [Note] InnoDB: Database physically writes the file full: wait...
2013-10-11 01:11:47 6028 [Note] InnoDB: Setting log file \xampp\mysql\data\ib_logfile101 size to 5 MB
2013-10-11 01:11:47 6028 [Note] InnoDB: Setting log file \xampp\mysql\data\ib_logfile1 size to 5 MB
2013-10-11 01:11:48 6028 [Note] InnoDB: Renaming log file \xampp\mysql\data\ib_logfile101 to \xampp\mysql\data\ib_logfile0
2013-10-11 01:11:48 6028 [Warning] InnoDB: New log files created, LSN=45781
2013-10-11 01:11:48 6028 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-10-11 01:11:49 6028 [Note] InnoDB: Doublewrite buffer created
2013-10-11 01:11:55 6028 [Note] InnoDB: 128 rollback segment(s) are active.
2013-10-11 01:11:55 6028 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-10-11 01:11:56 6028 [Note] InnoDB: Foreign key constraint system tables created
2013-10-11 01:11:56 6028 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-10-11 01:11:56 6028 [Note] InnoDB: Tablespace and datafile system tables created.
2013-10-11 01:11:56 6028 [Note] InnoDB: Waiting for purge to start
2013-10-11 01:11:56 6028 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-10-11 01:11:56 6028 [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: 5bb501db-3201-11e3-88ef-001a9252d87c.
2013-10-11 01:11:56 6028 [Note] Server hostname (bind-address): '*'; port: 3306
2013-10-11 01:11:56 6028 [Note] IPv6 is available.
2013-10-11 01:11:56 6028 [Note]   - '::' resolves to '::';
2013-10-11 01:11:56 6028 [Note] Server socket created on IP: '::'.
2013-10-11 01:11:58 6028 [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/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-10-11 01:11:58 6028 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-10-11 01:11:58 6028 [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/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-10-11 01:11:58 6028 [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/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-10-11 01:11:58 6028 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-10-11 01:11:59 6028 [Note] Event Scheduler: Loaded 0 events
2013-10-11 01:11:59 6028 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11'  socket: ''  port: 3306  MySQL Community Server (GPL)
2013-10-11 01:32:20 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:20 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:20 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:20 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:22 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:22 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:22 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:22 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_options" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_users" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_usermeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_terms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_term_taxonomy" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_posts" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_term_relationships" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_comments" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_postmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:36 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:36 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:32:47 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:47 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:32:49 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:49 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_usermeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:32:57 1c6c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:57 1c6c InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_commentmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 01:32:59 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:59 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:17 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:17 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:17 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:17 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:37 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:37 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:37 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:37 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:48 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:48 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 02:04:28 1c6c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 02:04:28 1c6c InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_links" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-11 15:25:33 3740 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 15:25:33 ea8 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-10-11 15:25:33 3740 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 15:25:33 3740 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 15:25:33 3740 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 15:25:33 3740 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 15:25:34 3740 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 15:25:34 3740 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 15:25:34 3740 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-11 15:25:34 3740 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2524657 in the ib_logfiles!
2013-10-11 15:25:34 3740 [Note] InnoDB: Database was not shutdown normally!
2013-10-11 15:25:34 3740 [Note] InnoDB: Starting crash recovery.
2013-10-11 15:25:34 3740 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-11 15:25:34 3740 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace yesautohandel/wp_terms which uses space ID: 3 at filepath: .\yesautohandel\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\yesautohandel\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2013-10-11 15:25:40 2664 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 15:25:40 408 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-10-11 15:25:40 2664 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 15:25:40 2664 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 15:25:40 2664 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 15:25:40 2664 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 15:25:40 2664 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 15:25:40 2664 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 15:25:40 2664 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-11 15:25:41 2664 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2524657 in the ib_logfiles!
2013-10-11 15:25:41 2664 [Note] InnoDB: Database was not shutdown normally!
2013-10-11 15:25:41 2664 [Note] InnoDB: Starting crash recovery.
2013-10-11 15:25:41 2664 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-11 15:25:41 2664 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace yesautohandel/wp_terms which uses space ID: 3 at filepath: .\yesautohandel\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\yesautohandel\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2013-10-11 15:28:14 4212 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 15:28:14 1078 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-10-11 15:28:14 4212 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 15:28:14 4212 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 15:28:14 4212 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 15:28:14 4212 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 15:28:14 4212 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 15:28:14 4212 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 15:28:14 4212 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-11 15:28:14 4212 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2524657 in the ib_logfiles!
2013-10-11 15:28:14 4212 [Note] InnoDB: Database was not shutdown normally!
2013-10-11 15:28:14 4212 [Note] InnoDB: Starting crash recovery.
2013-10-11 15:28:14 4212 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-11 15:28:14 4212 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace yesautohandel/wp_terms which uses space ID: 3 at filepath: .\yesautohandel\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\yesautohandel\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2013-10-11 15:28:21 4368 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 15:28:21 1114 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-10-11 15:28:21 4368 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 15:28:21 4368 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 15:28:21 4368 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 15:28:21 4368 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 15:28:21 4368 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 15:28:21 4368 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 15:28:21 4368 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-11 15:28:21 4368 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2524657 in the ib_logfiles!
2013-10-11 15:28:21 4368 [Note] InnoDB: Database was not shutdown normally!
2013-10-11 15:28:21 4368 [Note] InnoDB: Starting crash recovery.
2013-10-11 15:28:21 4368 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-11 15:28:21 4368 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace yesautohandel/wp_terms which uses space ID: 3 at filepath: .\yesautohandel\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\yesautohandel\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
by MisterMoma
11. October 2013 14:32
 
Forum: XAMPP für Windows
Topic: MYSQL startet nicht mehr
Replies: 1
Views: 1740

Error: MySQL shutdown unexpectedly.

i have installed before 1 year in my c drive xampp 1.7.1 and my 35 projects running through 1.7.1. after that i need xampp 1.8.2 and i just download from appache site the folder not installer version and stop my c drive xampp and place 1.8.2 to d drive and then start control panel when i start apache it starts but when start mysql error is
Error: MySQL shutdown unexpectedly.
This may be due to a blocked port, missing dependencies,
improper privileges, a crash, or a shutdown by another method.
Press the Logs button to view error logs and check
the Windows Event Viewer for more clues
If you need more help, copy and post this
entire log window on the forums

and the log is as follow

http://www.mediafire.com/download/2eo537umqc727fj/log.txt
by waleedehsan1
11. October 2013 05:21
 
Forum: MariaDB - MySQL
Topic: Error: MySQL shutdown unexpectedly.
Replies: 1
Views: 2902

Re: Issue start mysql even changed port number to 3307

You have installed MySQL 5.0 as single component and registered as windows service.
XAMPP control panel can not separate this service from it's own applications.
So if you want to use the XAMPP MySQL with a different port, you need to specify the port and a new service name for MySQL both in the control panel configs too.
by Altrea
10. October 2013 09:48
 
Forum: XAMPP for Windows
Topic: Issue start mysql even changed port number to 3307
Replies: 3
Views: 2466

Re: Issue start mysql even changed port number to 3307

In control panel it said:
Code: Select all
MySQL Service detected with wrong path
3:33:40 PM  [mysql]    Change XAMPP MySQL and Control Panel settings or
3:33:40 PM  [mysql]    Uninstall/disable the other service manually first
3:33:40 PM  [mysql]    Found Path: "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 5.0\my.ini" MySQL
3:33:40 PM  [mysql]    Expected Path: c:\xampp\mysql\bin\mysqld.exe --defaults-file=c:\xampp\mysql\bin\my.ini mysql

in log file:
Code: Select all
130928  9:12:34 [Note] Plugin 'FEDERATED' is disabled.
130928  9:12:43 InnoDB: The InnoDB memory heap is disabled
130928  9:12:43 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130928  9:12:43 InnoDB: Compressed tables use zlib 1.2.3
130928  9:12:48 InnoDB: Initializing buffer pool, size = 16.0M
130928  9:12:48 InnoDB: Completed initialization of buffer pool
130928  9:13:10 InnoDB: highest supported file format is Barracuda.
130928  9:13:41  InnoDB: Waiting for the background threads to start
130928  9:13:42 InnoDB: 5.5.32 started; log sequence number 9367709
130928  9:13:42 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130928  9:13:42 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
130928  9:13:42 [Note] Server socket created on IP: '0.0.0.0'.
130928  9:13:45 [Note] Event Scheduler: Loaded 0 events
130928  9:13:45 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.32'  socket: ''  port: 3306  MySQL Community Server (GPL)
130929  0:19:44 [Note] c:\xampp\mysql\bin\mysqld.exe: Normal shutdown

130929  0:19:46 [Note] Event Scheduler: Purging the queue. 0 events
130929  0:19:49  InnoDB: Starting shutdown...
130929  0:20:03  InnoDB: Shutdown completed; log sequence number 9367709
130929  0:20:05 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

130929 12:03:01 [Note] Plugin 'FEDERATED' is disabled.
130929 12:03:04 InnoDB: The InnoDB memory heap is disabled
130929 12:03:04 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130929 12:03:04 InnoDB: Compressed tables use zlib 1.2.3
130929 12:03:06 InnoDB: Initializing buffer pool, size = 16.0M
130929 12:03:06 InnoDB: Completed initialization of buffer pool
130929 12:03:07 InnoDB: highest supported file format is Barracuda.
130929 12:03:26  InnoDB: Waiting for the background threads to start
130929 12:03:27 InnoDB: 5.5.32 started; log sequence number 9367709
130929 12:03:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130929 12:03:27 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
130929 12:03:27 [Note] Server socket created on IP: '0.0.0.0'.
130929 12:03:28 [Note] Event Scheduler: Loaded 0 events
130929 12:03:28 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.32'  socket: ''  port: 3306  MySQL Community Server (GPL)
130929 14:55:43 [Note] c:\xampp\mysql\bin\mysqld.exe: Normal shutdown

130929 14:55:46 [Note] Event Scheduler: Purging the queue. 0 events
130929 14:55:51  InnoDB: Starting shutdown...
130929 14:56:08  InnoDB: Shutdown completed; log sequence number 9367709
130929 14:56:10 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

I'm using win7, the lastest xampp
by luckylam
10. October 2013 09:36
 
Forum: XAMPP for Windows
Topic: Issue start mysql even changed port number to 3307
Replies: 3
Views: 2466

Re: Issue start mysql even changed port number to 3307

How should we know that without any information?
Why do you think it is not working?
What is the response of the relating log files?
by Altrea
10. October 2013 05:43
 
Forum: XAMPP for Windows
Topic: Issue start mysql even changed port number to 3307
Replies: 3
Views: 2466

Issue start mysql even changed port number to 3307

HI guys I need your help...
I have two mysql installing, one has port 3306...
Now I change mysql xampp to 3307, I have ALREADY configured in my.ini file but it seems not working at all. What's the problem?
Any help would be appreciated!
Code: Select all
# password       = your_password
port            = 3307
socket          = "C:/xampp/mysql/mysql.sock"


# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3307
socket = "C:/xampp/mysql/mysql.sock"
basedir = "C:/xampp/mysql"
tmpdir = "C:/xampp/tmp"
datadir = "C:/xampp/mysql/data"
pid_file = "mysql.pid"
# enable-named-pipe
key_buffer = 16M
max_allowed_packet = 1M
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
log_error = "mysql_error.log"
by luckylam
10. October 2013 05:04
 
Forum: XAMPP for Windows
Topic: Issue start mysql even changed port number to 3307
Replies: 3
Views: 2466

Re: Cannot start MySQL, need help

Thanks, Nobbie!
Works like a charm!

As many people are having similar issues, maybe this threat and/or your solution should move to a place where most people looking for help will see it?

This threat is closed, ty.
by HansenDesign
09. October 2013 16:45
 
Forum: MariaDB - MySQL
Topic: Cannot start MySQL, need help
Replies: 7
Views: 11659

Re: Cannot start MySQL, need help

From http://bugs.mysql.com/bug.php?id=67595

[27 Nov 2012 8:39] Sunny Bains

This is a duplicate of bug#67179. Just different side effect. The Windows installer apparently copied the .ibd files around and that caused the problem. The ones in data/mysql. If you want to recover your files you will have to do the following:

1. Delete the data/mysql/*.ibd files and the corresponding .frm files for the .ibd files
2. Start the server with --skip-slave-start
3. You should be able to access and backup your data


Do not delete ibdata1 (from data folder), but data/mysql/*.idb etc. (see Item "1." above).
by Nobbie
09. October 2013 16:30
 
Forum: MariaDB - MySQL
Topic: Cannot start MySQL, need help
Replies: 7
Views: 11659

Cannot start MySQL, need help

Hello,
I am running Win Vista Ultimate 32bit.
XAMPP 1.8.3-1
Apache 2.4.4
MySQL 5.6.11
PHP 5.5.3

Error log shows:
Code: Select all
2013-10-09 15:43:30 6572 [Note] Plugin 'FEDERATED' is disabled.
2013-10-09 15:43:30 f30 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-10-09 15:43:30 6572 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-09 15:43:30 6572 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-09 15:43:30 6572 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-09 15:43:30 6572 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-09 15:43:30 6572 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-09 15:43:30 6572 [Note] InnoDB: Completed initialization of buffer pool
2013-10-09 15:43:30 6572 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-09 15:43:30 6572 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2934894 in the ib_logfiles!
2013-10-09 15:43:30 6572 [Note] InnoDB: Database was not shutdown normally!
2013-10-09 15:43:30 6572 [Note] InnoDB: Starting crash recovery.
2013-10-09 15:43:30 6572 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-09 15:43:30 6572 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress_johann/wp_terms which uses space ID: 3 at filepath: .\wordpress_johann\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress_johann\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.


Using it to test Wordpress-sites.
I do not want to have to reinstall Wordpress or MySQL, so deleting ibdata1 is no solution for me.

Anything I can do?

EDIT: Would it help, and if yes, how, to install XAMPP 1.8.2-1 like described here http://community.apachefriends.org/f/viewtopic.php?f=16&t=60831#p227718 ?
by HansenDesign
09. October 2013 14:54
 
Forum: MariaDB - MySQL
Topic: Cannot start MySQL, need help
Replies: 7
Views: 11659

Re: #1045 Cannot log in to the MySQL server

Neilbritto wrote:3 I at points I have modified my config.inc.php file, changing the password, but with no real different
outcome.

Code: Select all
$cfg['Servers'][$i]['auth_type']     = 'cookie';      // Authentication method (config, http or cookie based)
$cfg['Servers'][$i]['user'] = 'root';
$cfg['Servers'][$i]['password'] = 'hello';
$cfg['Servers'][$i]['extension'] = 'mysqli';
$cfg['Servers'][$i]['AllowNoPassword'] = true;
$cfg['Lang'] = '';


This is useless, as for auth_type 'cookie' the above values are NOT evaluated against MySQL (and als NOT evaluated against the values you enter in the login dialog), instead the values you provide in the login dialog are evaluated against MySQL. Only for auth_type 'config' (neither for 'cookie' nor for 'http') the user and password values from the config.php.inc are taken for login into MySQL (due to the fact, that there is no login dialog for auth_type 'config'). Anyway, you supplied "hello" instead of "1234" as password. It is very confusing what you are doing there.

Neilbritto wrote:I've heard it mentioned that there are two root accounts.


No and yes. There are not two root accounts in MySQL, but on Linux Operating System the system administrator (same as "Administrator" in Windows Environments) is called "root" as well. But this is a completely different context and you cannot compare a Linux User with a MySQL User.

Neilbritto wrote:Can anyone explain or point to the most succinct sources on how I am to start up using the database using these accounts


Unfortunatey, it is the worst thing you can do to forget the "root" password of MySQL. There are some reset procedures devilered with Xampp, but these have been faulty for many years (i dont know the current status). You *should* have a backup of your data and i would recommend to do a full de-install and new install of MySQL and finalley restore the backup.

P.S.:

Code: Select all
mysqladmin -u root password 1234


This is wrong syntax anyway, i think it must be

mysqladmin -u root -p 1234

or

mysqladmin --user root --password 1234

instead. See the manual (man mysqladmin) if in doubt. Same for the "mysql" client.
by Nobbie
09. October 2013 13:21
 
Forum: MariaDB - MySQL
Topic: #1045 Cannot log in to the MySQL server
Replies: 1
Views: 6661

Re: 1.8.2 Mysql & Apache can't start anymore

Well, on the /root directory i have Windows 8 instalation files, so as you can see, the addition of such functionality, even in the form as option, would be really appropriate .. :wink:

Also, i check this twice, my drive litter still stay the same, and server wont't run.
After (refresh) work'd again.
by afxmpp
08. October 2013 20:07
 
Forum: XAMPP for Windows
Topic: 1.8.2 Mysql & Apache can't start anymore
Replies: 8
Views: 5558

Re: 1.8.2 Mysql & Apache can't start anymore

No, because that is not needed.

If you want to have a portable XAMPP version on your USB drive extract XAMPP to the root directory of your USB drive (so that you will have at the end a xampp folder on the root directory) and don't (NEVER!) use the setup_xampp.bat script.
XAMPP is shipped by default without drive letter mapping and configured to work from a root directory installation. Restriction: you can't use Windows services without drive letter mapping, but that is for sure a very uncommon use case for portable installations.
by Altrea
08. October 2013 17:56
 
Forum: XAMPP for Windows
Topic: 1.8.2 Mysql & Apache can't start anymore
Replies: 8
Views: 5558

Re: 1.8.2 Mysql & Apache can't start anymore

Is it possible, to add functionality with new version, by inspection from the Xampp Control Panel, which drive letter is used to run server ?
And automatic correction of the configuration file, if you fire'd up server from different device letter ?

It would be a great facilitation .. 8)
by afxmpp
08. October 2013 17:45
 
Forum: XAMPP for Windows
Topic: 1.8.2 Mysql & Apache can't start anymore
Replies: 8
Views: 5558

Re: 1.8.2 Mysql & Apache can't start anymore

Depending on the user context the application is running (Windows Service, elevated Administrator, user, etc) a drive letter can be available or not.
by Altrea
08. October 2013 05:51
 
Forum: XAMPP for Windows
Topic: 1.8.2 Mysql & Apache can't start anymore
Replies: 8
Views: 5558
PreviousNext

Return to advanced search