Page 1 of 1

Error executing cleanup_abandoned_locks.sh

Posted: Tue Nov 03, 2015 5:46 pm
by raji33
Hi,

We have the below error while executing the script cleanup_abandoned_locks.sh.

Tried re-index and restarting the datastage services and also checked with oracle dba if there are any issues at DB level, No luck.
Any inputs please?


Error executing command: CWWIM4537E No principal is found from the 'wasds' principal name.
Stack Trace:
com.ascential.xmeta.exception.runtime.AuthenticationException: CWWIM4537E No principal is found from the 'wasds' principal name.
at com.ascential.acs.security.auth.impl.xmeta.XMetaAuthentication.login(XMetaAuthentication.java:43)
at com.ascential.xmeta.util.AuthenticationUtils.doLogin(AuthenticationUtils.java:60)
at com.ascential.xmeta.client.repository.command.CleanupAbandonedLocksCommand.executeCommand(CleanupAbandonedLocksCommand.java:162)
at com.ascential.xmeta.client.repository.command.CleanupAbandonedLocksCommand.main(CleanupAbandonedLocksCommand.java:100)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:228)
Caused by: com.ibm.websphere.security.auth.WSLoginFailedException: CWWIM4537E No principal is found from the 'wasds' principal name.
at com.ibm.ws.security.server.SecurityServerImpl.simple_authenticate(SecurityServerImpl.java:375)
at com.ibm.ws.security.server._SecurityServerImpl_Tie.simple_authenticate(_SecurityServerImpl_Tie.java:116)
at com.ibm.ws.security.server._SecurityServerImpl_Tie._invoke(_SecurityServerImpl_Tie.java:93)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:669)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:523)
at com.ibm.rmi.iiop.ORB.process(ORB.java:523)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1575)
at com.ibm.rmi.iiop.Connection.doRequestWork(Connection.java:3039)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2922)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:64)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1691)

Posted: Tue Nov 03, 2015 6:41 pm
by ray.wurlod
What is "wasds" on your system?

Posted: Tue Nov 03, 2015 7:04 pm
by raji33
Its the user name

Posted: Tue Nov 03, 2015 9:18 pm
by ray.wurlod
The originating cause is the WSLoginFailedException: it looks like this is not a valid user name or that the password provided with it was not successful.

If you are certain that both of those are genuine, research the possibility that the wasds user does not have the role(s) required to run cleanup_abandoned_locks.sh command.

Posted: Wed Nov 04, 2015 7:29 am
by raji33
When we tried log in using the same username and password on Aix server we can able to but while executing the script when providing the same user we were unable to. My question is if the user is locked/password incorrect it shouldnt allow us to get in on the server.

Posted: Wed Nov 04, 2015 3:34 pm
by ray.wurlod
That you can log in to AIX may be irrelevant. Which user registry does the login and security service for Information Server use?