Problem with XAMPP 1.7.2 Beta...

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

Problem with XAMPP 1.7.2 Beta...

Postby BliND123 » 16. July 2009 18:50

Well, was working great last night after installing it but this morning I try to start Apache and Mysql but Apache gives me this "WARNING: terminating worker thread 0". I know this is a beta but I am using it for Ampache which needs PHP 5.3. Now, I was thinking of uninstalling it to reinstall but I couldn't find an uninstall for this beta in Control Panel or in the XAMPP folder itself. Anyone know how to fix it or how to uninstall it to reinstall?
Last edited by BliND123 on 16. July 2009 20:37, edited 1 time in total.
BliND123
 
Posts: 4
Joined: 16. July 2009 18:43

Re: Problem with XAMPP 1.7.2 Beta...

Postby Wiedmann » 16. July 2009 20:11

Ampache gives me this "WARNING: terminating worker thread 0".

What is "Ampache"?

Maybe you can ask the author of "Ampache" the meaning of this warning?

Anyone know how to fix it

Sorry. Don't know anything about "Ampache".

BTW:
Is a normal installation without "Ampache" working. (Using the normal batchfiles or the control panel?)

or how to uninstall it to reinstall?

Delete the xampp folder (and the startmenu entries).
Wiedmann
AF Moderator
 
Posts: 17106
Joined: 01. February 2004 12:38
Location: Stuttgart / Germany

Re: Problem with XAMPP 1.7.2 Beta...

Postby BliND123 » 16. July 2009 20:36

Oh sorry, Ampache isn't giving me that warning, its XAMPP when I try to start Apache. I edited my above post to what I meant to say. LOL And I used the XAMPP 1.7.2 Beta installer, so is deleting the folder enough even if I reinstall it to a different directory?
BliND123
 
Posts: 4
Joined: 16. July 2009 18:43

Re: Problem with XAMPP 1.7.2 Beta...

Postby Wiedmann » 16. July 2009 20:40

its XAMPP when I try to start Apache.

Something in Apaches' "error.log"?

so is deleting the folder enough even if I reinstall it to a different directory?

Sure.

(If you have installed the Windows services, remove them first)
Wiedmann
AF Moderator
 
Posts: 17106
Joined: 01. February 2004 12:38
Location: Stuttgart / Germany

Re: Problem with XAMPP 1.7.2 Beta...

Postby BliND123 » 16. July 2009 21:18

Ok, this is what the Apache error.log is showing:
Code: Select all
[Thu May 07 23:43:01 2009] [notice] Digest: generating secret for digest authentication ...
[Thu May 07 23:43:01 2009] [notice] Digest: done
[Thu May 07 23:43:07 2009] [notice] Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8k mod_autoindex_color PHP/5.2.9 mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations
[Thu May 07 23:43:07 2009] [notice] Server built: Mar  8 2009 00:30:48
[Thu May 07 23:43:07 2009] [notice] Parent: Created child process 4720
[Thu May 07 23:43:10 2009] [notice] Digest: generating secret for digest authentication ...
[Thu May 07 23:43:10 2009] [notice] Digest: done
[Thu May 07 23:43:14 2009] [notice] Child 4720: Child process is running
[Thu May 07 23:43:14 2009] [notice] Child 4720: Acquired the start mutex.
[Thu May 07 23:43:14 2009] [notice] Child 4720: Starting 150 worker threads.
[Thu May 07 23:43:14 2009] [notice] Child 4720: Starting thread to listen on port 443.
[Thu May 07 23:43:14 2009] [notice] Child 4720: Starting thread to listen on port 443.
[Thu May 07 23:43:14 2009] [notice] Child 4720: Starting thread to listen on port 80.
[Thu May 07 23:43:14 2009] [notice] Child 4720: Starting thread to listen on port 80.
[Thu May 07 23:43:14 2009] [error] [client ::1] script 'C:/xampp/htdocs/test1.php' not found or unable to stat
[Thu May 07 23:43:14 2009] [error] [client ::1] File does not exist: C:/xampp/htdocs/favicon.ico
[Thu May 07 23:43:17 2009] [error] [client ::1] File does not exist: C:/xampp/htdocs/favicon.ico
[Thu May 07 23:43:28 2009] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu May 07 23:43:28 2009] [notice] Child 4720: Exit event signaled. Child process is ending.
[Thu May 07 23:43:29 2009] [notice] Child 4720: Released the start mutex
[Thu May 07 23:43:30 2009] [notice] Child 4720: All worker threads have exited.
[Thu May 07 23:43:30 2009] [notice] Child 4720: Child process is exiting
[Thu May 07 23:43:30 2009] [notice] Parent: Child process exited successfully.
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  : make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  : make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  : make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  : make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  : make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs


Like I said, it was working perfectly last night, I didn't change anything to it this morning and now its doing that.

Edit: Actually I turned UAC off and on, but I don't think that should have anything to do with this problem, should it?
BliND123
 
Posts: 4
Joined: 16. July 2009 18:43

Re: Problem with XAMPP 1.7.2 Beta...

Postby Wiedmann » 16. July 2009 21:43

(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:443

There is already a server/program runnimg which is using the Apache port. Stop this one and you can start Apache.
Wiedmann
AF Moderator
 
Posts: 17106
Joined: 01. February 2004 12:38
Location: Stuttgart / Germany

Re: Problem with XAMPP 1.7.2 Beta...

Postby BliND123 » 16. July 2009 21:50

I tried some yesterday but they all sucked compared to XAMPP so they were quickly uninstalled. I guess some traces were left cause I just did a registry cleanup with CCleaner and starting Apache from XAMPP works perfectly again.
BliND123
 
Posts: 4
Joined: 16. July 2009 18:43

Re: Problem with XAMPP 1.7.2 Beta...

Postby AG007 » 16. August 2009 10:31

I got the same problem.. what do i need to do?
Here is my error.log file:
Code: Select all
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Normalt må en socket-adresse (protokol/netværksadresse/port) kun bruges én gang.  : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

Do i need to close something? a program?
If "Yes" then what is the program called :S cuz when i click CTRL+ALT+DELETE and go to processer i didnt see any server or program called apache or something like that >.<
AG007
 
Posts: 1
Joined: 16. August 2009 10:24

Re: Problem with XAMPP 1.7.2 Beta...

Postby Wiedmann » 16. August 2009 10:48

Do i need to close something? a program?

Correct. As you can read in the error log, an other program is already using port 80.

If "Yes" then what is the program called

It's your pc. How can we know what programs you have installed and running?

i didnt see any server or program called apache or something like that

Maybe it's better to as the system which program is using which port (e.g. netstat, tcpview), instead of looking through the tasklist (without knowing what each program is doing and how it works).
Wiedmann
AF Moderator
 
Posts: 17106
Joined: 01. February 2004 12:38
Location: Stuttgart / Germany

Re: Problem with XAMPP 1.7.2 Beta...

Postby ahmedelhamahmy » 08. October 2009 10:21

Dear I had the same problem, everything was running perfectly untill I run Skype,
I went with the Port Check from the main Menu of XAMPP
Image
Image
and I found that port 80, and port 443 was written used by SYSTEM and not Free in thier Statues Coulmn.

I closed skype and all messengers programs and then tried again and everything went just fine, then I re loaded Skype again after be sure that the Appache is running.

Do the same and I think it will work just fine with you.

Best regards
Image
ahmedelhamahmy
 
Posts: 1
Joined: 08. October 2009 10:13

Re: Problem with XAMPP 1.7.2 Beta...

Postby haydar.cicekci » 10. April 2010 22:56

I found that port 80, and port 443 was written used by SYSTEM and not Free in thier Statues Coulmn.


Hi, I had the same problem, The port 80 was written used by sytem and I can not find how can i change it? Please help...
haydar.cicekci
 
Posts: 1
Joined: 10. April 2010 22:36

Re: Problem with XAMPP 1.7.2 Beta...

Postby Narrowboyy » 11. April 2010 01:31

haydar.cicekci wrote:
I found that port 80, and port 443 was written used by SYSTEM and not Free in thier Statues Coulmn.


Hi, I had the same problem, The port 80 was written used by sytem and I can not find how can i change it? Please help...
This is an old topic, so what Windows version are you using?

Are you logged in to your Windows as an Administrator to be able to administrate the XAMPP web servers?

See this topic for a possible solution to System on port 80:
viewtopic.php?f=16&t=40062

Also if using another server like Skype etc. have it/them use another port that XAMPP does not require exclusively.
Narrowboyy
 
Posts: 64
Joined: 16. February 2009 02:56

Re: Problem with XAMPP 1.7.2 Beta...

Postby masheen_17 » 23. April 2010 21:56

click the button on the xampp control panel "check ports",
this will show you whats running through port 80, the same port that apache uses by default.
i had skype running through port 80 as soon as i quit skype apache ran normally.
masheen_17
 
Posts: 1
Joined: 23. April 2010 21:51

Re: Problem with XAMPP 1.7.2 Beta...

Postby al! » 27. September 2010 01:00

turn skype off)
al!
 
Posts: 3
Joined: 08. April 2009 00:28


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 67 guests