06-21-2017 10:12 AM - edited 03-21-2019 11:27 AM
I've deployed a non-HA buildout of CloudCenter v4.8 using vSphere appliances. Everything is deployed.
Problem: During initial VMware private cloud config, I am unable to connect to Orchestrator. When I try to add CCO, I get "Error while communicating with Orchestrator" error.
Anyone have any ideas on this? Thanks in advance!
06-21-2017 11:36 AM
In my OSMOSIX.log from the CCM server, I'm seeing the following error:
"org.apache.http.conn.HttpHostHostConnectException: Connect to 10.145.1.43:8443 [/10.145.1.43] failed: Connection refused (Connection refused)"
So, 10.145.1.43 is the IP of my CCO appliance. Does the format of the message indicate problem with the way I configured AMQP or CCO?
Thanks so much!
06-21-2017 01:47 PM
HI Tristan,
I would be more interested to review the CCO osmosix log. I suspect you might see some exception in the CCO logs which says that CCO is not connected to AMQP.
If you see the error/exception related to AMQP in CCO logs, I would say to please restart the rabbitmq service on AMQP and then tomcat service on CCO, following with tomcat service restart on CCM machine which should help in fixing the issue.
Please let me know if that helps.
Best Regards,
Deepak Sukhiya
06-21-2017 03:50 PM
Thanks Deepak! I've pulled the osmosix log and am going through it now.
Just curious - is there a particular boot order for the non-HA environment? Does it matter in what order I boot, CCM, CCO, MON, and AMQP appliances?
I'll let you know how I get on...
06-29-2017 10:53 AM
Hi Tristan,
Following is the startup and shutdown sequence of the CloudCenter stack:
Startup:
1. AMQP
2. CCO
3 MON
4. CCM
Shutdown:
1. CCM
2. MON
3. CCO
4. AMQP
The above sequence is applicable for both HA and Non-HA environment.
Please let me know in case of any further questions.
Best Regards,
Deepak Sukhiya
08-13-2017 07:16 AM
Hi Deepak, if in HA and version 4.8,
this would be the order?
AMQP
CCO
MON
CCM_DB
CCM
CCM
CCM_DB
MON
CCO
AMQP
Also, where would the repo server fit into this?
thanks
08-13-2017 09:12 PM
Hi Sebastian,
This is correct!
Thanks,
Deepak
08-14-2017 05:26 AM
where would the repo server fit into this?
> It is not necessary to shut down the repo server as it is a
Thanks
Vihar K
10-24-2017 05:37 AM
02-01-2018 09:44 AM
Did you get a resolution to this? I have same problem. Version 4.8.2. No-HA. CCO, AMQP, CCM all configured correctly. CCO is accessible. Ran all network tests. all passed.
02-01-2018 08:41 PM
Hi mwerne01,
Just check whether AMQP can list CCO IP. Enter rabbitmqctl list-connections command on AMQP. It will list CCO IP address. If not reboot again and see.
Regards,
Sheriff
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide