Error: MySQL shutdown unexpectedly.

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

Error: MySQL shutdown unexpectedly.

Postby Aqueeb » 19. August 2013 06:15

Error Log:


2013-08-19 08:05:58 4168 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 08:05:58 288 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-19 08:05:58 4168 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 08:05:58 4168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 08:05:58 4168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 08:05:58 4168 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 08:05:58 4168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 08:05:58 4168 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 08:05:58 4168 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-08-19 08:05:58 4168 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-08-19 08:05:58 4168 [Note] InnoDB: Database physically writes the file full: wait...
2013-08-19 08:05:59 4168 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-08-19 08:05:59 4168 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-08-19 08:06:01 4168 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-08-19 08:06:01 4168 [Warning] InnoDB: New log files created, LSN=45781
2013-08-19 08:06:01 4168 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-08-19 08:06:01 4168 [Note] InnoDB: Doublewrite buffer created
2013-08-19 08:06:02 4168 [Note] InnoDB: 128 rollback segment(s) are active.
2013-08-19 08:06:02 4168 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-08-19 08:06:02 4168 [Note] InnoDB: Foreign key constraint system tables created
2013-08-19 08:06:02 4168 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-08-19 08:06:02 4168 [Note] InnoDB: Tablespace and datafile system tables created.
2013-08-19 08:06:02 4168 [Note] InnoDB: Waiting for purge to start
2013-08-19 08:06:02 4168 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-08-19 08:06:03 4168 [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: 177a9295-0878-11e3-ba15-74867a0ebc7e.
2013-08-19 08:06:03 4168 [Note] Server hostname (bind-address): '*'; port: 3306
2013-08-19 08:06:03 4168 [Note] IPv6 is available.
2013-08-19 08:06:03 4168 [Note] - '::' resolves to '::';
2013-08-19 08:06:03 4168 [Note] Server socket created on IP: '::'.
2013-08-19 10:14:44 6724 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 10:14:44 1acc 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-19 10:14:44 6724 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 10:14:44 6724 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 10:14:44 6724 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 10:14:44 6724 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 10:14:44 6724 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 10:14:44 6724 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 10:14:44 6724 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-19 10:14:44 6724 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1613645 in the ib_logfiles!
2013-08-19 10:14:44 6724 [Note] InnoDB: Database was not shutdown normally!
2013-08-19 10:14:44 6724 [Note] InnoDB: Starting crash recovery.
2013-08-19 10:14:44 6724 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-19 10:14:44 6724 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lr/users uses space ID: 2 at filepath: .\lr\users.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-08-19 10:20:31 6500 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 10:20:31 1968 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-19 10:20:31 6500 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 10:20:31 6500 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 10:20:31 6500 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 10:20:31 6500 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 10:20:31 6500 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 10:20:31 6500 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 10:20:31 6500 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-19 10:20:31 6500 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1613645 in the ib_logfiles!
2013-08-19 10:20:31 6500 [Note] InnoDB: Database was not shutdown normally!
2013-08-19 10:20:31 6500 [Note] InnoDB: Starting crash recovery.
2013-08-19 10:20:31 6500 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-19 10:20:31 6500 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lr/users uses space ID: 2 at filepath: .\lr\users.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-08-19 10:32:08 2452 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 10:32:08 17e0 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-19 10:32:08 2452 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 10:32:08 2452 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 10:32:08 2452 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 10:32:08 2452 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 10:32:08 2452 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 10:32:08 2452 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 10:32:08 2452 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-19 10:32:08 2452 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1613645 in the ib_logfiles!
2013-08-19 10:32:08 2452 [Note] InnoDB: Database was not shutdown normally!
2013-08-19 10:32:08 2452 [Note] InnoDB: Starting crash recovery.
2013-08-19 10:32:08 2452 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-19 10:32:08 2452 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lr/users uses space ID: 2 at filepath: .\lr\users.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-08-19 10:32:09 6860 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 10:32:09 1490 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-19 10:32:09 6860 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 10:32:09 6860 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 10:32:09 6860 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 10:32:09 6860 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 10:32:09 6860 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 10:32:09 6860 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 10:32:09 6860 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-19 10:32:09 6860 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1613645 in the ib_logfiles!
2013-08-19 10:32:09 6860 [Note] InnoDB: Database was not shutdown normally!
2013-08-19 10:32:09 6860 [Note] InnoDB: Starting crash recovery.
2013-08-19 10:32:09 6860 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-19 10:32:09 6860 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lr/users uses space ID: 2 at filepath: .\lr\users.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-08-19 10:32:10 4280 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 10:32:10 1bdc 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-19 10:32:10 4280 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 10:32:10 4280 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 10:32:10 4280 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 10:32:10 4280 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 10:32:10 4280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 10:32:10 4280 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 10:32:10 4280 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-19 10:32:10 4280 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1613645 in the ib_logfiles!
2013-08-19 10:32:10 4280 [Note] InnoDB: Database was not shutdown normally!
2013-08-19 10:32:10 4280 [Note] InnoDB: Starting crash recovery.
2013-08-19 10:32:10 4280 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-19 10:32:10 4280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lr/users uses space ID: 2 at filepath: .\lr\users.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-08-19 10:33:33 5704 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 10:33:33 12d8 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-19 10:33:33 5704 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 10:33:33 5704 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 10:33:33 5704 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 10:33:33 5704 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 10:33:33 5704 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 10:33:33 5704 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 10:33:33 5704 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-19 10:33:33 5704 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1613645 in the ib_logfiles!
2013-08-19 10:33:33 5704 [Note] InnoDB: Database was not shutdown normally!
2013-08-19 10:33:33 5704 [Note] InnoDB: Starting crash recovery.
2013-08-19 10:33:33 5704 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-19 10:33:33 5704 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lr/users uses space ID: 2 at filepath: .\lr\users.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-08-19 10:33:40 6428 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 10:33:40 1b44 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-19 10:33:40 6428 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 10:33:40 6428 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 10:33:40 6428 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 10:33:40 6428 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 10:33:40 6428 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 10:33:40 6428 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 10:33:40 6428 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-19 10:33:40 6428 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1613645 in the ib_logfiles!
2013-08-19 10:33:40 6428 [Note] InnoDB: Database was not shutdown normally!
2013-08-19 10:33:40 6428 [Note] InnoDB: Starting crash recovery.
2013-08-19 10:33:40 6428 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-19 10:33:40 6428 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lr/users uses space ID: 2 at filepath: .\lr\users.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-08-19 10:33:46 6160 [Note] Plugin 'FEDERATED' is disabled.
2013-08-19 10:33:46 14e0 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-19 10:33:46 6160 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-19 10:33:46 6160 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-19 10:33:46 6160 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-19 10:33:46 6160 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-19 10:33:46 6160 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-19 10:33:46 6160 [Note] InnoDB: Completed initialization of buffer pool
2013-08-19 10:33:46 6160 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-19 10:33:46 6160 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1613645 in the ib_logfiles!
2013-08-19 10:33:46 6160 [Note] InnoDB: Database was not shutdown normally!
2013-08-19 10:33:46 6160 [Note] InnoDB: Starting crash recovery.
2013-08-19 10:33:46 6160 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-19 10:33:47 6160 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lr/users uses space ID: 2 at filepath: .\lr\users.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
Aqueeb
 
Posts: 2
Joined: 19. August 2013 06:09
XAMPP Version: 5.5.19
Operating System: win 8

Re: Error: MySQL shutdown unexpectedly.

Postby Aqueeb » 19. August 2013 06:16

What should I do? Please help.
Aqueeb
 
Posts: 2
Joined: 19. August 2013 06:09
XAMPP Version: 5.5.19
Operating System: win 8


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 35 guests