1 Reply Latest reply: Apr 22, 2013 6:27 AM by 971162 RSS

    OES admin server not starting - User admin is not permitted to boot

    1001214
      Hi all,

      I am facing a very Critical issue below...need resolution ASAP, as Project delivery being impacted very badly. Highly appreciate any suggestions please.

      I removed the state.chk file from /ales32-admin/work/runtime (after taking its backup), to implement some policies and restarted the OES admin server.
      The OES admin server is not starting. The error details are given below.
      The OES server version is 10.1.4.3, patch cp6.

      --- Getting below error at linux prompt while starting the server using /oracle/mw/oes_10.1.4.3/ales32-admin/bin/WLESadmin.sh start ---

      Starting Oracle Entitlements Server Admin...
      Waiting for processes to initialize...
      Starting Oracle Entitlements Server WebLogic Server...
      Starting ALES WLS.sita-sns-admin.in.niit-tech.com...
      Waiting for server READY at url: https://sita-sns-admin.in.niit-

      tech.com:9003/services/ManagedServer.............................................................................................................................................
      .................................................................................................................................................................................
      .................................................................................................................................................................................
      ............................................................................................................failed.
      The requested action waitready to URL https://sita-sns-admin.in.niit-tech.com:9003/services/ManagedServer failed.
      2013-03-28 09:19:03,867 [Main Thread] ERROR com.bea.security.utils.ASISignal - java.rmi.RemoteException: Unable to wait for the server within 600 times
      Admin Console failed to start.

      Please make sure all the configuration are correct.

      ------------------- Error logs are as below -------------------------------

      ---system_console.log---

      2013-04-01 05:19:29,589 [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR com.bea.security.providers.authorization.asi.PatternClassLoader -
      Missing JAR file: /apps/sw/oracle/mw/oes_10.1.4.3/ales32-admin/lib/jdbc2_0-stdext.jar
      2013-04-01 05:19:29,994 [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR
      com.bea.security.providers.authorization.asi.AuthorizationProviderImpl - com.bea.security.providers.authorization.asi.InvocationException: ArmeNOTREADY Exception: Engine did not recieve initial policy
      2013-04-01 05:19:30,359 [Thread-18] WARN com.bea.security.ssl.axis.AxisClientSocketFactory - Error during SSL handshake; host: sita-sns-admin.in.niit-tech.com, port: 9,003.
      2013-04-01 05:28:19,878 [Main Thread] ERROR com.bea.security.utils.ASISignal - java.rmi.RemoteException: Unable to wait for the server within 600 times

      ---asiAdminServer.log---

      ####<Apr 1, 2013 5:19:29 AM UTC> <Error> <Security> <sita-sns-admin.in.niit-tech.com> <asiAdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1364793569994> <BEA-090060> <The AccessDecision class "com.bea.security.providers.authorization.asi.AuthorizationProviderStub" returned an error: com.bea.security.providers.authorization.asi.InvocationException: ArmeNOTREADY Exception: Engine did not recieve initial policy.>
      ####<Apr 1, 2013 5:19:30 AM UTC> <Critical> <Security> <sita-sns-admin.in.niit-tech.com> <asiAdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1364793570005> <BEA-090404> <User admin is not permitted to boot the server; The server policy may have changed in such a way that the user

      is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
      ####<Apr 1, 2013 5:19:30 AM UTC> <Critical> <WebLogicServer> <sita-sns-admin.in.niit-tech.com> <asiAdminServer> <WrapperStartStopAppMain> <<WLS Kernel>> <> <> <1364793570006>
      <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have
      changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the
      server policy definitions. weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
           at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1009)
           at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
           at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
           at weblogic.security.SecurityService.start(SecurityService.java:141)
           at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
           at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
           at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

      ---WLESWebLogic.wrapper.log---

      INFO | jvm 1 | 2013/04/01 05:19:29 | <Apr 1, 2013 5:19:29 AM UTC> <Notice> <Security> <BEA-090082> <Security initializing using security realm asiadmin.>
      INFO | jvm 1 | 2013/04/01 05:19:30 | <Apr 1, 2013 5:19:29 AM UTC> <Error> <Security> <BEA-090060> <The AccessDecision class
      "com.bea.security.providers.authorization.asi.AuthorizationProviderStub" returned an error: com.bea.security.providers.authorization.asi.InvocationException: ArmeNOTREADY
      Exception: Engine did not recieve initial policy.>
      INFO | jvm 1 | 2013/04/01 05:19:30 | <Apr 1, 2013 5:19:30 AM UTC> <Critical> <Security> <BEA-090404> <User admin is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to
      update the server policy definitions.>
      INFO | jvm 1 | 2013/04/01 05:19:30 | <Apr 1, 2013 5:19:30 AM UTC> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason:
      weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer
      able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
      INFO | jvm 1 | 2013/04/01 05:19:30 | weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed
      in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server
      policy definitions.
      INFO | jvm 1 | 2013/04/01 05:19:30 |      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization (CommonSecurityServiceManagerDelegateImpl.java:1009)
      INFO | jvm 1 | 2013/04/01 05:19:30 |      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize
      (CommonSecurityServiceManagerDelegateImpl.java:1050)
      INFO | jvm 1 | 2013/04/01 05:19:30 |      at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
      INFO | jvm 1 | 2013/04/01 05:19:30 |      at weblogic.security.SecurityService.start(SecurityService.java:141)
      INFO | jvm 1 | 2013/04/01 05:19:30 |      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      INFO | jvm 1 | 2013/04/01 05:19:30 |      Truncated. see log file for complete stacktrace
      INFO | jvm 1 | 2013/04/01 05:19:30 | >
      INFO | jvm 1 | 2013/04/01 05:19:30 | <Apr 1, 2013 5:19:30 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
      INFO | jvm 1 | 2013/04/01 05:19:30 | <Apr 1, 2013 5:19:30 AM UTC> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
      INFO | jvm 1 | 2013/04/01 05:19:30 | <Apr 1, 2013 5:19:30 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
      STATUS | wrapper | 2013/04/01 05:19:32 | <-- Wrapper Stopped

      Edited by: 998211 on Apr 4, 2013 11:59 PM

      Edited by: 998211 on Apr 5, 2013 12:00 AM

      Edited by: 998211 on Apr 5, 2013 12:01 AM