On 2011-09-08, at 1:01 PM, Mark Montague wrote:
>
> Short form: from a terminal window, try running "httpd -t" and see if it
> reports any error in your configuration files. Note that you might have
> multiple versions of httpd on your system (see below) and try to invoke the
> same version
Short form: from a terminal window, try running "httpd -t" and see if
it reports any error in your configuration files. Note that you might
have multiple versions of httpd on your system (see below) and try to
invoke the same version via the command line that you're trying to start
via the
On September 8, 2011 12:49 , Norman Fournier
wrote:
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?
Yes, except below you say that "ps aux | grep httpd" doe
On 2011-09-08, at 10:27 AM, Mark Montague wrote:
> On September 8, 2011 12:06 , Norman Fournier
> 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 dir
On September 8, 2011 12:06 , Norman Fournier
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
Hello,
My webserver cpu crashed last week and I have had to reconfigure my directory
layout to accommodate a newer version of Apache. Unfortunately none of the
sites handled by this server is visible on the internet. In the main the conf
is the same as the previous working copy. named is workin
