On 2011-09-08, at 10:27 AM, Mark Montague wrote: > On September 8, 2011 12:06 , Norman Fournier <norman@xxxxxxxxxxxxxxxxxx> wrote: >> I have had to reconfigure my directory layout to accommodate a newer version of Apache. > > This is unusual. Usually different versions of Apache HTTP Server will use the same directory layout. The directory layout usually only changes when you switch between different distributions of Apache HTTP Server -- for example, the distribution provided by Red Hat will use one directory layout, but if you compiled Apache HTTP Server yourself a different directory layout would be used unless you took care to duplicate all of Red Hat's configuration and layout for httpd. > > If possible, try to minimize variables when upgrading and keep the directory layout the same. This may mean using a different distribution of Apache HTTP Server. > > It looks like the configuration file you have came from a MacOS X system. Are you using this configuration file with the version of httpd supplied by Apple? Were you using a version of httpd supplied by Apple before this problem started? This is the conf file supplied with osx 10.5. The previous webserver was running on osx 10.4. This version has changed the name of the "httpd" folder to "apache2". vhosts conf files are located in a nested folder inside "apache2" called "extra". I have checked the syntax of the included vshosts and they appear correct. The syntax of this file also appears correct. > >> My guess is that the httpd.conf is where my error is located. > > Why do you guess that? Is this based on some evidence (in that case, please share the evidence), or is it just a purely random guess? I arrived at that interim conclusion based on a process of elimination, starting with the BIND configuration and working backwards to here. But ini essence it is a random guess. I have no evidence other than the data terminal shares with me. The sites are visible on other machines on the internal network using bare ip and port numbers. I assume that means the web server is working or it wouldnt be serving web page at all? >> If you could look over this file for me and offer suggestions as to where my error might be I would appreciate it. > > This is the wrong way to solve the problem. > > First, when you try to start httpd, do you get any errors or warning messages in the terminal in which you are starting it? Or if you are using the Apple Server Admin tool, does it complain or report any errors? There are no errors or warnings in terminal when I start the webserver, but it appears that it is not running as ps uax | grep httpd does not return anything? I have used apachectl graceful and it doesn't return the usual "apapche gracefully restarted". I then tried the restarting using Sharing in system preferences pane and it tells me web sharing is on. > Next, are any errors in your web server error log file? This is apparently /private/var/log/apache2/error_log in your configuration. There has been nothing written to the log files since the server crash 4 days ago. > Near the end of the configuration file you posted, there are a lot of Include directives. If you do have an error in your httpd configuration, it could be in the file you posted, but it could also be in any of those included files. The include directives were all authored by apple except the include for vhosts. The vhosts were authored by me. They were working in the previous iteration of the webserver. Should I post a typical vhost file? I appreciate you looking over this for me Mark. Thank you. Norman --- www: http://www.normanfournier.com facebook: http://www.facebook.com/normanfournierdotcom linkedin: http://www.linkedin.com/profile/view?id=18127460 youtube: http://www.youtube.com/user/normanfournier --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|