Jump to content

Richard Bowser

Members
  • Posts

    16
  • Joined

  • Last visited

    Never

Contact Methods

  • Website URL
    http://www.roughwriter.org

Profile Information

  • Gender
    Male
  • Location
    El Paso Texas

Richard Bowser's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. 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? ???
  2. Thanks. I guess I'm just going to back out to 2.0c and see what happens.
  3. 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 ???
  4. 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.
  5. 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 ???
  6. PS "Put Online" fails with "internal error". I would have to get Apache running before I could do http://localhost to reach it ??? Rich
  7. 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! ???
  8. 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
  9. A semaphore is a protected variable that embodies the classic way to restrict data access to shared resources in a multiprogramming environment. The numerical value of a semaphore represents the number of resource units available. In the special case where there is only one single item to protect, it is represented by a binary semaphore. PHP provides resources to implement System V IPC facilities, including semaphores, documented in CXXXVI. However, these won't work for me, since semaphores must be specifically enabled when PHP is compiled, and my WAMP distribution (5.1.7.2) does not include that functionality. I can implement my own semaphores, BUT I need some advice: I know a construct such as $sem = --$sem will approximate the single uninterruptible operation the interlocking primitive requires. However I will need to see actual assembly code to verify the execution sequence invoked. I need to confirm that I can get an uninterruptible test & set instruction sequence. Given that, the rest of building all needed control structures becomes almost trivially simple. Can anybody help me understand how (or even IF) I can confirm the actual code executed? Thanks in advance. Richard Bowser
  10. Reading the PHP manual, I believe it is possible to use digest mode authentication in a PHP script. This is just a belief because – although Example 34.2 illustrates it – nowhere, in the PHP manual, or at php.net is the function http_digest_parse() documented. If this is wrong PLEASE tell me! Here’s my situation: I copied the example verbatim and tried to run it, with the example’s user names & passwords (both pairs). Twice I had failures. The dialog box did appear in each case of login attempt, but each time the call to http_digest_parse($_SERVER['PHP_AUTH_DIGEST']) returned a binary 1 (for Failure). This was no shock to me, since this was only my first try. I went to look up the function and found: nothing. Whatsoever. A brick wall dead-end. I don't want to act like"clueless Lewis", but I guess here I really am! Richard B
  11. I know you're a newbie, as I once was. Probably the simplest answer is that WAMP is a test & development utility for web sites. It is especially useful in developing web database applications. You might want to check out Janet Valade's PHP & MySQL For Dummies®, Published by Wiley Publishing, Inc. Best of luck!
  12. I found it!  I recently spent over 2 weeks just searching for HTTP authentication in PHP and I couldn't find it.  But after all the dialog this post generated, it made me think "maybe I'm missing something".  And so I went searching again.  Then I discovered that chapter 34 in the PHP manual is entitled "HTTP authentication with PHP".  :-[ Thanks everyone. (Even you, oldmanice.  You made me [i]start[/i] thinking "maybe I'm approaching this all wrong"!) Richard Bowser May God bless EVERYBODY.
  13. Folks, is there a problem with my question?  If it’s too long, let’s simplify it: I’ve read the tutorials, studied the manuals, asked friends, and spent prodigious amounts of time experimenting and carefully testing every hypothesis I or my friends could generate.  I admit I have not read through the source code of Apache and Firefox 2.0.  But now I’m just trying to locate which particular haystack I need to search in for this particular elusive needle. This is NOT a casual or unthinking question.  I even posted a question in PHP freaks forum questions asking what was the best forum to post my question in, and I was told to try here.  I would have no problem being told "RTFM", that is – if I had a manual to read.  I would love to find one!  (Yes, I do have a copy of RFC2716 and I have studied it, painstakingly.)  Can anyone tell me where I can find documentation or script examples of how to authenticate users via built-in RFC2716 Basic authorization dialogs? ???
  14. I have a login script called auth.php which a friend gave me.  Yet whenever I try to use it on my local WAMP5 system v 1.66 (current) it seems to unbalance either my Apache localhost server or my browser client (on both IE7 & FF 2.0).  The script relies on Basic authentication (not digest).  I strongly suspect there’s something pretty marginal in the coding, because I get such widely varying results even with minor diagnostic tweaks.  It seems to perturb the challenge-response interaction of client and my Apace server.  For example, if I change the line that calls displayLogin() on unset Login variables to print ‘Not set<br>’; then the login dialog is not displayed and the script just sails right through to completion.  I do NOT comprehend this behavior. I have been searching on the web for a while and have not found any example login scripts to copy that use RFC 2617-style Basic authentication.  Neither have I been able to locate any documentation describing how to write a login script (for the server side) using RFC 2617 Basic authentication that forces the client to invoke its built-in login dialog process, either in any PHP documentation or in any HTML documentation.  My problem is that on my test machine, the implicit login state machine always fails to accept any input whatsoever.  I want to determine whether my Apache has a problem, or the donated script is bad.  Therefore, I would love to find a sample script to emulate.  I would be happy with either a PHP script, or even a pure html script. I want to maintain my own MySQL users database, and really I only want the native browser dialog to return whatever values the user enters in $PHP_AUTH_USER and $PHP_AUTH_PW.  It is possible that this is really an Apace configuration problem.  But it is also conceivable that I just don’t comprehend the real problem.  In any case, I would like to see some known valid login scripts that use this method.  I am fully aware that Digest mode is more secure, but I’d like to get a Basic mode script working first before moving on to Digest. The script is below for anyone who wants to peruse it.  Any comments would be very much appreciated! auth.php: <?PHP function displayLogin() { header("WWW-Authenticate: Basic realm=\"Authorization Required\""); header("HTTP/1.0 401 Unauthorized"); echo "<h2>Authentication Failure</h2>"; echo "The username and password provided did not work. Please reload this page and try again."; exit; } $db = mysql_connect('127.0.0.1','root','') or die("Couldn't connect to the database."); mysql_select_db('userdb') or die("Couldn't select the database"); if (!isset($PHP_AUTH_USER) || !isset($PHP_AUTH_PW)) { // If username or password hasn't been set, display the login request. displayLogin(); } else { // Escape both the password and username string to prevent users from inserting bogus data. $PHP_AUTH_USER = addslashes($PHP_AUTH_USER); $PHP_AUTH_PW = md5($PHP_AUTH_PW); // Check username and password against the database. $result = mysql_query("SELECT * FROM users WHERE passwd='$PHP_AUTH_PW' AND username='$PHP_AUTH_USER'") or die("Couldn't query the user-database."); $num = mysql_result($result, 0); if (!$num) { // If there were no matching users, show the login displayLogin(); } } // All code/html below will only be displayed to authenticated users. ?> ???
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.