Re: Issues with vhosts: Service Temporarily Unavailable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I found the problem as soon as i sent the message ;) it was an issue
with my first vhost entry as it was rewriting to an itools
(www.hforge.org) server on port 8080, but at the time it was not up
and running.
I assumed that the apache will still work as it will read the first
entry on the httpd.conf file, but now i know that i have to make a
virual host entry for this in the httpd-vhosts.conf

Thanks for the reply.
Norman

On Wed, Jul 29, 2009 at 10:35 PM, André Warnier<aw@xxxxxxxxxx> wrote:
> Norman Khine wrote:
>>
>> Hello,
>> I have an issue with Apache in that when I enable vhosts I get this 503
>> error:
>>
>> --
>> Service Temporarily Unavailable
>>
>> The server is temporarily unable to service your request due to
>> maintenance downtime or capacity problems. Please try again later.
>> --
>>
>> If I disable
>>
>> # Virtual hosts
>> Include conf/extra/httpd-vhosts.conf
>>
>> All works fine.
>>
>> But as soon as I enable it, I get the "The server is temporarily
>> unable to service your request due to maintenance downtime or capacity
>> problems. Please try again later."
>>
>> Here are my configuration options:
>>
>> $ ./configure --enable-cgi --enable-vhost-alias --enable-rewrite
>> --enable-proxy --enable-headers
>>
>> $ /usr/local/apache2/bin/httpd -V
>> Server version: Apache/2.2.12 (Unix)
>> Server built:   Jul 29 2009 22:27:22
>> Server's Module Magic Number: 20051115:23
>> Server loaded:  APR 1.3.7, APR-Util 1.3.8
>> Compiled using: APR 1.3.7, APR-Util 1.3.8
>> Architecture:   32-bit
>> Server MPM:     Prefork
>>  threaded:     no
>>    forked:     yes (variable process count)
>> Server compiled with....
>>  -D APACHE_MPM_DIR="server/mpm/prefork"
>>  -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 DYNAMIC_MODULE_LIMIT=128
>>  -D HTTPD_ROOT="/usr/local/apache2"
>>  -D SUEXEC_BIN="/usr/local/apache2/bin/suexec"
>>  -D DEFAULT_PIDLOG="logs/httpd.pid"
>>  -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
>>  -D DEFAULT_LOCKFILE="logs/accept.lock"
>>  -D DEFAULT_ERRORLOG="logs/error_log"
>>  -D AP_TYPES_CONFIG_FILE="conf/mime.types"
>>  -D SERVER_CONFIG_FILE="conf/httpd.conf"
>>
>> I am on OS X 10.4.11
>>
>> Is there a way to check what the problem is?
>>
> Yes.
> Turn your vhosts back on, and enter
>
> /usr/local/apache2/bin/httpd -t
>
> or try to start Apache, and then look at the logfile error.log.
>
> In all likelihood, one of the above will tell you what is wrong.
>
> ---------------------------------------------------------------------
> 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
>
>

---------------------------------------------------------------------
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



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux