Production - Service not available message (intermittent)

[lalithj]

Thanks,

This has become a real production issue now, as this is in production we got
limited access.

Some how I enabled the logs and reproduce the error, also captured the below
in idp-process.log

Eventhough it was waiting in login Screen but it appears things were
processing in idp, looking at below logs can we assume the botleneck is in
shib (uApprove) mysql database? because It got stoped in sharedtoken...






17:12:30.449 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:314]
- Resolving attribute surname for principal 50xxxxx
17:12:30.449 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:336]
- Resolved attribute surname containing 1 values
17:12:30.449 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:314]
- Resolving attribute givenName for principal 50xxxxx
17:12:30.449 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:336]
- Resolved attribute givenName containing 1 values
17:12:30.452 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:336]
- Resolved attribute commonName containing 1 values
17:12:30.452 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:314]
- Resolving attribute eduPersonAffiliation for principal 50xxxxx
17:12:30.453 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:336]
- Resolved attribute uid containing 1 values
17:12:30.455 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:336]
- Resolved attribute eduPersonAffiliation containing 1 values
17:12:30.455 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:314]
- Resolving attribute auEduPersonSharedToken for principal 50xxxxx
17:12:30.456 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:354]
- Resolving data connector sharedToken for principal 50xxxxx



After the timeout, I observed below in apache logs

)The timeout specified has expired: ajp_ilink_receive() can't receive header




Interesting thing is, then I close my browser and try again, it went
through. This is the behaviour users are complaining about

I can't find much in /var/log/mysqld.log


Could this be a networking issue? Given that this is production, any way we
can troubshoot further, or any other suspects?

Thanks











--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Production-Service-not-available-message-intermittent-tp7586537p7587111.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.