About peter_teunissen

peter_teunissen · ‎05-19-2017

@Jonathan Hurley: The error I'm getting in the Postfix log: warning: TLS library problem: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown:s3_pkt.c:1315:SSL alert number 46: The solution you suggest is exactly what I was looking for. I'll test and report back.

peter_teunissen · ‎05-19-2017

Currenlty, in my setup sending alert notification mails through SMTP with start TLS enabled fails due to a SSL peer verification error. I use a self signed certificate on the mail server and would like to disable SSL peer verification. Is there a property I could add to accomplish this?

peter_teunissen · ‎05-10-2017

That did the trick, thanks. Is it possible to give this new user the ability to admin existing users too?

peter_teunissen · ‎05-10-2017

I have a Cloudbreak 1.14.1 install up and running. A new user was added through the 'Sign up' link, but it appears that creates a completely new environment since that user can't see the existing clusters and doesn't show up under 'accounts'. I would like to remove this user so the email can be used to subsequently add the user using the 'Invite user' button. How can I remove a user that I can't see under accounts?

peter_teunissen · ‎04-19-2017

It turned out that during moving the resources to another subscription, the storageaccount was inadvertently moved to another resource group. Moving it back solved the issue.

peter_teunissen · ‎04-19-2017

Immediately after starting the creation of my cluster the infrastructure creation fails due to a vhd file not found error: 4/19/2017 11:33:58 AM spark-dev - update in progress: Infrastructure creation failed. Reason: Image creation failed because https://sequenceiqwesteurope2.blob.core.windows.net/images/hdc-hdp--1703101455.vhddoes not exist or Cloudbreak could not reach. However, I created a similar cluster just weeks ago with the same setup If I go into the Cloudbreak VM and try to get the vhd URI with wget, I can simply download the vhd file. When I look in the Cloudbreak log, I see an additional error, just before the above: "The Resource 'Microsoft.Storage/storageAccounts/cbstorewe5db978ee37d347a' under resource group 'cbstore' was not found." When I look in Azure, I don't see this resource and I don't remember having seen it before. I'm running Cloudbreak version 1.14.1-6ff7af8 What could cause this problem? Could it be the missing resource? If so, how could I recreate it?

peter_teunissen · ‎04-12-2017

That'll be the problem. My VM is in West-Europe.

peter_teunissen · ‎04-05-2017

I installed Cloudbreak 1.14.1 on Azure. I can't add users because emails don't get send. In earlier versions I could work around this by looking for the email in the cloudbreak log, now nothing shows up in the log. I openend all outgoing smtp ports, but that wasn't the issue. Where can I look to solve this issue? The log doesn't show anything.

peter_teunissen · ‎03-29-2017

I had a working Cloudbreak 1.6.3 setup using Azure. After upgrading to 1.14.0, the credentials no longer work. Both an existing credential and newly created ones give the following error when creating a new cluster: Failed to create cluster: Unrecognized fiels 'tenantid' (class com.sequenceid.cloudbreak.api.model.wasbFileSystemConfigu[not visible in popup] not marked as ignorable (2 known properties: "accountname", "accountKey"]) as [Source: {"tenantid":"<removed>","clientid":"<removed>","accountname":"someaccount","accountKey":"<removed>" etc etc. The GUI provides an alternative way now to create an Azure credential (interactive) but that requires one to add subscriptionId and tenantid to 'profile', but there's no option in the GUI to update a 'profile'. I seems something is changed in the Azure credential setup, but only halfway released. What can I do to get a working credential and create a cluster?

peter_teunissen · ‎03-28-2017

I could get a step further by manually updating the cluster status in the status table to 'STOPPED' manually starting all node vm's, logging in and halting them restarting cloudbreak Then after some time cloudbreak syncs with the cluster and can startup the cluster. However it says that the infrastructure is started and that a cluster startup is ongoing. In Azure however the VM's still have a 'stopped' status. When I look in the Cloudbreak startup log, I see an error: Failed to convert from type [java.util.LinkedHashSet<?>] to type [com.sequenceiq.cloudbreak.api.model.AutoscaleStackResponse] for value 'com.sequenceiq.cloudbreak.domain.Stack@25194c0b' Even after restarting Cloudbreak, these errors reoccur and the GUI still hangs in the 'update in progress: Starting Ambari cluster' fase...

peter_teunissen · ‎03-28-2017

I installed a HDP 2.5 cluster on Azure using Cloudbreak 1.6.3. Everything was running fine, until Microsoft stopped both the cluster and the cloudbreak VM because of a supposed 'service violation'. After that issue was resolved I restarted the cloudbreak vm and was told to upgrade to version 1.14.0 and regenerate the docker-compose.yml by the cdb doctor command. So I did. After starting cloudbreak and logging in, all seemed fine, only the reference to my cluster was missing. I also noticed that the GUI takes a long time loading (the page is greyed out and a 'Loading...' sign is displayed. It might be timing out on something... Starting the nodes manually resulted in Cloudbreak showing the cluster again. But subsequently syncing it from within cloudbreak results in an error 'Cluster can't be synchronized. [ stack status: STOPPED, cluster status: AVAILABLE ]'. Refreshing the Cloudbreak GUI makes the stop button appear, but clicking it results in 'cluster not available' error. Stopping all the nodes manually and syncing results in an error 'Cluster and it's stack sync failed please try again: Stack 11 has flows under operation, request not allowed'. The error stays the same, even after retry after some time. How can I get the link to my (currently stopped) cluster back in the cloudbreak GUI and sync it?

peter_teunissen · ‎03-27-2017

I can stop & start just fine (apart from a small Zeppelin issue, but that's beside the point). ... and after some time and a logout/login, the node counts were updated correctly... all's good now.

peter_teunissen · ‎03-27-2017

@khorvath Oops, I was a bit to enthusiastic... now Cloudbreak syncs without any errors, but it shows a count of 0 for each of the node types. In the header the total node count is still correct (5) but on the node type tabs it says 0 Under the Nodes sub page all nodes are shown as healthy. I checked, all the nodes are active in Ambari. It might be just cosmetic... but it's strange.

peter_teunissen · ‎03-27-2017

Thanks @khorvath, that worked flawlessly!

peter_teunissen · ‎03-27-2017

I have created a cluster on Azure using Cloudbreak. Due to access right issues in the Azure tenant, the cluster was moved to another Azure subscription. All is running just fine and shows up in the Azure portal under the new subscription. However, Cloudbreak has lost it's connection to the cluster due to the changed subscription ID. Syncing Cloudbreak to the cluster obviously fails currently. The GUI doesn't allow me to update an existing subscription ID within the credential. Is there another way for me to update the existing credential and sync Cloudbreak to the moved cluster?

peter_teunissen · ‎03-23-2017

Thanks, that did the trick. I guess this is a bug. Where should I report it? A quick google search didn't give me anything useful on 'hortonworks bug report'

peter_teunissen · ‎03-23-2017

I changed the directory to one based on the wasb defaultFS. But the spark throws a class not find error: java.lang.ClassNotFoundException: com.microsoft.azure.storage.blob.BlobListingDetails You'd expect this class to be available on a system supporting WASB... Could I add some java options somewhere so it can find this class? Also strange is that when I look at the setup of a HDInsight cluster, it's setup just like the default setup by Cloudbreak and there it simply works, the spark history server doesn't complain about the default hdfs:///spark-history uri

peter_teunissen · ‎03-21-2017

Ah, silly me. I made a security group and forgot to add port 9443. <facepalm>

peter_teunissen · ‎03-21-2017

in the log I see a time out: cloudbreak_1 | 2017-03-21 21:28:13,027 [reactorDispatcher-4] isBootstrapApiAvailable:262 INFO c.s.c.o.s.SaltOrchestrator - [owner:spring] [type:springLog] [id:] [name:] Failed to connect to bootstrap app org.apache.http.conn.HttpHostConnectException: Connect to 52.232.xxx.xxx:9443 [/52.232.xxx.xxx] failed: Connection timed out (Connection timed out seems the bootstrap app failed to start...

peter_teunissen · ‎03-21-2017

I've been able to do one test install with Cloudbreak this morning. The second install failed and had to be terminated. After that, every install hangs at the 'update in progress: Bootstrapping infrastructure cluster' fase. I can't discover the cause. Where could I look to find the reason for the hanged cluster rollout?

peter_teunissen · ‎03-21-2017

I setup a small hdp 2.4 cluster with cloudbreak. After startup the spark history server fails. In the log I find: Caused by: java.io.IOException: Incomplete HDFS URI, no host: hdfs:///spark-history I found these entries in the spark-defaults.conf file: spark.history.fs.logDirectory hdfs:///spark-history spark.eventLog.dir hdfs:///spark-history. I'm using WASB storage for the cluster. I've no idea what host to set these URI's to.

peter_teunissen · ‎03-17-2017

Thanks @pdarvasi, that solved the issue. It was indeed the fact that my user has multiple subscriptions and it switched to the wrong one. It would be a good thing if the tool is able to handle that correctly. Thanks for filing the issue. I also noted that the current script greps for 'data: Application Id:' but at least in the latest version of the Azure CLI it actually reads 'data: AppId:' in the output. This might require a change to the tool also. Thanks for the help!

peter_teunissen · ‎03-17-2017

I've been trying to create an Azure ARM application with the cbd azure configure-arm command as needed for the Cloudbreak Azure credential. I keeps failing with an insufficient privileges error. Currently the my user has the 'owner' role on the subscriptions and is admin on de Azure AD so that shouldn't be the issue. The only thing that could be a problem is the fact that my user has several Azure subscriptions and in the cbd configure-arm output I see it switching to the default subscription, which is not the one I gave as a parameter. Could this be the culprit? How can I force the command to use the proper subscription or does this command only work with a user with a single subscription? Thanks

Online	Offline
Last Visited	‎05-19-2017 01:37 PM

Date Registered	‎03-17-2017 04:05 PM
Last Visited	‎05-19-2017 01:37 PM
Total Messages Posted	23
Total Kudos Received	5

Re: Infrastructure creation failed. Reason: Image ...

Re: How can I disable SSL peer verification for SM...

How can I disable SSL peer verification for SMTP n...

Re: Remove user created with 'Sign up' link on log...

Remove user created with 'Sign up' link on login p...

Re: Infrastructure creation failed. Reason: Image ...

Infrastructure creation failed. Reason: Image crea...

Re: Cloudbreak on Azure can't send email

Cloudbreak on Azure can't send email

After upgrade from cloudbreak 1.6.3 to 1.14.0 Azur...

Re: Azure HDP cluster disappeared from Cloudbreak ...

Azure HDP cluster disappeared from Cloudbreak GUI ...

Re: Update existing Azure credential with new subs...

Re: Update existing Azure credential with new subs...

Re: Update existing Azure credential with new subs...

Update existing Azure credential with new subscrip...

Re: spark hdfs uri missing host on hdp 2.4

Re: spark hdfs uri missing host on hdp 2.4

Re: Every cluster creation hangs at update in prog...

Re: Every cluster creation hangs at update in prog...

Every cluster creation hangs at update in progress...

spark hdfs uri missing host on hdp 2.4

Re: cdb azure configure-arm with multiple subscrip...

cdb azure configure-arm with multiple subscription...