6 Replies Latest reply on Sep 26, 2013 4:22 AM by de3db5ed-485c-438c-ae02-35d12ea2134d

    Unable to Start the Managed Server - Urgent

    de3db5ed-485c-438c-ae02-35d12ea2134d

      I have created a Admin Server(7044) domain and i am able to login in the server. Later User has requested to create the cluster, so i have created new server(WSMS1 - 8044) and new Cluster. For the Cluster i have given the admin port(7044) and i targeted the existed data source also but currently i am not able to start the Managed server by using the following command in putty - "./startManagedWeblogic.sh WSMS1 http://localhost:8044". For your information there is another domain(Created by other person) have same configuration and it's working fine.

       

      Please help.

        • 1. Re: Unable to Start the Managed Server - Urgent
          de3db5ed-485c-438c-ae02-35d12ea2134d

          For more information, when i tried to start the managed server by using following commend "./startManagedWeblogic.sh WSMS1 http://localhost:8044" - it is asking the Username and password, so i am providing the same what i given for adim server, but it's not authenticating ..

          • 2. Re: Unable to Start the Managed Server - Urgent
            Fabian

            Could you paste the last 10-15 lines from your logs ie after excuting "./startManagedWeblogic.sh WSMS1 http://localhost:8044" and then entering the username and password.

            1 person found this helpful
            • 3. Re: Unable to Start the Managed Server - Urgent
              de3db5ed-485c-438c-ae02-35d12ea2134d

              Please check.

               

              Enter username to boot WebLogic server:weblogic

              Enter password to boot WebLogic server:

              <Sep 24, 2013 6:58:56 PM WIT> <Info> <Management> <BEA-141107> <Version: WebLogic

              Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >

              <Sep 24, 2013 6:59:10 PM WIT> <Emergency> <Management> <BEA-141151> <The admin

              server could not be reached at http://10.87.1.179:8044.>

              <Sep 24, 2013 6:59:11 PM WIT> <Info> <Configuration Management> <BEA-150018> <This

              server is being started in managed server independence mode in the absence of the

              admin server.>

              <Sep 24, 2013 6:59:11 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state

              changed to STARTING>

              <Sep 24, 2013 6:59:11 PM WIT> <Info> <WorkManager> <BEA-002900> <Initializing

              self-tuning thread pool>

              <Sep 24, 2013 6:59:15 PM WIT> <Notice> <Log Management> <BEA-170019> <The server log

              file

              /home/Oracle/Middleware/user_projects/domains/AmlockWebService/servers/wsms1/logs/wsms1.log

              is opened. All server side log events will be written to this file.>

              <Sep 24, 2013 6:59:32 PM WIT> <Notice> <Security> <BEA-090082> <Security

              initializing using security realm myrealm.>

              <Sep 24, 2013 6:59:33 PM WIT> <Critical> <Security> <BEA-090403> <Authentication for

              user weblogic denied>

              <Sep 24, 2013 6:59:33 PM WIT> <Critical> <WebLogicServer> <BEA-000386> <Server

              subsystem failed. Reason: weblogic.security.SecurityInitializationException:

              Authentication for user weblogic denied

              weblogic.security.SecurityInitializationException: Authentication for user weblogic

              denied

                at

              weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)

                at

              weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)

                at

              weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)

                at weblogic.security.SecurityService.start(SecurityService.java:141)

                at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

                Truncated. see log file for complete stacktrace

              Caused By: javax.security.auth.login.FailedLoginException:

              [Security:090303]Authentication Failed: User weblogic

              weblogic.security.providers.authentication.LDAPAtnDelegateException:

              [Security:090295]caught unexpected exception

                at

              weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)

                at

              com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)

                at

              com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at

              sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                Truncated. see log file for complete stacktrace

              >

              <Sep 24, 2013 6:59:33 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state

              changed to FAILED>

              <Sep 24, 2013 6:59:33 PM WIT> <Error> <WebLogicServer> <BEA-000383> <A critical

              service failed. The server will shut itself down>

              <Sep 24, 2013 6:59:33 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state

              changed to FORCE_SHUTTING_DOWN>

              • 4. Re: Unable to Start the Managed Server - Urgent
                Fabian

                For starting Managed Server use the below command

                ./startManagedWebLogic.sh managed_server_name admin_url (UNIX)

                 

                In your case

                ./startManagedWeblogic.sh WSMS1 http://localhost:7044/

                Better to use Ip Address of the server instead typing local host

                • 5. Re: Unable to Start the Managed Server - Urgent
                  de3db5ed-485c-438c-ae02-35d12ea2134d

                  Thank you very much Fabian,

                   

                  By using the following syntax./startManagedWebLogic.sh managed_server_name admin_url (UNIX)" , the server has started but my application is not connecting if i tried to connect from 8044 port.

                   

                  I have targeted Admin Server and Cluster to the data source but still it is not working.

                   

                  Please advise.

                  • 6. Re: Unable to Start the Managed Server - Urgent
                    de3db5ed-485c-438c-ae02-35d12ea2134d

                    I just re-deployed the WAR and it is working fine now... Thanks you very much