Kartheek
Explorer

Re: Cloudbreak stuck in creating AWS HDF Cluster

by Explorer in Support Questions
‎06-25-2019 03:57 PM
‎06-25-2019 03:57 PM
The status of the cluster creation has not changed and it's been like that for over 2 days. I am thinking the issue is the proxy setup but not sure where the issues could be since cloudbreak was able to install on the VM and was able to contact aws to create the servers. ... View more

Re: Cloudbreak unable to connect to Nginx

by Explorer in Support Questions
‎06-25-2019 03:56 PM
‎06-25-2019 03:56 PM
The status of the cluster creation has not changed and it's been like that for over 2 days. I am thinking the issue is the proxy setup but not sure where the issues could be since cloudbreak was able to install on the VM and was able to contact aws to create the servers. ... View more

Re: Cloudbreak unable to connect to Nginx

by Explorer in Support Questions
‎06-24-2019 05:26 PM
‎06-24-2019 05:26 PM
AWS is showing the servers as up and running. I was able to ssh to them from the cloudbreak VM as well but the cloudbreak UI is only showing status as "create in progress". The last even history message was "Infrastructure metadata collection finished" I checked cloudbreak logs and there are no errors in it. I see the below message repeated over and over again. 2019-06-24 15:48:43,800 [scheduledExecutor-1] distributeFlows:166 INFO  c.s.c.s.h.HeartbeatService - [owner:spring] [type:springLog] [id:] [name:] [flow:] [tracking:] Active CB nodes: (1)[[CloudbreakNode{uuid='52c98d7e-a196-4ec1-8378-5b8adfc2f83a', lastUpdated=1561391310002}]], failed CB nodes: (0)[[]] 2019-06-24 15:48:52,221 [http-nio-8080-exec-8] <init>:57 INFO  c.s.c.f.MDCContextFilter - [owner:spring] [type:springLog] [id:] [name:] [flow:] [tracking:] No trackingId in request. Adding trackingId: 'f4e52ca0-73af-4f94-98a6-16093895beb8' 2019-06-24 15:48:52,224 [http-nio-8080-exec-8] getAllForAutoscale:311 INFO  c.s.c.s.StackCommonService - [owner:undefined] [type:Autoscale] [id:] [name:] [flow:] [tracking:f4e52ca0-73af-4f94-98a6-16093895beb8] Get all stack, autoscale authorized only. 2019-06-24 15:49:00,004 [scheduledExecutor-2] cancelInvalidFlows:221 INFO  c.s.c.s.h.HeartbeatService - [owner:spring] [type:springLog] [id:] [name:] [flow:] [tracking:] Check if there are termination flows for the following stack ids: [9] 2019-06-24 15:49:02,221 [http-nio-8080-exec-9] <init>:57 INFO  c.s.c.f.MDCContextFilter - [owner:spring] [type:springLog] [id:] [name:] [flow:] [tracking:] No trackingId in request. Adding trackingId: 'e335bdd8-7dfb-48ad-a697-fad696d923de' 2019-06-24 15:49:02,223 [http-nio-8080-exec-9] getAllForAutoscale:311 INFO  c.s.c.s.StackCommonService - [owner:undefined] [type:Autoscale] [id:] [name:] [flow:] [tracking:e335bdd8-7dfb-48ad-a697-fad696d923de] Get all stack, autoscale authorized only. ... View more

Cloudbreak stuck in creating AWS HDF Cluster

by Explorer in Support Questions
‎06-24-2019 05:26 PM
‎06-24-2019 05:26 PM
Trying to create a HDF cluster in AWS using cloudbreak but the process is stuck in "Create in Progress". AWS console show the servers are created and they up and running. Was able to ssh from cloudbreak VM so there are connectivity issues. Cloudbreak logs shows no errors. These messages repeat over and over again. Checked the Ambari server and nginx was up and running. 2019-06-24 16:50:02,992 [reactorDispatcher-85] pollWithTimeout:32 INFO  c.s.c.s.PollingService - [owner:e315477d-074c-4ed1-ad47-1367a19b0567] [type:STACK] [id:10] [name:data-ingestion-hdf-dev] [flow:21049f09-4326-4668-b391-8972b1dfeccd] [tracking:40e8f3bf-54ad-4cd0-9307-ca4179bd2886] Polling attempt 3. 2019-06-24 16:50:02,993 [reactorDispatcher-85] checkStatus:25 INFO  c.s.c.s.s.f.NginxCertListenerTask - [owner:e315477d-074c-4ed1-ad47-1367a19b0567] [type:STACK] [id:10] [name:data-ingestion-hdf-dev] [flow:21049f09-4326-4668-b391-8972b1dfeccd] [tracking:40e8f3bf-54ad-4cd0-9307-ca4179bd2886] Check if nginx is running on 130.x.xx.xx:9443. 2019-06-24 16:50:12,274 [http-nio-8080-exec-8] <init>:57 INFO  c.s.c.f.MDCContextFilter - [owner:spring] [type:springLog] [id:] [name:] [flow:] [tracking:] No trackingId in request. Adding trackingId: '1d7362b4-ad15-46ee-8c6e-06ccb4ad86d4' 2019-06-24 16:50:12,276 [http-nio-8080-exec-8] getAllForAutoscale:311 INFO  c.s.c.s.StackCommonService - [owner:undefined] [type:Autoscale] [id:] [name:] [flow:] [tracking:1d7362b4-ad15-46ee-8c6e-06ccb4ad86d4] Get all stack, autoscale authorized only. 2019-06-24 16:50:14,357 [scheduledExecutor-1] distributeFlows:166 INFO  c.s.c.s.h.HeartbeatService - [owner:spring] [type:springLog] [id:] [name:] [flow:] [tracking:] Active CB nodes: (1)[[CloudbreakNode{uuid='52c98d7e-a196-4ec1-8378-5b8adfc2f83a', lastUpdated=1561395000002}]], failed CB nodes: (0)[[]] 2019-06-24 16:50:22,273 [http-nio-8080-exec-13] <init>:57 INFO  c.s.c.f.MDCContextFilter - [owner:spring] [type:springLog] [id:] [name:] [flow:] [tracking:] No trackingId in request. Adding trackingId: '71f18ec4-a5e4-4307-8fca-e6766fd8f6e6' 2019-06-24 16:50:22,275 [http-nio-8080-exec-13] getAllForAutoscale:311 INFO  c.s.c.s.StackCommonService - [owner:undefined] [type:Autoscale] [id:] [name:] [flow:] [tracking:71f18ec4-a5e4-4307-8fca-e6766fd8f6e6] Get all stack, autoscale authorized only. ... View more

Re: Cloudbreak unable to connect to Nginx

by Explorer in Support Questions
‎06-24-2019 04:54 PM
‎06-24-2019 04:54 PM
The server are up and running but cloudbreak is not able to poll them. The connection from VM to server is working as I was able to SSH to them from the VM. AWS console shows the server are configured and are running properly. But the cloudbreak UI just shows "Create in progress" status. ... View more

Cloudbreak unable to connect to Nginx

by Explorer in Support Questions
‎06-21-2019 04:13 PM
‎06-21-2019 04:13 PM
Trying to create a HDF cluster using cloudbreak but the creation process is stuck at step Infrastructure metadata collection finished. When checking the cloudbreak logs saw the below: 2019-06-21 15:34:36,443 [reactorDispatcher-57] pollWithTimeout:32 INFO c.s.c.s.PollingService - [owner:e315477d-074c-4ed1-ad47-1367a19b0567] [type:STACK] [id:5] [name:dv-data-ingestion-hdf-dev] [flow:7ed0ed96-2d9b-47c5-8f3d-fa8fd91a5049] [tracking:8454d361-1d3c-4e7b-9b03-c9184450d47a] Polling attempt 35. 2019-06-21 15:34:36,445 [reactorDispatcher-57] checkStatus:25 INFO c.s.c.s.s.f.NginxCertListenerTask - [owner:e315477d-074c-4ed1-ad47-1367a19b0567] [type:STACK] [id:5] [name:dv-data-ingestion-hdf-dev] [flow:7ed0ed96-2d9b-47c5-8f3d-fa8fd91a5049] [tracking:8454d361-1d3c-4e7b-9b03-c9184450d47a] Check if nginx is running on 130.6.234.168:9443. I checked and the cloudbreak VM is able to connect to the Ambari server and nginx is running on the server. Nginx error logs shows this: 2019/06/21 15:33:16 [error] 4913#0: *16 connect() failed (111: Connection refused) while connecting to upstream, client: 135.28.27.13, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "130.6.234.168", referrer: "https://130.6.234.168/ambari/" ... View more
Contact Me
Online
Offline
Last Visited
‎02-12-2021 05:57 AM
Public Statistics
Date Registered ‎06-21-2019 03:30 PM
Last Visited ‎02-12-2021 05:57 AM
Total Messages Posted 7