5 Replies Latest reply on Aug 24, 2015 12:34 PM by Bill Robinson

    NSH_PROXY not starting due to conflict

      Greetings,

       

      I'm currently getting an error when standing up a host server containing a copy of each application server profile (configuration, nsh_proxy, job). We don't want to use the ALL profile to keep them broken apart for growth and load balancing. I'm wondering if anyone else has run into this error and their solution.

       

      from AppServerLauncher.log

      [21 Aug 2015 14:12:10,562] [main] [INFO] [::] [] Not starting Application Server: nsh_proxy and deployment name: nsh_proxy because it is in conflict with mydevhost.

       

      I'm trying to setup an HA environment where each host server is self contained then load balanced by an F5. DNS will point to the pool name which will contain enumerated pool members aliases (bsansh => bsansh1 (aliased to HOST1), bsansh2 (aliased to HOST2, etc.). I don't want to use the ALL profile as we'll likely be moving the Job server off to a separate bigger host later.

       

      This is the first profile created on the first host. I still have to make configuration and jobs App server profiles on this same host.

       

      myid@mydevhost-> sudo su -

      root@mydevhost-> su - bladmin

      bladmin@mydevhost-> pwd

      /opt/bmc/bladelogic/NSH/br

      bladmin@mydevhost-> ll deployments/bladelogic.keystore

      -rw-r--r--    1 bladmin  bladmin      2026 Jul 21 14:24 deployments/bladelogic.keystore

      bladmin@mydevhost-> blasadmin -s _template

      blasadmin now running against deployment: _template

      Bladelogic Admin Utility; Version 8.6.00.216.

      Copyright (c) 2001-2012 BladeLogic, Inc. All rights reserved.

      Type 'help' for Bladmin help.

      bladmin:_template>create NSH_PROXY 9800 NSH_PROXY

      bladmin:_template>switch nsh_proxy

      blasadmin now running against deployment: nsh_proxy

      bladmin:nsh_proxy>set appserver ProxySvcPort 9842

      bladmin:nsh_proxy>set appserver PwdStore file

      bladmin:nsh_proxy>quit

       

      bladmin@mydevhost-> logout

      root@mydevhost-> service blappserv restart

      Stopping BladeLogic AppServer ... OK

      Starting BladeLogic AppServer ... OK

       

      root@mydevhost-> service blprocserv restart

      Stopping BladeLogic ProcessSpawner ... OK

      Starting BladeLogic ProcessSpawner ... OK

       

      The Infrastructure Management's Application Server Profile has:

      ProxyServiceURLs as service:proxysvc.bladelogic:bless://mydevhost:9842

      ProxySvcPort as 9842

       

      from AppServerLauncher.log

      [21 Aug 2015 15:32:11,106] [main] [INFO] [::] [] Not starting Application Server: nsh_proxy and deployment name: nsh_proxy because it is in conflict with dl80131

      [21 Aug 2015 15:32:11,107] [main] [INFO] [::] [] Registering shutdown hook

      [21 Aug 2015 15:32:11,108] [main] [INFO] [::] [] Application server launcher started

      [21 Aug 2015 15:32:11,108] [main] [INFO] [::] [] Ready

      [21 Aug 2015 15:32:47,361] [Thread-4] [INFO] [::] [] Application server dl80131 has started successfully

      [21 Aug 2015 15:32:47,991] [RMI TCP Connection(5)-10.135.160.19] [INFO] [::] [] Connection accepted


      Thanks in advance. Cheers, Mark S.

        • 1. Re: NSH_PROXY not starting due to conflict
          Bill Robinson

          use a different base port range.  you can then go set the proxysvcport to 9842 on the proxy instance.  there are probably other ports conflicting between the two instances.

          • 2. Re: NSH_PROXY not starting due to conflict

            Thank you. As a follow up ...

             

            After issuing: service blappserv stop && service blprocserv stop

            is it matter of issuing: rm -rf /opt/bmc/bladelogic/NSH/br/deployments/nsh_proxy

            blasadmin help doesn't show a "delete" or "destroy" deployment command, only "create" ?

            • 3. Re: NSH_PROXY not starting due to conflict
              Bill Robinson

              Go into blasadmin and change the minport, maxport, registryport, jmxmanagement port for the nsh_proxy instance. instead of 98xx us 99xx or 101xx or something else that doesn’t conflict w/ the other instances.

              • 4. Re: NSH_PROXY not starting due to conflict

                Hi. Changing the ports per your suggestion didn't appear to have worked. After changing the specific AppServer and ManagementService port entries the AppServerLauncher.log error occurred again.

                 

                I then tarball'd and removed the existing deployment/nsh_proxy directory, re-ran the creation commands using: create nsh_proxy 9900 NSH_PROXY; switch nsh_proxy; appserver ProxySvcPort 9842; appserver PwdStore file;

                only to throw the error again after restart.


                 

                 

                bladmin@mydevhost-> blasadmin -s default show AppServer all | egrep -i "port|jmx|]"

                [AppServer]

                AppSvcPort:9841

                CLRProxyPort:0

                DaalPluginImportWaitTimeout:

                DisableIpv6SupportForSysInfo:

                HTTPProxyPort:

                HttpsIDRACPortNumber:4433

                HttpsPortNumber:9843

                JMXConnectionTimeout:20

                MaxJMXConnections:20

                MaxNumberOfDashboardReports:90

                MaxPort:9899

                MinPort:9850

                ProxySvcPort:9842

                RegistryPort:9836

                SSLPort:0

                 

                bladmin@mydevhost-> blasadmin -s default show ManagementService all | egrep -i "port|jmx|]"

                [ManagementService]

                JMXManagementPort:9838

                JmxNotificationLevel:finer

                 

                bladmin@mydevhost-> blasadmin -s nsh_proxy show AppServer all | egrep -i "port|jmx|]"

                [AppServer]

                AppSvcPort:

                CLRProxyPort:0

                DaalPluginImportWaitTimeout:

                DisableIpv6SupportForSysInfo:

                HTTPProxyPort:

                HttpsIDRACPortNumber:

                HttpsPortNumber:

                JMXConnectionTimeout:20

                MaxJMXConnections:20

                MaxNumberOfDashboardReports:90

                MaxPort:9999

                MinPort:9950

                ProxySvcPort:9842

                RegistryPort:9936

                SSLPort:

                bladmin@mydevhost-> blasadmin -s nsh_proxy show ManagementService all | egrep -i "port|jmx|]"

                [ManagementService]

                JMXManagementPort:9938

                JmxNotificationLevel:finer


                root@mydevhost-> iptables -L

                Chain INPUT (policy ACCEPT)

                target     prot opt source               destination

                 

                Chain FORWARD (policy ACCEPT)

                target     prot opt source               destination

                 

                Chain OUTPUT (policy ACCEPT)

                target     prot opt source               destination


                root@mydevhost-> service blappserv restart && service blprocserv restart

                Stopping BladeLogic AppServer ... OK

                Starting BladeLogic AppServer ... OK

                Stopping BladeLogic ProcessSpawner ... OK

                Starting BladeLogic ProcessSpawner ... OK

                 

                bladmin@mydevhost-> grep nsh_proxy AppServerLauncher.log

                [21 Aug 2015 16:47:55,567] [main] [INFO] [::] [] Not starting Application Server: nsh_proxy and deployment name: nsh_proxy because it is in conflict with mydevhost

                [21 Aug 2015 16:51:50,034] [main] [INFO] [::] [] Not starting Application Server: nsh_proxy and deployment name: nsh_proxy because it is in conflict with mydevhost

                [21 Aug 2015 16:59:02,937] [main] [INFO] [::] [] Not starting Application Server: nsh_proxy and deployment name: nsh_proxy because it is in conflict with mydevhost

                [21 Aug 2015 17:31:20,668] [main] [INFO] [::] [] Not starting Application Server: nsh_proxy and deployment name: nsh_proxy because it is in conflict with mydevhost

                • 5. Re: NSH_PROXY not starting due to conflict
                  Bill Robinson

                  the NSHProxySvcPort is the same for both instances.  that is the conflict.