Apache-Start Problem (XAMPP 1.8.2)

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

Apache-Start Problem (XAMPP 1.8.2)

Postby was955 » 22. August 2013 16:00

iam having same thing

skype is not the problem it is using 41643

apache_start returns:

port Diese Eingabeforderung nicht waehrend des Running beenden
Bitte erst bei einem gewollten Shutdown schliessen
Please close this command only for Shutdown
Apache 2 is starting ...
(OS 10048)Only one usage of each socket address (protocol/network address/port)
is normally permitted. : AH00072: make_sock: could not bind to address [::]:808
(OS 10048)Only one usage of each socket address (protocol/network address/port)
is normally permitted. : AH00072: make_sock: could not bind to address
AH00451: no listening sockets available, shutting down
AH00015: Unable to open logs

Apache konnte nicht gestartet werden
Apache could not be started
Press any key to continue . . .

and the sql log shows:

2013-08-22 17:52:44 9172 [Note] Plugin 'FEDERATED' is disabled.
2013-08-22 17:52:44 2598 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-22 17:52:44 9172 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-22 17:52:44 9172 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-22 17:52:44 9172 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-22 17:52:44 9172 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-22 17:52:44 9172 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-22 17:52:44 9172 [Note] InnoDB: Completed initialization of buffer pool
2013-08-22 17:52:44 9172 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-22 17:52:44 9172 [Warning] InnoDB: The log sequence number in the ibdata files is higher than the log sequence number in the ib_logfiles! Are you sure you are using the right ib_logfiles to start up the database. Log sequence number in the ib_logfiles is 1600614, logsequence numbers stamped to ibdata file headers are between 10390440 and 10390440.
2013-08-22 17:52:44 9172 [Note] InnoDB: The log sequence numbers 10390440 and 10390440 in ibdata files do not match the log sequence number 1600614 in the ib_logfiles!
2013-08-22 17:52:44 9172 [Note] InnoDB: Database was not shutdown normally!
2013-08-22 17:52:44 9172 [Note] InnoDB: Starting crash recovery.
2013-08-22 17:52:44 9172 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-22 17:52:44 9172 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace drupal/field_revision_commerce_free_shipping uses space ID: 729 at filepath: .\drupal\field_revision_commerce_free_shipping.ibd. Cannot open tablespace worden/wp_layerslider which uses space ID: 729 at filepath: .\worden\wp_layerslider.ibd
InnoDB: Error: could not open single-table tablespace file .\worden\wp_layerslider.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: 3
Joined: 04. August 2013 03:29
Operating System: windows 7 64bit enterprise

Re: Apache-Start Problem (XAMPP 1.8.2)

Postby Altrea » 22. August 2013 16:17


was955 wrote:iam having same thing

Why do you think you are having the same thing? Do you think "Apache don't starts" is an issue with a single reason?
You did reconfigure Apache to use port 8081, the original author not.
You have a problem with MySQL too, the original author not.

Btw this MySQL issue in relation to XAMPP is since today just known for XAMPP version 1.8.3, not 1.8.2. So are you really sure you are using XAMPP 1.8.2? Please double check this.

Your problem is that port 8081 wasn't free at the time apache tries to capture it.

Best wishes,
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
AF Moderator
Posts: 9365
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 43 guests