Symantec Access Management

Created on behalf of @ P Soni

and follow up on thread : 12.7 adminui: creating legacy administrator to loginto admin ui 

Hi Ujwol,

Thanks for your reply. I changed the search. It went through to the final screen this time, which is better. but I haven't had much luck. I came to below screen and it got hung.

I started the adminui using standalone script. It has been sitting here for hours now, The logs below is from 3rd attempt of starting jboss.

12:31:02,145 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 44) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.

From server.log not much detail:

tail -f server.log
2018-01-25 12:31:07,597 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
2018-01-25 12:31:07,693 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA
2018-01-25 12:31:07,810 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTPS listener https listening on /0.0.0.0:8443
2018-01-25 12:31:07,843 INFO  [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started
2018-01-25 12:31:07,844 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra
2018-01-25 12:31:07,846 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
2018-01-25 12:31:08,204 INFO  [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
2018-01-25 12:31:08,309 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
2018-01-25 12:31:08,310 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
2018-01-25 12:31:08,310 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 16172ms - Started 252 of 304 services (104 services are lazy, passive or on-demand)

What is the way of further debugging this issue?

Hi ,

Can you change the log level to "debug" in /opt/CA/siteminder/siteminder/adminui/standalone/configuration/standalone-full.xml

Change :

<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>

To : 

<root-logger>
<level name="DEBUG"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>

and upload the new server.log ?

Also if this is linux, can you check available entropy :

cat /proc/sys/kernel/random/entropy_avail

Hi Ujwol,

Thanks for your help. Unfortunately can't capture the log right now as I had reinstalled as someone was doing some configuration. It works now but really not sure what trigger makes it go into that phase.

Entropy : 3134 (is it enough or this could be an issue?)

I will put the debug level settings in. I really hope that there will be solution to this problem.

Ah ok ..entropy value > 1000 is good and usually enough.

I am closing this thread for now .. let us know when you could reproduce the issue again..