apache-2.0.51 on fc2 - error

[Kristina Clair]

On 4/29/05, Dave Pisarek <shaggyshags at gmail.com> wrote:
> On 4/29/05, Saurabh Barve <sa at atmos.colostate.edu> wrote:
> > Hi,
> >
> > The apache list wasn't much help, so I am trying my luck here. I am
> > running apache-2.0.51 on an FC2 machine.
> >
> > When I try to run apachectl command, I get a weird error:
> >
> > [root]# apachectl status
> > ERROR at dump.c:188: Connection refused
> >
> > Has anybody else seen this error before?
> >
> > Here's more information about apache and the fc2 installation-
> >
> > [root]# httpd -V
> > Server version: Apache/2.0.51
> > Server built:   Nov 12 2004 10:10:20
> > Server's Module Magic Number: 20020903:9
> > Architecture:   32-bit
> > Server compiled with....
> >   -D APACHE_MPM_DIR="server/mpm/prefork"
> >   -D APR_HAS_SENDFILE
> >   -D APR_HAS_MMAP
> >   -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
> >   -D APR_USE_SYSVSEM_SERIALIZE
> >   -D APR_USE_PTHREAD_SERIALIZE
> >   -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
> >   -D APR_HAS_OTHER_CHILD
> >   -D AP_HAVE_RELIABLE_PIPED_LOGS
> >   -D HTTPD_ROOT="/etc/httpd"
> >   -D SUEXEC_BIN="/usr/sbin/suexec"
> >   -D DEFAULT_PIDLOG="logs/httpd.pid"
> >
> > [root]# uname -a
> > Linux 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686 i386
> > GNU/Linux
> >
> > --
> > ----------------------------------------------------------------
> > | "Yours is to work. The results will take care of themselves" |
> > |  -- Swami Vivekanad                                          |
> > ----------------------------------------------------------------
> >
> > Saurabh Barve
> > sa at atmos.colostate.edu
> > (970)491-7714
> >
> > --
> > fedora-list mailing list
> > fedora-list at redhat.com
> > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> >
> 
> Are you able to start apache? Is it lisening on port 443?
> --
> -- Dave
> 

Yeah, if you are seeing a connection refused error then that means
apachectl can't connect to apache.  Common reasons for this would be:
because apache isn't running, apache isn't running on the expected
port (it's probably trying to connect to port 80), or something else
is preventing the connection (like a firewall?).

Kristina