You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Arno WAS <ar...@free.fr> on 2004/03/03 14:03:11 UTC
Re: [users@httpd] ErrorDocument 500 not working
Hello,
Have you try to put this :
ErrorDocument 500 http://YOUR_SERVER/pcs_outage.html
Instead of
ErrorDocument 500 /pcs_outage.html
Arno
> I am not getting much of a response.....so maybe I am looking in the wrong
> place.
>
>
> I have a feeling this could be related to my <VirtualHost> container.
>
> In my case, the IP address of the front-end server server is
> 192.168.37.171.
>
> "pcsstg.harrahs.org" is registered to point to the same IP address. (I
> checked this by doing a ping pcsstg.harrahs.org.)
>
> BUT....SHOULD I HAVE AN IP ADDRESS INSTEAD OF "pcsstg.harrahs.org" IN THE
> <VirtualHost> TAG???
>
> --------------------------------------
> NameVirtualHost 192.168.37.171
>
> <VirtualHost pcsstg.harrahs.org> <--- IS THIS INCORRECT?????
> ServerAdmin lstacey@harrahs.com
> DocumentRoot /www/pcs/htdocs
> ServerName pcsstg.harrahs.org
> ErrorLog logs/error_log.pcsstg
> TransferLog logs/access_log.pcsstg
> ErrorDocument 500 /pcs_outage.html
> </VirtualHost>
> --------------------------------------
>
>
>
> Robin Clarke
> Harrah's | Information Technology | Las Vegas
> p: (702) 407 6137 f: (702) 407 6132
>
>
> -----Original Message-----
> From: Robin Clarke
> Sent: Tuesday, February 03, 2004 1:26 PM
> To: users@httpd.apache.org
> Subject: RE: [users@httpd] ErrorDocument 500 not working
>
>
> I am still unable to get the ErrorDocument directive to work.
>
> I have made change to httpd.conf, and now I see slightly different results.
>
> <VirtualHost pcsstg.harrahs.org>
> ServerAdmin lstacey@harrahs.com
> DocumentRoot /www/pcs/htdocs
> ServerName pcsstg.harrahs.org
> ErrorLog logs/error_log.pcsstg
> TransferLog logs/access_log.pcsstg
> #ErrorDocument 500 /pcs_outage.html <-- COMMENTED THIS OUT
> </VirtualHost>
>
>
> # 3) external redirects
> #ErrorDocument 402 http://some.other_server.com/subscription_info.html
> #
> ErrorDocument 500 /pcs_outage.html <--- PUT IN THIS GLOBAL DECLARATION
>
>
> When I shut down the WebSphere app server, and I try to hit the site, I get
> the usual Apache Internal Server Error page, but with an additional error
> at the bottom that says:
>
> "Additionally, a 500 Internal Server Error error was encountered while
> trying to use an ErrorDocument to handle the request. "
>
>
> There is no entry in error_log.
>
> access_log shows the following. The last line is what happens when the app
> server is down. Why is there a dash as the last character, and no number?
>
> 10.135.18.52 - - [03/Feb/2004:15:12:04 -0600] "GET /ipopeng.htm HTTP/1.1"
> 304 0 10.135.18.52 - - [03/Feb/2004:15:12:04 -0600] "GET
> /media/images/brands.jpg HTTP/1.1" 304 0 10.135.18.52 - -
> [03/Feb/2004:15:12:05 -0600] "GET /normal.js HTTP/1.1" 304 0 10.135.18.52 -
> - [03/Feb/2004:15:12:05 -0600] "GET /plugins.js HTTP/1.1" 304 0
> 10.135.18.52 - - [03/Feb/2004:15:12:05 -0600] "GET /agenda.js HTTP/1.1" 304
> 0 10.135.18.52 - - [03/Feb/2004:15:12:05 -0600] "GET /normal.css HTTP/1.1"
> 304 0 10.135.18.52 - - [03/Feb/2004:15:12:49 -0600] "GET / HTTP/1.1" 500 -
>
>
> I am using IBM_HTTP_SERVER/1.3.19.3 Apache/1.3.20 (Unix).
>
> THANK YOU!
>
>
> Robin Clarke
> Harrah's | Information Technology | Las Vegas
> p: (702) 407 6137 f: (702) 407 6132
>
>
> -----Original Message-----
> From: Robin Clarke
> Sent: Monday, February 02, 2004 9:36 AM
> To: users@httpd.apache.org
> Subject: RE: [users@httpd] ErrorDocument 500 not working
>
>
> I see the following entry in the (WebSphere) plugin log file (native.log).
>
> This looks as expected as the back end App Server is down, and I expect
> this returns the 500 to Apache.
>
>
> ------------------------------------------------------------
> [Mon Feb 2 10:43:13 2004] 0000aabe 00000001 - ERROR: ws_common:
> websphereGetStream: Failed to connect to app server, OS err=79 [Mon Feb 2
> 10:43:13 2004] 0000aabe 00000001 - ERROR: ws_common: websphereExecute:
> Failed to create the stream [Mon Feb 2 10:43:13 2004] 0000aabe 00000001 -
> ERROR: ws_server: serverSetFailoverStatus: Marking BM Clienteling down [Mon
> Feb 2 10:43:13 2004] 0000aabe 00000001 - ERROR: ws_common:
> websphereHandleRequest: Failed to execute the transaction to 'BM
> Clienteling'; will try another one [Mon Feb 2 10:43:13 2004] 0000aabe
> 00000001 - ERROR: ws_common: websphereHandleRequest: Failed to find an app
> server to handle this request
> ------------------------------------------------------------
>
> Robin Clarke
> Harrah's | Information Technology | Las Vegas
> p: (702) 407 6137 f: (702) 407 6132
>
>
> -----Original Message-----
> From: Jez Hancock [mailto:jez.hancock@munk.nu]
> Sent: Monday, February 02, 2004 9:23 AM
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] ErrorDocument 500 not working
>
> On Mon, Feb 02, 2004 at 08:47:04AM -0800, Robin Clarke wrote:
> > I am trying to configure Apache to display a certain page when my
> > application server is down - but am having no luck. (WebSphere is
> > running, but the actual app server is stopped.)
>
> You mention your access log, but what does the error log say?
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org