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.
[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-> 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
blasadmin now running against deployment: nsh_proxy
bladmin:nsh_proxy>set appserver ProxySvcPort 9842
bladmin:nsh_proxy>set appserver PwdStore file
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
[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.