Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

NAS SSO service could not started.

Hi

I have a problem that i am unable to start the SSO service onto the one of my NAS server in inline mode but the service is running fine on my two NAS which are deployed on OOB mode.

It gives error that could not start the service please chk configurations . As i checked the nas_server.log logs i get the following error does any one have some idea abt it

DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSOUser = shkcas04

2010-09-21 12:02:16.997 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSOUser = shkcas04:DURATION=0

2010-09-21 12:02:17.003 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSOPass = Cisco1234

2010-09-21 12:02:17.003 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSOPass = Cisco1234:DURATION=0

2010-09-21 12:02:17.008 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSOKdc = pkshv002.apac.ad.ici.com

2010-09-21 12:02:17.009 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSOKdc = pkshv002.apac.ad.ici.com:DURATION=1

2010-09-21 12:02:17.014 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSORealm = APAC.AD.ICI.COM

2010-09-21 12:02:17.014 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSORealm = APAC.AD.ICI.COM:DURATION=0

2010-09-21 12:02:17.019 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - invoke: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:save

2010-09-21 12:02:17.021 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - invoke: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:save:DURATION=2

2010-09-21 12:02:17.026 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - invoke: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:startSSOServer

2010-09-21 12:02:17.026 +0500 WARN  com.perfigo.wlan.jmx.adsso.GSSServer               - Server was not running ...

2010-09-21 12:02:17.026 +0500 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - Server starting server ...

2010-09-21 12:02:17.026 +0500 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - SPN : [shkcas04/pkshv002.apac.ad.ici.com@APAC.AD.ICI.COM]

2010-09-21 12:02:17.026 +0500 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - building kdc list for domain pkshv002.apac.ad.ici.com

2010-09-21 12:02:18.470 +0500 DEBUG com.perfigo.wlan.ssl.SSLLog                        - RMISocketFactory:adding socket:d3c940[TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.92.15.1,port=15873,localport=1099]]

2010-09-21 12:02:25.695 +0500 TRACE com.perfigo.wlan.jmx.admin.FailSafeManager         - FailSafeManager is running:{0.85,0.3,[0:0:15]}:DETECT_INTERVAL=20:DETECT_TIME_OUT=300

2010-09-21 12:02:25.695 +0500 TRACE com.perfigo.wlan.jmx.admin.FailSafeManager         - FailSafeManager has nothing to do ...10.92.15.1:0:1

2010-09-21 12:02:25.695 +0500 TRACE com.perfigo.wlan.jmx.admin.FailSafeManager         - FailSafeManager is going to sleep: {0.85,0.3,[0:0:0]} delay=20000

2010-09-21 12:02:37.022 +0500 ERROR com.perfigo.wlan.jmx.adsso.GSSServer               - Unable to start server ... pkshv002.apac.ad.ici.com

2010-09-21 12:02:37.022 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - invoke: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:startSSOServer:DURATION=19996

2010-09-21 12:02:37.061 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSOState = 0

2010-09-21 12:02:37.061 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - setAttribute: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:SSOState = 0:DURATION=0

2010-09-21 12:02:37.066 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - invoke: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:save

2010-09-21 12:02:37.067 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - invoke: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:save:DURATION=1

2010-09-21 12:02:39.598 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - isRegistered: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo

2010-09-21 12:02:39.598 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - isRegistered: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:DURATION=0

2010-09-21 12:02:39.603 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - unregisterMBean: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo

2010-09-21 12:02:39.603 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - unregisterMBean: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:DURATION=0

2010-09-21 12:02:39.608 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - createMBean: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type=MLet,name=casLoader

2010-09-21 12:02:39.609 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - createMBean: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type=MLet,name=casLoader:DURATION=1

2010-09-21 12:02:39.615 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - invoke: DefaultDomain:type=com.perfigo.wlan.jmx.admin.ServerInfo:init

2010-09-21 12:02:39.615 +0500 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper             - BeanServerWrapper - invoke:

Regards

Waqas

1 ACCEPTED SOLUTION

Accepted Solutions

Re: NAS SSO service could not started.

Waqas,

From a SSH session on the CAS, can you ping that server and post the reply?

Faisal

4 REPLIES

Re: NAS SSO service could not started.

Waqas,

Can you ping the AD server from your CAS?

Faisal

Community Member

Re: NAS SSO service could not started.

Dear Faisal ,

yes i can ping my ADs .As i am not a microsoft guy but ill try to explain it as best as i can the structure of AD

we have a Parent AD and two  child AD. We are creating a user on parent AD but running KTPass on child and it is running .Now this actually worked for one of our server but this server is giving us the problem.

Regards

Waqas

Re: NAS SSO service could not started.

Waqas,

From a SSH session on the CAS, can you ping that server and post the reply?

Faisal

Community Member

Re: NAS SSO service could not started.

Thanks faisal for your help as My CAS was unable to ping the AD server and after adding the static route in CAS my problem is solved and the SSO service is started to run.

Regards

Waqas

917
Views
0
Helpful
4
Replies
CreatePlease to create content