Richard Bowser Posted February 8, 2009 Share Posted February 8, 2009 I - and a friend - just installed WampServer 2.0f.exe, me on XP Pro SP3, and him on Vista Home Premium. BOTH of us were greeted by "Wamp Server Offline" and cannot run phpMyAdmin. I had just uninstalled Wampserver2.0c in order to upgrade, and he had never run WAMP of any flavor before. (My WampServer2.0c had run flawlessly.) Can anybody suggest where to look to see why we are hitting this stone wall? Neither of us got any errors or warnings. I am confused. Richard Bowser Quote Link to comment Share on other sites More sharing options...
corbin Posted February 8, 2009 Share Posted February 8, 2009 So WAMP isn't run or it won't run? What's in error.log? (Look around for the Apache folder and then find it.) Quote Link to comment Share on other sites More sharing options...
wildteen88 Posted February 8, 2009 Share Posted February 8, 2009 When wamp is running in Offline mode it means it'll only accept connections from the ip address 127.0.0.1 (which is what localhost resolves to). To allow connections from any ip address left click the WAMP tray icon and select Put Online If the icon is white then there are no problems. if its yellow then it means either a configuration issue or not all services are running (the only available services are Apache or MySQL). If its red then WAMP is not running Quote Link to comment Share on other sites More sharing options...
Richard Bowser Posted February 8, 2009 Author Share Posted February 8, 2009 The php_error.log showed a whole slew of "undefined variable" errors in refresh.php and wampserverlib.php. I searched the installed directories using Windows Grep, and searched for the problems. The situation is not yet clear to me, but an interesting error message is "Warning: Invalid argument supplied for foreach() in C:\wamp\scripts\refresh.php on line 497" Line 497 holds "foreach ($apacheVersionList as $oneApache)" This suggests to me a failure is occurring before Apache starts up. I searched all Apache logs and cannot find a reference to Apache getting started anywhere. It is now evident that something is wrong somewhere. Please help! ??? Quote Link to comment Share on other sites More sharing options...
Richard Bowser Posted February 8, 2009 Author Share Posted February 8, 2009 PS "Put Online" fails with "internal error". I would have to get Apache running before I could do http://localhost to reach it ??? Rich Quote Link to comment Share on other sites More sharing options...
Mchl Posted February 8, 2009 Share Posted February 8, 2009 So the WampServer icon is red/yellow instead of white? Do you have Skype, or other application that might be occupying port 80? Click in WampServer icon in tray, go to Apache>Service>Test Port 80 and report what it says. Quote Link to comment Share on other sites More sharing options...
Richard Bowser Posted February 8, 2009 Author Share Posted February 8, 2009 Yes, my icon is red/white. I tested Port 80: "Your port 80 is not actually used" Therefore it is not busy. (I have nothing that can obscure it.) I uninstalled 2.0c and installed 2.0f, and then hit this stone wall. Rich ??? Quote Link to comment Share on other sites More sharing options...
wildteen88 Posted February 8, 2009 Share Posted February 8, 2009 refresh.php has nothing to do with Apache. refresh.php is used to build the WAMP tray menu. Also I think the log you where seeing was the php_error.log make sure you was loading Apaches error log. Quote Link to comment Share on other sites More sharing options...
Richard Bowser Posted February 8, 2009 Author Share Posted February 8, 2009 Yes, I was examining the php_error.log, as the first reply directed me. The Apache error.log is at C:\wamp\bin\apache\Apache2.2.11\logs\error.log and has only dates from Mon Dec 01 11:00:22 2008 to Wed Dec 10 09:49:49 2008. My problems occurred today, Feb 08 2009. Only I motice that my error.log looks more like what I'd intuitively expect to be an access log, only it's obviously NOT an access log. I note that Apache doesn't report any errors at all. I feel this looks suspiciously like a package problem with identical "trackmarks" duplicated on two Windows computers using the same install package. I am tempted to remove 2.0f and reinstall 2.0c to test it. But FYI, here is my error.log contents: Starting the Apache2.2 service The Apache2.2 service is running. rmine the server's fully qualified domain name, using 192.168.1.106 for ServerName [Mon Dec 01 11:00:22 2008] [notice] Apache/2.2.10 (Win32) configured -- resuming normal operations [Mon Dec 01 11:00:22 2008] [notice] Server built: Oct 10 2008 12:39:04 [Mon Dec 01 11:00:22 2008] [notice] Parent: Created child process 1844 httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.106 for ServerName httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.106 for ServerName [Mon Dec 01 11:00:22 2008] [notice] Child 1844: Child process is running [Mon Dec 01 11:00:22 2008] [notice] Child 1844: Acquired the start mutex. [Mon Dec 01 11:00:22 2008] [notice] Child 1844: Starting 64 worker threads. [Mon Dec 01 11:00:22 2008] [notice] Child 1844: Starting thread to listen on port 80. [Mon Dec 01 11:35:14 2008] [notice] Parent: child process exited with status 1 -- Restarting. httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.106 for ServerName [Mon Dec 01 11:35:17 2008] [notice] Apache/2.2.10 (Win32) configured -- resuming normal operations [Mon Dec 01 11:35:17 2008] [notice] Server built: Oct 10 2008 12:39:04 [Mon Dec 01 11:35:17 2008] [notice] Parent: Created child process 760 httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.106 for ServerName httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.106 for ServerName [Mon Dec 01 11:35:18 2008] [notice] Child 760: Child process is running [Mon Dec 01 11:35:18 2008] [notice] Child 760: Acquired the start mutex. [Mon Dec 01 11:35:18 2008] [notice] Child 760: Starting 64 worker threads. [Mon Dec 01 11:35:18 2008] [notice] Child 760: Starting thread to listen on port 80. httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.109 for ServerName [Fri Dec 05 17:14:14 2008] [warn] pid file C:/Program Files/Apache Software Foundation/Apache2.2/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run? [Fri Dec 05 17:14:14 2008] [notice] Apache/2.2.10 (Win32) configured -- resuming normal operations [Fri Dec 05 17:14:14 2008] [notice] Server built: Oct 10 2008 12:39:04 [Fri Dec 05 17:14:14 2008] [notice] Parent: Created child process 1964 httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.109 for ServerName httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.109 for ServerName [Fri Dec 05 17:14:14 2008] [notice] Child 1964: Child process is running [Fri Dec 05 17:14:14 2008] [notice] Child 1964: Acquired the start mutex. [Fri Dec 05 17:14:14 2008] [notice] Child 1964: Starting 64 worker threads. [Fri Dec 05 17:14:14 2008] [notice] Child 1964: Starting thread to listen on port 80. httpd.exe: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName [Tue Dec 09 09:42:46 2008] [warn] pid file C:/Program Files/Apache Software Foundation/Apache2.2/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run? [Tue Dec 09 09:42:46 2008] [notice] Apache/2.2.10 (Win32) configured -- resuming normal operations [Tue Dec 09 09:42:46 2008] [notice] Server built: Oct 10 2008 12:39:04 [Tue Dec 09 09:42:46 2008] [notice] Parent: Created child process 2768 httpd.exe: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName httpd.exe: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName [Tue Dec 09 09:42:47 2008] [notice] Child 2768: Child process is running [Tue Dec 09 09:42:47 2008] [notice] Child 2768: Acquired the start mutex. [Tue Dec 09 09:42:47 2008] [notice] Child 2768: Starting 64 worker threads. [Tue Dec 09 09:42:47 2008] [notice] Child 2768: Starting thread to listen on port 80. httpd.exe: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName [Wed Dec 10 09:02:17 2008] [warn] pid file C:/Program Files/Apache Software Foundation/Apache2.2/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run? [Wed Dec 10 09:02:17 2008] [notice] Apache/2.2.10 (Win32) configured -- resuming normal operations [Wed Dec 10 09:02:17 2008] [notice] Server built: Oct 10 2008 12:39:04 [Wed Dec 10 09:02:17 2008] [notice] Parent: Created child process 3912 httpd.exe: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName httpd.exe: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName [Wed Dec 10 09:02:17 2008] [notice] Child 3912: Child process is running [Wed Dec 10 09:02:17 2008] [notice] Child 3912: Acquired the start mutex. [Wed Dec 10 09:02:17 2008] [notice] Child 3912: Starting 64 worker threads. [Wed Dec 10 09:02:17 2008] [notice] Child 3912: Starting thread to listen on port 80. [Wed Dec 10 09:45:25 2008] [error] [client 127.0.0.1] File does not exist: C:/Program Files/Apache Software Foundation/Apache2.2/htdocs/favicon.ico [Wed Dec 10 09:49:45 2008] [notice] Parent: Received shutdown signal -- Shutting down the server. [Wed Dec 10 09:49:45 2008] [notice] Child 3912: Exit event signaled. Child process is ending. [Wed Dec 10 09:49:46 2008] [notice] Child 3912: Released the start mutex [Wed Dec 10 09:49:49 2008] [notice] Child 3912: All worker threads have exited. [Wed Dec 10 09:49:49 2008] [notice] Child 3912: Child process is exiting [Wed Dec 10 09:49:49 2008] [notice] Parent: Child process exited successfully. Quote Link to comment Share on other sites More sharing options...
wildteen88 Posted February 8, 2009 Share Posted February 8, 2009 The following error can be a problem httpd.exe: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName Open Apaches httpd.conf and find a line that starts with ServerName. Make sure it reads ServerName localhost:80 Save the httpd.conf and restart Apache. Quote Link to comment Share on other sites More sharing options...
Richard Bowser Posted February 8, 2009 Author Share Posted February 8, 2009 You have found the right haystack, but not the needle yet. My httpd.conf has line 171 as "ServerName localhost:80" My C:\wamp\bin\apache\Apache2.2.11\conf\original httpd.conf had line 171 commented out. I tried changing that, but it made no difference. I have several lines in my error.log of the form "httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.106 for ServerName". So something is inhibiting setting the server's domain name. Any ideas ??? Quote Link to comment Share on other sites More sharing options...
corbin Posted February 8, 2009 Share Posted February 8, 2009 The unable to determine fully qualified domain name error is not fatal. httpd.exe should continue to run fine after it assumes a name. There is probably some other problem. Quote Link to comment Share on other sites More sharing options...
Richard Bowser Posted February 8, 2009 Author Share Posted February 8, 2009 Thanks. I guess I'm just going to back out to 2.0c and see what happens. Quote Link to comment Share on other sites More sharing options...
Richard Bowser Posted February 8, 2009 Author Share Posted February 8, 2009 Help PLEASE: How do I mark this as "resolved"? ??? Quote Link to comment Share on other sites More sharing options...
Richard Bowser Posted February 9, 2009 Author Share Posted February 9, 2009 OK: I have confirmation the package WampServer2.0f.exe for both my PC & my buddy's PC is a great big FAIL. 2.0c works on both machines. The default setup crashes and apparently won't even allow Apache to start. Both crashes are identical, on both machines. Folks, maybe we should call out Will Smith and the M.I.B. - I sense a bug. How can one report a WAMP bug? ??? Quote Link to comment Share on other sites More sharing options...
Mchl Posted February 9, 2009 Share Posted February 9, 2009 On their forums. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.