Xampp v - Error 2002 "Error establishing db con-tion

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Xampp v - Error 2002 "Error establishing db con-tion

Postby Blabloger » 12. August 2013 16:49

Hi, all. Yesterday I set up my xampp and wordpress and started creating a blog. Everything was fine. Today - I can't login to localhost/wordpress. When I go there, it says "Error establishing a database connection". When I go to localhost/wordpress/wp-admin ,

it says:

" This either means that the username and password information in your wp-config.php file is incorrect or we can't contact the database server at localhost. This could mean your host's database server is down.

Are you sure you have the correct username and password?
Are you sure that you have typed the correct hostname?
Are you sure that the database server is running?

If you're unsure what these terms mean you should probably contact your host. If you still need help you can always visit the WordPress Support Forums.

When I go to localhost/phpmyadmin , it says:

#2002 - No connection could be made because the target machine actively refused it.

So what do I do? Any insight? I am very non-technical non-coding person so I hope there is some understandable solution. Thank you, guys, in advance!
Posts: 2
Joined: 12. August 2013 16:41
Operating System: Windows 7

Re: Xampp v - Error 2002 "Error establishing db con-

Postby Blabloger » 12. August 2013 20:21

This is what it says in the Mysql Log:

2013-08-12 18:31:50 4000 [Note] Plugin 'FEDERATED' is disabled.
2013-08-12 18:31:51 d2c 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-12 18:31:51 4000 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-12 18:31:51 4000 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-12 18:31:51 4000 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-12 18:31:51 4000 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-12 18:31:51 4000 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-12 18:31:51 4000 [Note] InnoDB: Completed initialization of buffer pool
2013-08-12 18:31:51 4000 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-12 18:31:51 4000 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3298033 in the ib_logfiles!
2013-08-12 18:31:51 4000 [Note] InnoDB: Database was not shutdown normally!
2013-08-12 18:31:51 4000 [Note] InnoDB: Starting crash recovery.
2013-08-12 18:31:51 4000 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-12 18:31:52 4000 [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 mywordpress/wp_terms which uses space ID: 3 at filepath: .\mywordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\mywordpress\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.
Posts: 2
Joined: 12. August 2013 16:41
Operating System: Windows 7

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 91 guests