MCB, IDP hangs during startup

[Scott Koranda]

On Wed, Nov 26, 2014 at 12:45 PM, Steven Carmody
<steven_carmody at brown.edu> wrote:
> On 11/26/14 12:06 PM, David Langenberg wrote:
>> Is there anything interesting in the tomcat logs (specifically
>> catalina.out & localhost-$DATE)?  Have you turned up MCB logging to
>> DEBUG level?
>>
>
> I've MCB logging to DEBUG ... here are the last two lines that appear in
> idp-process:
>
> mcbConfig =
> [edu.internet2.middleware.assurance.mcb.authn.provider.MCBConfiguration at 49deadf0]
>
> 13:32:17.964 - DEBUG
> [edu.internet2.middleware.assurance.mcb.authn.provider.MCBLoginServlet:103]
> - Initializing velocity engine using
> [/usr/local/idp-2.4/conf/velocity.properties]
>
> When others using MCG look at their log files, does that value of
> mcbConfig seem reasonable and appropriate ?

Yes. I have this:

20:45:14.979 - DEBUG
[edu.internet2.middleware.assurance.mcb.authn.provider.MCBLoginServlet:103]
- Initializing velocity engine using
[/opt/shibboleth-idp-2.4.0/conf/velocity.properties]

>
> And... can you tell me what line appears next in your idp-process log
> file, after the "Initializing velocity engine using ...." ?

20:48:38.536 - INFO
[edu.internet2.middleware.shibboleth.common.config.BaseService:158] -
Loading new configuration for service shibboleth.AttributeResolver

The next log entry from MCB itself does not occur until after an
authentication flow is underway.

>
> Looking at the code, the method in MCBLoginServlet returns soon after
> adding that line to the log .... I'd like to know where execution
> continues after that point ....
>
> thanks !
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net