Re: 503 service unavailable error

[kevin mcgowan <clunis@xxxxxxxxx>]

so it looks like your certs are fine if you're seeing LOGIN and  
REGISTER requests on the weblogin server.  What about logs on the web  
server that is attempting to provide the service?  There is nothing  
in the apache logs on the service?

This error is intermittent?  How many weblogin servers do you have?   
Are the success and error experiences between the same service and  
weblogin servers?  Are these happening with the same web browser?   
Can you tell me OS, Apache version, Cosign version, and web browser  
versions being used?

Are cookie files being created in the filter cache directory (if you  
su to your web server user can you create files?)?  Is this machine  
receiving Kerberos tickets and can the web server user write those as  
well?

k

On Aug 4, 2005, at 1:11 PM, David Alexander wrote:

> What are the possible causes of 503 service unavailable?
>
> I have the correct owner on the filter directory.  The only clue  
> that I have is in syslog.
>
> failure:
>
> [root@cosign11 root]# tail -f /var/log/cosignd.log
> Aug  4 12:41:57 cosign11 cosignd[6286]: connect: 132.235.xxx.xxx
> Aug  4 12:41:57 cosign11 cosignd[6286]: LOGIN user xxx_cell  
> 132.235.yyy.yyy
> Aug  4 12:41:57 cosign11 cosignd[6286]: REGISTER user xxx_cell  
> 132.235.yyy.yyy cosign-shibboleth
>
> success:
>
> [root@cosign11 root]# tail -f /var/log/cosignd.log
> Aug  4 12:43:00 cosign11 cosignd[6404]: connect: 132.235.xxx.xxx
> Aug  4 12:43:00 cosign11 cosignd[6404]: LOGIN user xxx_cell  
> 132.235.yyy.yyy
> Aug  4 12:43:00 cosign11 cosignd[6404]: REGISTER user xxx_cell  
> 132.235.yyy.yyy cosign-shibboleth
> Aug  4 12:43:00 cosign11 cosignd[6405]: connect: 132.235.xxx.xxx
>
>
> --Dave
>
> !DSPAM:42f24fb3163651852320630!