5 Replies Latest reply: Apr 8, 2012 11:57 PM by 866404 RSS

    server starting problem

    915353
      [sreekanth@sreekanth10 security]$ cd ../../../

      [sreekanth@sreekanth10 bin]$ ls
      Admin.log icicimng1-2.sh nodemanager setDomainEnv.sh startWebLogic.sh
      Admin.sh mng1.log server_migration startManagedWebLogic.sh stopManagedWebLogic.sh
      icicimng1-1.sh mng2.log service_migration startPointBaseConsole.sh stopWebLogic.sh
      [sreekanth@sreekanth10 bin]$ ./icicimng1-2.sh
      [sreekanth@sreekanth10 bin]$ tail -f mng2.log
      * server administration, use the WebLogic Server *
      * console at http://hostname:port/console *
      ***************************************************
      starting weblogic with Java version:
      java version "1.6.0_05"
      Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
      Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
      Starting WLS with line:
      /home/sreekanth/bea_icici/jdk160_05/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dweblogic.security.SSL.trustedCAKeyStore=/home/sreekanth/bea_icici/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/home/sreekanth/bea_icici/wlserver_10.3 -Dwls.home=/home/sreekanth/bea_icici/wlserver_10.3/server -Dweblogic.home=/home/sreekanth/bea_icici/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/sreekanth/bea_icici/patch_wls1030/profiles/default/sysext_manifest_classpath:/home/sreekanth/bea_icici/patch_cie660/profiles/default/sysext_manifest_classpath -Xverify:none -da -Dplatform.home=/home/sreekanth/bea_icici/wlserver_10.3 -Dwls.home=/home/sreekanth/bea_icici/wlserver_10.3/server -Dweblogic.home=/home/sreekanth/bea_icici/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=Admin_Url -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/sreekanth/bea_icici/patch_wls1030/profiles/default/sysext_manifest_classpath:/home/sreekanth/bea_icici/patch_cie660/profiles/default/sysext_manifest_classpath -Dweblogic.Name=icicimng1-2 -Djava.security.policy=/home/sreekanth/bea_icici/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
      <Apr 7, 2012 1:27:57 PM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
      <Apr 7, 2012 1:28:42 PM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
      <Apr 7, 2012 1:28:43 PM GMT+05:30> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://Admin_Url.>
      <Apr 7, 2012 1:28:43 PM GMT+05:30> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
      <Apr 7, 2012 1:28:43 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
      <Apr 7, 2012 1:28:43 PM GMT+05:30> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
      <Apr 7, 2012 1:28:43 PM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file /home/sreekanth/bea_icici/user_projects/domains/icici_domain/servers/icicimng1-2/logs/icicimng1-2.log is opened. All server side log events will be written to this file.>
      <Apr 7, 2012 1:28:44 PM GMT+05:30> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters..
      weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
           at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unknown Source)
           at weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
           at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(Unknown Source)
           at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(Unknown Source)
           at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(Unknown Source)
           Truncated. see log file for complete stacktrace
      com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
           at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
           at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
           at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
           at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
           at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unknown Source)
           Truncated. see log file for complete stacktrace
      com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
           at com.bea.common.ldap.properties.LDAPStoreServicePropertiesConfigurator.convertStoreProperties(LDAPStoreServicePropertiesConfigurator.java:53)
           at com.bea.common.security.internal.service.StoreServiceImpl.initJDOProperties(StoreServiceImpl.java:101)
           at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:73)
           at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
           at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
           Truncated. see log file for complete stacktrace
      >
      <Apr 7, 2012 1:28:44 PM GMT+05:30> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
      <Apr 7, 2012 1:28:44 PM GMT+05:30> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

      There are 1 nested errors:

      weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
           at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
           at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
           at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
           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)

      >
      <Apr 7, 2012 1:28:44 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
      <Apr 7, 2012 1:28:44 PM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
      <Apr 7, 2012 1:28:44 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
      ^C
      [sreekanth@sreekanth10 bin]$



      please any one help me
        • 1. Re: server starting problem
          jmft2012
          start AdminServer first, then the Managed Server
          • 2. Re: server starting problem
            915353
            Hi

            Here the Admin server is already Running . IN My environment 1 Admin Server And 3 manage servers . I write the wrapperscripts for all the server.
            Before writeing the wrapperscripts server are all successfully running but when i am creating the scripts Admin server has running normally and one Managed Server running normally . But when we r starting the second server the above error has occured.

            PLease reply
            • 3. Re: server starting problem
              jmft2012
              <Apr 7, 2012 1:28:43 PM GMT+05:30> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://Admin_Url.>

              you should have looked into above msg's implication I meant.
              • 4. Re: server starting problem
                866404
                Hi,

                Kill the process, and restart ADMIN again and then Managed Servers. Looks like your admin server didnt come up properly.

                If still you are not able to start the server then check you host is configured or not in /etc/hosts file. If you can not ping yourself you can fix that in several ways.

                Add an entry in /etc/hosts with your hostname
                Add a DNS entry in your DNS



                Thanks,
                Sujit
                • 5. Re: server starting problem
                  Arunbodap-Oracle
                  It looks like the admin URL that you have used in your wrapper scripts might have caused the issue.

                  Please check the admin URL and understand why admin server is nor reachable with that URL. If you have used "localhost" as your hostname, it is the one causing the problem when you start managed servers on other machines.
                  If you are not using localhost, then I suggest that you ping the IP/DNS you have used in the admin URL from the machine where you are starting the managed server.
                  Make sure the adminserver is running on the URL used.

                  This might be the first time you are starting the managed server on that machine, so that is why it would need to have the admin server up and running to setup the LDAP and security settings initially.

                  So, check the admin URL as well as ensure that you are able to access the console using the same admin URL, before trying to start your managed server.


                  Arun

                  Edited by: ArunBodap on Apr 8, 2012 9:58 PM