I have installed these before but needed to upgrade to php 5.4.1. However, I had problems so re-installed MySQL 5.5.28 (64 bit version) [the Apache server was already installed in c:\apache and working and the service was starting automatically).
This installed (in c:\MySQL) okay and the service started okay on rebooting the system (with my.ini in the root folder).
I then installed php 5.4.1 into c:\php.
I copied the php.ini-development file to c:\windows and renamed it php.ini and added the following lines to php.ini
Can anyone please shed any light on where I have made a mistake. As I said, I have installed these previously with no (well little!!!) problems.
Okay - found my mistake....apologies. I had entered my password on MySQL incorrectly. However, when going back to square one and re-installing everything, I have fallen at the first hurdle. On installing Apache 2.2 the system reports that it has installed correctly but the pop-up dos box states....
httpd.exe: Could not reliably determine the server's fully qualified domain name
, using 192.168.1.103 for ServerName
(OS 10013)An attempt was made to access a socket in a way forbidden by its acces
s permissions. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs.
Of course the Apache Service will not start but I don't understand the error message or what I need to do to resolve the situation. Can anyone help please?
Unless its a major change, you can typically get away with just updating a specific component of the apache/mysql/php chain. The only thing I see as "kinda" wrong, is that doc_root isn't really required when you're building a module for the PHP.
The second error I wouldn't worry about the first part. It's simply detecting no valid domain and reverting to an IP address. 192.168/16 is an internal subnet. If it actually configures against that, you may need to remove it if your machine is DHCP (which it could very well be). I wouldn't think that its stupid enough to bind an ip address though, so that would probably toss that quite regularly. I'd assume it should cause no real problems otherwise.
The second one is your problem. It cannot establish a socket on port 80 to listen to. Either there is already something listening on port 80 (quite a number of applications do by default) or you have a firewall tool blocking your connection attempt. Check your netstat -abo and look for the :80 in use. You can also use the netstat -ao | find ":80 ", and take the associated pid and check the tasklist for the associated program.
|All times are GMT +1. The time now is 12:19 PM.|
Powered by vBulletin®
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.