Created 06-10-2016 02:16 PM
Hi,
I am not able to open http://ec2-52-58-222-207.eu-central-1.compute.amazonaws.com:3000 URL using my browser. I am using pre built image of AMI having cloudbreak installed in AWS. so what could be reason for this? I open the port 3000 while launching EC2 instances
Created 06-10-2016 02:27 PM
You should have these ports open (as per the documentation) - also what's in your Profile (PUBLIC_IP/PRIVATE_ID)
Created 06-10-2016 02:27 PM
You should have these ports open (as per the documentation) - also what's in your Profile (PUBLIC_IP/PRIVATE_ID)
Created on 06-10-2016 02:36 PM - edited 08-19-2019 02:16 AM
I am using PUBLIC_IP and also inserted AWS access key ID and SECRET key..
Still I am not able to access it..
Created 06-10-2016 04:09 PM
Can you please SSH to the box and run docker ps and send us the results. Also can you check if you see any exceptions in cbd logs cloudbreak ?
Created 06-10-2016 06:00 PM
Docker ps :
[cloudbreak@ip-172-31-8-58 cloudbreak-deployment]$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 395eb179af7c sequenceiq/uaa:2.7.1 "/tmp/run.sh" About a minute ago Up About a minute 0.0.0.0:8089->8080/tcp cbreak_identity_1 a6df032bbc09 sequenceiq/socat:1.0.0 "socat -u TCP-LISTEN:" About a minute ago Up About a minute 0.0.0.0:32770->3333/tcp cbreak_logsink_1 f6bf112dbbe5 hortonworks/cloudbreak-auth:1.2.6 "/sultans/start-docke" About a minute ago Up About a minute 3001/tcp, 0.0.0.0:3001->3000/tcp cbreak_sultans_1 bee65b8146d3 gliderlabs/registrator:v5 "/bin/registrator con" 2 minutes ago Up 2 minutes cbreak_registrator_1 bc78688e46a7 gliderlabs/consul-server:0.5 "/bin/consul agent -s" 2 minutes ago Up 2 minutes 0.0.0.0:8400->8400/tcp, 8300-8302/tcp, 8301-8302/udp, 0.0.0.0:8500->8500/tcp, 8600/tcp, 172.17.0.1:53->8600/udp cbreak_consul_1 414af0947616 hortonworks/cloudbreak-web:1.2.6 "/uluwatu/start-docke" 2 minutes ago Up 2 minutes 0.0.0.0:3000->3000/tcp cbreak_uluwatu_1 00a40c24f3b1 sequenceiq/haveged:1.1 "haveged -F" 2 minutes ago Up 2 minutes cbreak_haveged_1
yes I am getting error while running cbd logs cloudbreak.. what could be probale issue for this?
cbd logs cloudbreak:
cloudbreak_1 | Caused by: org.springframework.beans.factory.BeanCreationExceptio n: Error creating bean with name '(inner bean)#5d6bf4c': Cannot resolve referenc e to bean 'entityManagerFactory' while setting constructor argument; nested exce ption is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'databaseUpMigration' defined in class path resource [com/sequen ceiq/cloudbreak/conf/DatabaseMigrationConfig.class]: Bean instantiation via fact ory method failed; nested exception is org.springframework.beans.BeanInstantiati onException: Failed to instantiate [org.apache.ibatis.migration.operations.UpOpe ration]: Factory method 'databaseUpMigration' threw exception; nested exception is org.apache.ibatis.migration.MigrationException: Error executing command. Cau se: org.apache.ibatis.migration.MigrationException: Could not create SqlRunner. Cause: org.postgresql.util.PSQLException: Connection refused. Check that the hos tname and port are correct and that the postmaster is accepting TCP/IP connectio ns. cloudbreak_1 | at org.springframework.beans.factory.support.BeanDefinitionValue Resolver.resolveReference(BeanDefinitionValueResolver.java:359) cloudbreak_1 | at org.springframework.beans.factory.support.BeanDefinitionValue Resolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:108) cloudbreak_1 | at org.springframework.beans.factory.support.ConstructorResolver .resolveConstructorArguments(ConstructorResolver.java:634) cloudbreak_1 | at org.springframework.beans.factory.support.ConstructorResolver .instantiateUsingFactoryMethod(ConstructorResolver.java:444) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractAutowireCap ableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory .java:1123) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractAutowireCap ableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1018) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractAutowireCap ableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:510) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractAutowireCap ableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482) cloudbreak_1 | at org.springframework.beans.factory.support.BeanDefinitionValue Resolver.resolveInnerBean(BeanDefinitionValueResolver.java:299) cloudbreak_1 | ... 127 more cloudbreak_1 | Caused by: org.springframework.beans.factory.BeanCreationExceptio n: Error creating bean with name 'databaseUpMigration' defined in class path res ource [com/sequenceiq/cloudbreak/conf/DatabaseMigrationConfig.class]: Bean insta ntiation via factory method failed; nested exception is org.springframework.bean s.BeanInstantiationException: Failed to instantiate [org.apache.ibatis.migration .operations.UpOperation]: Factory method 'databaseUpMigration' threw exception; nested exception is org.apache.ibatis.migration.MigrationException: Error execut ing command. Cause: org.apache.ibatis.migration.MigrationException: Could not c reate SqlRunner. Cause: org.postgresql.util.PSQLException: Connection refused. C heck that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. cloudbreak_1 | at org.springframework.beans.factory.support.ConstructorResolver .instantiateUsingFactoryMethod(ConstructorResolver.java:599) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractAutowireCap ableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory .java:1123) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractAutowireCap ableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1018) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractAutowireCap ableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:510) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractAutowireCap ableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractBeanFactory $1.getObject(AbstractBeanFactory.java:306) cloudbreak_1 | at org.springframework.beans.factory.support.DefaultSingletonBea nRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractBeanFactory .doGetBean(AbstractBeanFactory.java:302) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractBeanFactory .getBean(AbstractBeanFactory.java:197) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractBeanFactory .doGetBean(AbstractBeanFactory.java:296) cloudbreak_1 | at org.springframework.beans.factory.support.AbstractBeanFactory .getBean(AbstractBeanFactory.java:197) cloudbreak_1 | at org.springframework.beans.factory.support.BeanDefinitionValue Resolver.resolveReference(BeanDefinitionValueResolver.java:351) cloudbreak_1 | ... 135 more cloudbreak_1 | Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apache.ibatis.migration.operations.UpOperation]: Fact ory method 'databaseUpMigration' threw exception; nested exception is org.apache .ibatis.migration.MigrationException: Error executing command. Cause: org.apach e.ibatis.migration.MigrationException: Could not create SqlRunner. Cause: org.po stgresql.util.PSQLException: Connection refused. Check that the hostname and por t are correct and that the postmaster is accepting TCP/IP connections. cloudbreak_1 | at org.springframework.beans.factory.support.SimpleInstantiation Strategy.instantiate(SimpleInstantiationStrategy.java:189) cloudbreak_1 | at org.springframework.beans.factory.support.ConstructorResolver .instantiateUsingFactoryMethod(ConstructorResolver.java:588) cloudbreak_1 | ... 146 more cloudbreak_1 | Caused by: org.apache.ibatis.migration.MigrationException: Error executing command. Cause: org.apache.ibatis.migration.MigrationException: Could not create SqlRunner. Cause: org.postgresql.util.PSQLException: Connection refu sed. Check that the hostname and port are correct and that the postmaster is acc epting TCP/IP connections. cloudbreak_1 | at org.apache.ibatis.migration.operations.UpOperation.operate(Up Operation.java:64) cloudbreak_1 | at com.sequenceiq.cloudbreak.conf.DatabaseMigrationConfig.databa seUpMigration(DatabaseMigrationConfig.java:57) cloudbreak_1 | at com.sequenceiq.cloudbreak.conf.DatabaseMigrationConfig$Enhan cerBySpringCGLIB$30f187ab.CGLIB$databaseUpMigration$2(<generated>) cloudbreak_1 | at com.sequenceiq.cloudbreak.conf.DatabaseMigrationConfig$Enhan cerBySpringCGLIB$30f187ab$FastClassBySpringCGLIB$31a6508a.invoke(<generated>) cloudbreak_1 | at org.springframework.cglib.proxy.MethodProxy.invokeSuper(Metho dProxy.java:228) cloudbreak_1 | at org.springframework.context.annotation.ConfigurationClassEnha ncer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:355) cloudbreak_1 | at com.sequenceiq.cloudbreak.conf.DatabaseMigrationConfig$Enhan cerBySpringCGLIB$30f187ab.databaseUpMigration(<generated>) cloudbreak_1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) cloudbreak_1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:62) cloudbreak_1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:43) cloudbreak_1 | at java.lang.reflect.Method.invoke(Method.java:498) cloudbreak_1 | at org.springframework.beans.factory.support.SimpleInstantiation Strategy.instantiate(SimpleInstantiationStrategy.java:162) cloudbreak_1 | ... 147 more cloudbreak_1 | Caused by: org.apache.ibatis.migration.MigrationException: Could not create SqlRunner. Cause: org.postgresql.util.PSQLException: Connection refus ed. Check that the hostname and port are correct and that the postmaster is acce pting TCP/IP connections. cloudbreak_1 | at org.apache.ibatis.migration.operations.DatabaseOperation.getS qlRunner(DatabaseOperation.java:76) cloudbreak_1 | at org.apache.ibatis.migration.operations.DatabaseOperation.chan gelogExists(DatabaseOperation.java:61) cloudbreak_1 | at org.apache.ibatis.migration.operations.UpOperation.operate(Up Operation.java:38) cloudbreak_1 | ... 158 more cloudbreak_1 | Caused by: org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepti ng TCP/IP connections. cloudbreak_1 | at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionIm pl(ConnectionFactoryImpl.java:207) cloudbreak_1 | at org.postgresql.core.ConnectionFactory.openConnection(Connecti onFactory.java:64) cloudbreak_1 | at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJ dbc2Connection.java:138) cloudbreak_1 | at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJ dbc3Connection.java:29) cloudbreak_1 | at org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(Abstrac tJdbc3gConnection.java:21) cloudbreak_1 | at org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJ dbc4Connection.java:31) cloudbreak_1 | at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.j ava:24) cloudbreak_1 | at org.postgresql.Driver.makeConnection(Driver.java:410) cloudbreak_1 | at org.postgresql.Driver.connect(Driver.java:280) cloudbreak_1 | at org.springframework.jdbc.datasource.SimpleDriverDataSource.ge tConnectionFromDriver(SimpleDriverDataSource.java:140) cloudbreak_1 | at org.springframework.jdbc.datasource.AbstractDriverBasedDataSo urce.getConnectionFromDriver(AbstractDriverBasedDataSource.java:155) cloudbreak_1 | at org.springframework.jdbc.datasource.AbstractDriverBasedDataSo urce.getConnection(AbstractDriverBasedDataSource.java:120) cloudbreak_1 | at org.apache.ibatis.migration.DataSourceConnectionProvider.getC onnection(DataSourceConnectionProvider.java:19) cloudbreak_1 | at org.apache.ibatis.migration.operations.DatabaseOperation.getS qlRunner(DatabaseOperation.java:74) cloudbreak_1 | ... 160 more cloudbreak_1 | Caused by: java.net.ConnectException: Connection refused cloudbreak_1 | at java.net.PlainSocketImpl.socketConnect(Native Method) cloudbreak_1 | at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocke tImpl.java:350) cloudbreak_1 | at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPla inSocketImpl.java:206) cloudbreak_1 | at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketI mpl.java:188) cloudbreak_1 | at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) cloudbreak_1 | at java.net.Socket.connect(Socket.java:589) cloudbreak_1 | at java.net.Socket.connect(Socket.java:538) cloudbreak_1 | at org.postgresql.core.PGStream.<init>(PGStream.java:60) cloudbreak_1 | at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionIm pl(ConnectionFactoryImpl.java:101) cloudbreak_1 | ... 173 more
Created 06-10-2016 06:12 PM
It's not so easy to read over the formatting but apparently a few containers did not start for you (e.g. uaadb, pcdb, cbdb). Can you do a cbd kill and after a cbd regenerate a cbd start. You should have 12 containers (microservices) and among those the databases.
Created 06-13-2016 12:35 PM
Hi Janos,
I have done. I can see login page but I could able to login and see the next page.
I have typed cbd ps and got this result. do you have any idea what could be problem?
Created 06-13-2016 01:26 PM
Hey thanks.. I just increased my machine instances capacity and choose large machine and now I am able to enter into page using username but I am getting this new error . Do you have any idea about this?
6/13/2016 3:23:32 PM aram12 - create in progress: Creating infrastructure6/13/2016 3:23:49 PM aram12 - update in progress: Infrastructure creation failed. Reason: com.sequenceiq.cloudbreak.cloud.exception.CloudConnectorException: AWS CloudFormation stack reached an error state: CREATE_FAILED reason: API: ec2:CreateVpc You are not authorized to perform this operation.6/13/2016 3:23:49 PM aram12 - create failed: Infrastructure creation failed. Reason: com.sequenceiq.cloudbreak.cloud.exception.CloudConnectorException: AWS CloudFormation stack reached an error state: CREATE_FAILED reason: API: ec2:CreateVpc You are not authorized to perform this operation.
Created 06-13-2016 03:38 PM
It seams like your account does not have right to create a VPC (you can check this on AWS console where you can try to create a new VPC). Alternatively you can reuse your company's VPC as well - http://sequenceiq.com/cloudbreak-docs/latest/aws/#infrastructure-templates and check Create a new subnet in an existing VPC or Use an existing subnet in an existing VPC.
Created 06-14-2016 01:41 PM
Thanks Janos.. Its working perfectly fine. I have used existing subnet for creating clusters. Thanks 🙂