‘buildNumber: unbound variable’ in Ambari Setup

I’m currently experimenting with Apache Ambari, because setting up a Hadoop cluster manually looked like no fun whatsoever. However, the Ambari project does not distribute binaries, and the freely available Hortonworks binaries required a support identifier in order to deploy a cluster. That’s a hard no on that one there super chief.

So, I built Ambari from source. That was a trial that probably deserves a blog post in its own right.

But, I got my RPMs,  installed them on my target server and tried to run the setup process;

Well, fuck.

A first look, the internet proved little help – I found a couple of people with the issue, but no helpful information. So, in my desperation, I went to the third page of a google search. I know, shocking.

And what I found was a chinese blog post. I don’t read a work of any asian languages, but a quick text search of the post led me to this;

Aha! So, I tried it (replacing the value of the variable with the correct version number, in my case), and lo;

And we are in business. So, it seems that if you build ambari-server yourself, it is reliant on a buildNumber enviroment variable. (I don not recall having this issue with the Hortonworks binaries).

Would have been nice to have that in documentation huh?

3 thoughts on “‘buildNumber: unbound variable’ in Ambari Setup

  1. Thanks man, i have the same problem and in first time of my life the internet on a easy way help-me fix some problem.

    really thanks.

    • Looking this fix method i guess that maybe Ambari can have a file for environments configuration (like apache spark has) some Ambari-env.conf or like that.

      i will try find one end reply here if i found.

      • When I put Ambari into production, I intend to make sure that this environment variable is a part of the startup script for the service. I’m still in testing stages though so I haven’t bothered to do this yet!

Leave a Reply

Your email address will not be published. Required fields are marked *