Quantcast

503 error - service not available

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

503 error - service not available

filch

Not sure what happened here. The app was working just fine until today.
I am getting a 503 Service temporarily unavailable error when trying to
connect to a tomcat site using Apache as the front end and mod_jk
connectors. I have verified that tomcat is running on the correct ports
using:netstat -atp | grep java. I see no errors in the message logs ( we
are on CentOS by the way ) but I do see:

|[Wed Aug 03 18:49:24 2011] [15605:1199618400] [info] ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Wed Aug 03 18:49:24 2011] [15605:1199618400] [error] ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
[Wed Aug 03 18:49:24 2011] exodus www.exodusdecoded.com 0.198512
[Wed Aug 03 18:49:24 2011] [15605:1199618400] [info] jk_handler::mod_jk.c (2618): Service error=-3 for worker=exodus
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to (174.122.30.18:8010) (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [error] ajp_send_request::jk_ajp_common.c (1585): (exodus) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to (174.122.30.18:8010) (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [error] ajp_send_request::jk_ajp_common.c (1585): (exodus) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [error] ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
[Wed Aug 03 18:50:46 2011] exodus www.exodusdecoded.com 0.197989
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_handler::mod_jk.c (2618): Service error=-3 for worker=exodus

|

in the mod_jk.log file. Apache is running. I am stumped but really need
to get this back running if anyone out there is more experienced at
tomcat and apache connectors than I am, which wouldn't take much ;-)

Cheers,

Dave

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 503 error - service not available

Igor Cicimov
Obviously apache can't connect to tomcat. Any firewall/load balancer changes
maybe done last night between apache and tomcat? Can you access tomcat apps
bypassing apache? Can you telnet to tomcat server on the tomcat port from
the apache? Any errors in the tomcat log? Have you tried restarting tomcat?


Igor

On Thu, Aug 4, 2011 at 12:28 PM, Dave Filchak <[hidden email]> wrote:

>
> Not sure what happened here. The app was working just fine until today. I
> am getting a 503 Service temporarily unavailable error when trying to
> connect to a tomcat site using Apache as the front end and mod_jk
> connectors. I have verified that tomcat is running on the correct ports
> using:netstat -atp | grep java. I see no errors in the message logs ( we are
> on CentOS by the way ) but I do see:
>
> |[Wed Aug 03 18:49:24 2011] [15605:1199618400] [info]
> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
> failed (recoverable), because of error during request sending (attempt=2)
> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [error]
> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
> [Wed Aug 03 18:49:24 2011] exodus www.exodusdecoded.com 0.198512
> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [info] jk_handler::mod_jk.c
> (2618): Service error=-3 for worker=exodus
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
> (errno=111)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
> ajp_connect_to_endpoint::jk_**ajp_common.c (959): Failed opening socket to
> (174.122.30.18:8010) (errno=111)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
> ajp_send_request::jk_ajp_**common.c (1585): (exodus) connecting to backend
> failed. Tomcat is probably not started or is listening on the wrong port
> (errno=111)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
> failed (recoverable), because of error during request sending (attempt=1)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
> (errno=111)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
> ajp_connect_to_endpoint::jk_**ajp_common.c (959): Failed opening socket to
> (174.122.30.18:8010) (errno=111)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
> ajp_send_request::jk_ajp_**common.c (1585): (exodus) connecting to backend
> failed. Tomcat is probably not started or is listening on the wrong port
> (errno=111)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
> failed (recoverable), because of error during request sending (attempt=2)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
> [Wed Aug 03 18:50:46 2011] exodus www.exodusdecoded.com 0.197989
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_handler::mod_jk.c
> (2618): Service error=-3 for worker=exodus
>
> |
>
> in the mod_jk.log file. Apache is running. I am stumped but really need to
> get this back running if anyone out there is more experienced at tomcat and
> apache connectors than I am, which wouldn't take much ;-)
>
> Cheers,
>
> Dave
>
>
Pid
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 503 error - service not available

Pid
On 04/08/2011 03:38, Igor Cicimov wrote:
> Obviously apache can't connect to tomcat. Any firewall/load balancer changes
> maybe done last night between apache and tomcat? Can you access tomcat apps
> bypassing apache? Can you telnet to tomcat server on the tomcat port from
> the apache? Any errors in the tomcat log? Have you tried restarting tomcat?

+1

What changed on the system(s)?

How do you know Tomcat is actually running?

What is in the Tomcat logs for the period immediately before and after
it stopped working?


p

> On Thu, Aug 4, 2011 at 12:28 PM, Dave Filchak <[hidden email]> wrote:
>
>>
>> Not sure what happened here. The app was working just fine until today. I
>> am getting a 503 Service temporarily unavailable error when trying to
>> connect to a tomcat site using Apache as the front end and mod_jk
>> connectors. I have verified that tomcat is running on the correct ports
>> using:netstat -atp | grep java. I see no errors in the message logs ( we are
>> on CentOS by the way ) but I do see:
>>
>> |[Wed Aug 03 18:49:24 2011] [15605:1199618400] [info]
>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>> failed (recoverable), because of error during request sending (attempt=2)
>> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [error]
>> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
>> [Wed Aug 03 18:49:24 2011] exodus www.exodusdecoded.com 0.198512
>> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [info] jk_handler::mod_jk.c
>> (2618): Service error=-3 for worker=exodus
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
>> (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> ajp_connect_to_endpoint::jk_**ajp_common.c (959): Failed opening socket to
>> (174.122.30.18:8010) (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>> ajp_send_request::jk_ajp_**common.c (1585): (exodus) connecting to backend
>> failed. Tomcat is probably not started or is listening on the wrong port
>> (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>> failed (recoverable), because of error during request sending (attempt=1)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
>> (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> ajp_connect_to_endpoint::jk_**ajp_common.c (959): Failed opening socket to
>> (174.122.30.18:8010) (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>> ajp_send_request::jk_ajp_**common.c (1585): (exodus) connecting to backend
>> failed. Tomcat is probably not started or is listening on the wrong port
>> (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>> failed (recoverable), because of error during request sending (attempt=2)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
>> [Wed Aug 03 18:50:46 2011] exodus www.exodusdecoded.com 0.197989
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_handler::mod_jk.c
>> (2618): Service error=-3 for worker=exodus
>>
>> |
>>
>> in the mod_jk.log file. Apache is running. I am stumped but really need to
>> get this back running if anyone out there is more experienced at tomcat and
>> apache connectors than I am, which wouldn't take much ;-)
>>
>> Cheers,
>>
>> Dave
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Re: 503 error - service not available

filch
In reply to this post by Igor Cicimov
No changes regarding firewall or load balancers. Tomcat and apache live
on the same machine in this case.

On 22/07/64 2:59 PM, Igor Cicimov wrote:
> Obviously apache can't connect to tomcat. Any firewall/load balancer changes
> maybe done last night between apache and tomcat? Can you access tomcat apps
> bypassing apache?
There are, what appears to be three tomcat instances on this machine.
One using 8080, one on 8180 and the other 8280. I cannot connect to any
of these but the only one I care about is the one on 8180
> Can you telnet to tomcat server on the tomcat port from
> the apache?
I have tried telneting to the host on all ports defined in server.xml
and I can telnet to 8105 and 8205, the SHUTDOWN ports, but not 8005, and
none of the others. The connector ports for this instance, the one I am
concerned with are 8180 and 8443. The AJP connector port is 8010
> Any errors in the tomcat log? Have you tried restarting tomcat?
I have tried and thought I was successful but I am now getting:

java.net.ConnectException: Connection refused
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:519)
     at java.net.Socket.connect(Socket.java:469)
     at java.net.Socket.<init>(Socket.java:366)
     at java.net.Socket.<init>(Socket.java:180)
     at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:421)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:337)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:415)

when I try to shut it down.

I hope I am giving you useful information. As I said, I am not an
experienced tomcat admin. I inherited this site and am just trying to
learn. Wish ?I didn't have to learn under these circumstances.

Thanks

Dave

>
>
> Igor
>
> On Thu, Aug 4, 2011 at 12:28 PM, Dave Filchak<[hidden email]>  wrote:
>
>> Not sure what happened here. The app was working just fine until today. I
>> am getting a 503 Service temporarily unavailable error when trying to
>> connect to a tomcat site using Apache as the front end and mod_jk
>> connectors. I have verified that tomcat is running on the correct ports
>> using:netstat -atp | grep java. I see no errors in the message logs ( we are
>> on CentOS by the way ) but I do see:
>>
>> |[Wed Aug 03 18:49:24 2011] [15605:1199618400] [info]
>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>> failed (recoverable), because of error during request sending (attempt=2)
>> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [error]
>> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
>> [Wed Aug 03 18:49:24 2011] exodus www.exodusdecoded.com 0.198512
>> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [info] jk_handler::mod_jk.c
>> (2618): Service error=-3 for worker=exodus
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
>> (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> ajp_connect_to_endpoint::jk_**ajp_common.c (959): Failed opening socket to
>> (174.122.30.18:8010) (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>> ajp_send_request::jk_ajp_**common.c (1585): (exodus) connecting to backend
>> failed. Tomcat is probably not started or is listening on the wrong port
>> (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>> failed (recoverable), because of error during request sending (attempt=1)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
>> (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> ajp_connect_to_endpoint::jk_**ajp_common.c (959): Failed opening socket to
>> (174.122.30.18:8010) (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>> ajp_send_request::jk_ajp_**common.c (1585): (exodus) connecting to backend
>> failed. Tomcat is probably not started or is listening on the wrong port
>> (errno=111)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>> failed (recoverable), because of error during request sending (attempt=2)
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
>> [Wed Aug 03 18:50:46 2011] exodus www.exodusdecoded.com 0.197989
>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_handler::mod_jk.c
>> (2618): Service error=-3 for worker=exodus
>>
>> |
>>
>> in the mod_jk.log file. Apache is running. I am stumped but really need to
>> get this back running if anyone out there is more experienced at tomcat and
>> apache connectors than I am, which wouldn't take much ;-)
>>
>> Cheers,
>>
>> Dave
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 503 error - service not available

Rainer Jung-3
In reply to this post by filch
On 04.08.2011 04:28, Dave Filchak wrote:

>
> Not sure what happened here. The app was working just fine until today.
> I am getting a 503 Service temporarily unavailable error when trying to
> connect to a tomcat site using Apache as the front end and mod_jk
> connectors. I have verified that tomcat is running on the correct ports
> using:netstat -atp | grep java. I see no errors in the message logs ( we
> are on CentOS by the way ) but I do see:
>
> |[Wed Aug 03 18:49:24 2011] [15605:1199618400] [info]
> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
> failed (recoverable), because of error during request sending (attempt=2)
> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [error]
> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
> [Wed Aug 03 18:49:24 2011] exodus www.exodusdecoded.com 0.198512
> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [info]
> jk_handler::mod_jk.c (2618): Service error=-3 for worker=exodus
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
> (errno=111)
> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
> ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to
> (174.122.30.18:8010) (errno=111)

Error 111 is "Connection refused by host". So something between youweb
server and the Tomcat server (both ends included) doesn't allow to
connect to 174.122.30.18 port 8010. You should be able to reproduce with
telnet as others suggested and then diagnose purely on the network layer.

Regards,

Rainer


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 503 error - service not available

Bugzilla from ramesses21@gmail.com
In reply to this post by Pid
On 08/04/2011 04:31 AM, Pid wrote:

> On 04/08/2011 03:38, Igor Cicimov wrote:
>> Obviously apache can't connect to tomcat. Any firewall/load balancer changes
>> maybe done last night between apache and tomcat? Can you access tomcat apps
>> bypassing apache? Can you telnet to tomcat server on the tomcat port from
>> the apache? Any errors in the tomcat log? Have you tried restarting tomcat?
> +1
>
> What changed on the system(s)?
>
> How do you know Tomcat is actually running?
>
> What is in the Tomcat logs for the period immediately before and after
> it stopped working?
>
>
> p
>
>> On Thu, Aug 4, 2011 at 12:28 PM, Dave Filchak<[hidden email]>  wrote:
>>
>>> Not sure what happened here. The app was working just fine until today. I
>>> am getting a 503 Service temporarily unavailable error when trying to
>>> connect to a tomcat site using Apache as the front end and mod_jk
>>> connectors. I have verified that tomcat is running on the correct ports
>>> using:netstat -atp | grep java. I see no errors in the message logs ( we are
>>> on CentOS by the way ) but I do see:
>>>
>>> |[Wed Aug 03 18:49:24 2011] [15605:1199618400] [info]
>>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>>> failed (recoverable), because of error during request sending (attempt=2)
>>> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [error]
>>> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
>>> [Wed Aug 03 18:49:24 2011] exodus www.exodusdecoded.com 0.198512
>>> [Wed Aug 03 18:49:24 2011] [15605:1199618400] [info] jk_handler::mod_jk.c
>>> (2618): Service error=-3 for worker=exodus
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>>> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
>>> (errno=111)
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>>> ajp_connect_to_endpoint::jk_**ajp_common.c (959): Failed opening socket to
>>> (174.122.30.18:8010) (errno=111)
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>>> ajp_send_request::jk_ajp_**common.c (1585): (exodus) connecting to backend
>>> failed. Tomcat is probably not started or is listening on the wrong port
>>> (errno=111)
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>>> failed (recoverable), because of error during request sending (attempt=1)
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>>> jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed
>>> (errno=111)
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>>> ajp_connect_to_endpoint::jk_**ajp_common.c (959): Failed opening socket to
>>> (174.122.30.18:8010) (errno=111)
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>>> ajp_send_request::jk_ajp_**common.c (1585): (exodus) connecting to backend
>>> failed. Tomcat is probably not started or is listening on the wrong port
>>> (errno=111)
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info]
>>> ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat
>>> failed (recoverable), because of error during request sending (attempt=2)
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [error]
>>> ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
>>> [Wed Aug 03 18:50:46 2011] exodus www.exodusdecoded.com 0.197989
>>> [Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_handler::mod_jk.c
>>> (2618): Service error=-3 for worker=exodus
>>>
>>> |
>>>
>>> in the mod_jk.log file. Apache is running. I am stumped but really need to
>>> get this back running if anyone out there is more experienced at tomcat and
>>> apache connectors than I am, which wouldn't take much ;-)
>>>
>>> Cheers,
>>>
>>> Dave
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
     My apologies if I did not interpret this thread correctly, but
maybe you could see if the Apache daemon is running by signing into root
with "su -l" and running this command "service httpd status" if not
active then run this command "service httpd start". From what I gether
from this thread is sounds like the Apache web server is not active and
the problem is not ApacheTomcat.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Pid
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 503 error - service not available

Pid
On 04/08/2011 21:36, Brendon wrote:
> From what I gether from this thread is sounds like the Apache web server
> is not active and the problem is not ApacheTomcat.

If HTTPD wasn't active there'd be nothing in the mod_jk log and no 503
response...


p

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 503 error - service not available

Igor Cicimov
Anything in the system log? Running out of file descriptors maybe?

Igor

On Aug 5, 2011 7:07 AM, "Pid" <[hidden email]> wrote:

On 04/08/2011 21:36, Brendon wrote: > From what I gether from this thread is
sounds like the Apache ...
If HTTPD wasn't active there'd be nothing in the mod_jk log and no 503
response...

p --------------------------------------------------------------------- To
unsubscribe, e-mail: u...
Loading...