You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Brenden Cobb <bc...@blackduck.com.INVALID> on 2025/11/18 19:04:38 UTC
Re: Help needed
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org <us...@ambari.apache.org>, dev@ambari.apache.org <de...@ambari.apache.org>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com>.
Hi all,
Also, with the source of (I assume) 3.0.0 and again with 3.1.0, I see that the ambari-server src stack info still has the base of bigtop 3.2.0 with 3.3.0 and 3.4.0 as ‘extras’. What also confuses and concerns is that the repoinfo for all these maintains that centos-9 is available for redhat 9 family. Why not rocky-linux 9 if that is the only real choice?
I still have no effective answer for why the references to 3.2.0 I mentioned are preventing any useful install of ambari.
What I did notice is that, despite the ranger typo in the documented release binary download, the suite worked far better and made no references to 3.2.0 when I installed it. But every other instance I have tried does (built from source).
I ask, how an any practical upgrade be performed if the software is always after 3.2.0 somewhere?
Marc
From: Marc Hoppins <ma...@eset.com>
Sent: Thursday, November 27, 2025 11:56 AM
To: user@ambari.apache.org
Subject: RE: [EXT]Re: Help needed
[External Sender]
Hi, Brendan,
Sorry for the delay. I decided to wipe the slate clean and begin from the start.
So, now I am thinking the important part is the actual source.
I followed your link and downloaded the ZIP. I corrected the tagsync typo and rebuilt. No problems. I installed, created a test cluster and re-installed to targets.
[cid:image003.png@01DC62A8.5D9F6FF0]
So I tried installing on one target via commandline: yum install -y Hadoop_3_0_0
Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded into the source somewhere. Surely this would make any attempt to upgrade a complete failure?
Where am I looking to fix in the source?
Marc
From: Brenden Cobb <bc...@blackduck.com>>
Sent: Thursday, November 20, 2025 10:25 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image004.png@01DC62A8.5D9F6FF0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image005.png@01DC62A8.5D9F6FF0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com>.
Jefferson,
Thank you for your reply. To respond to your concerns. I do acknowledge the sites and discourses you mentioned. However these, as you indicted, speak more to those engaged in the improvement and furtherance of the project more with regard to the coding than use. I, on the other hand, like many others who would make use of this suite of software, am in the camp of end-user and administration than fixing code or troubleshooting 3rd-party software.
To emphasise this: we were using cloudera but the costs of using that have indicated that we will no longer be using it. I have been keeping an eye on this project since cloudera’s paywall went up and while it promised to be very useful, building it created far too many problems with artifacts missing, versions being incorrect, and so on. The project was shelved and it seemed to be an opportunity lost. Then it gained a new lease of life and development continued. I saw a pre-built solution was provided with updated documentation. I tested it and was extremely hopeful but alas, the ranger module failed all because of a simple thing like one missing character from a declaration. However, rather than simply fixing the problem and allowing the public to try the suite for themselves, development continues but now throws up far more issues than one omitted character.
Again, I am not a coder/programmer, merely one hoping to encourage its use to the data folks here rather than, as they are trying, cobbling together a half-baked (but workable) solution using ansible and a monitoring package.
Marc
From: Jefferson Almeida <jr...@gmail.com>
Sent: Tuesday, January 13, 2026 2:09 PM
To: user@ambari.apache.org
Cc: dev@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
Hi Marc,
I understand your frustration with the project, but I think a few points need to be clarified, and some expectations need to be realigned.
First, the BIGTOP stack in Ambari follows a stack inheritance model, as described here:
https://ambari.apache.org/docs/2.7.8/ambari-design/stack-and-services/stack-inheritance
Because of this, not every service or file must be redefined or duplicated in each stack version. A stack such as 3.3.0 can legitimately reference artifacts inherited from 3.2.0 or earlier, even if a service was introduced or fully enabled later. This is expected behavior and not, by itself, an error or ambiguity.
Second, Ambari is a mature and stable project, but like any complex open-source software, it still has areas that can and should be improved. Those improvements, however, happen through constructive collaboration. Raising concerns is welcome, but doing so without proposing solutions, patches, or even concrete suggestions does not move the project forward.
Statements questioning the credibility of the software or the community, without engaging in the contribution process (JIRAs, patches, reviews, or design discussions), do not help resolve the issues you are experiencing.
If you believe there is a real inconsistency or bug, the best path forward is to:
* Open a JIRA with a clear technical description
* Propose a fix or at least a concrete improvement
* Engage with the community to validate the approach
The community only benefits when its members are willing to collaborate, share knowledge, and contribute — not just point out problems.
Best regards,
Jefferson Almeida
Em ter., 13 de jan. de 2026 às 05:09, Marc Hoppins <ma...@eset.com>> escreveu:
Hi, Brendan/All,
ambari-server/src/main/resources/stacks/3.3.0/RANGER/alerts.json references BIGTOP/3.2.0/services/RANGER/package/alerts/alert_ranger_admin_passwd_check.py
How is this ever going to work if 3.2.0 does not even have ranger ?
3.2.0/properties/stack_packages.json makes declarations for ranger-admin, ranger-tagsync and ranger-usersync but, again, RANGER does not appear to be a part of 3.2.0
Is this why I still see errors regarding 3.2.0 when I suggest I want 3.3.0?
I am still mystified by this software which has such useful potential but so much incredible ambiguity.
For the developers: WHY was a simple correction and rebuilt collection made available as soon as the typo was discovered? No mention in the official pages ANYWHERE that this problem exists, and that the prebuilt (downloadable) binaries will not operate as required.
Marc
From: Brenden Cobb <bc...@blackduck.com>>
Sent: Friday, December 5, 2025 11:00 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Hi Marc - Sorry for the delay… What happens when you run yum install hadoop_3_3_0 via CLI?
Your response suggests you were trying to install “Hadoop_3_0_0”
I would suggest double-checking building Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/building-from-source
And building Bigtop for Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/bigtop-guide
I also found the info here useful for building:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0
The “component did not advertise a version” message suggests something amiss on of the builds.
The stacks are specified here: https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/BIGTOP
I’m not a Ambari contributor, so I can only help so much based on my personal experience building ambari/bigtop and running on Rocky 8.
Cheers
From: Marc Hoppins <ma...@eset.com>>
Date: Thursday, November 27, 2025 at 5:57 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
Sorry for the delay. I decided to wipe the slate clean and begin from the start.
So, now I am thinking the important part is the actual source.
I followed your link and downloaded the ZIP. I corrected the tagsync typo and rebuilt. No problems. I installed, created a test cluster and re-installed to targets.
[cid:image001.png@01DC84A3.64D468D0]
So I tried installing on one target via commandline: yum install -y Hadoop_3_0_0
Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded into the source somewhere. Surely this would make any attempt to upgrade a complete failure?
Where am I looking to fix in the source?
Marc
From: Brenden Cobb <bc...@blackduck.com>>
Sent: Thursday, November 20, 2025 10:25 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image002.png@01DC84A3.64D468D0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image003.png@01DC84A3.64D468D0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com>.
Hi all (again),
I am sorry but I still don’t get it. From Apache BIGTOP site:
For Apache BIGTOP 3.2.0
bigtop 3.2.0 stack includes the following components
alluxio 2.8.0
bigtop-ambari-mpack 2.7.5
bigtop-groovy 2.5.4
bigtop-jsvc 1.2.4
bigtop-utils 3.1.0
flink 1.15.3
gpdb 5.28.5
hadoop 3.3.4
hbase 2.4.13
hive 3.1.3
kafka 2.8.1
livy 0.7.1
oozie 5.2.1
phoenix 5.1.2
solr 8.11.2
spark 3.2.1
tez 0.10.1
ycsb 0.17.0
zeppelin 0.10.1
zookeeper 3.5.9
and
bigtop 3.3.0 stack includes the following components
alluxio 2.9.3
bigtop-groovy 2.5.4
bigtop-jsvc 1.2.4
bigtop-select 3.3.0
bigtop-utils 3.3.0
flink 1.16.2
hadoop 3.3.6
hbase 2.4.17
hive 3.1.3
kafka 2.8.2
livy 0.8.0
phoenix 5.1.3
ranger 2.4.0
solr 8.11.2
spark 3.3.4
tez 0.10.2
zeppelin 0.11.0
zookeeper 3.7.2
According to the stack definition for Ambari 3.0.0 using BIGTOP 3.3.0, it EXTENDS BIGTOP 3.2.0. But all it seems to be doing is including Ranger for BIGTOP 3.2.0 as all the service versions are those defined for 3.2.0. Here is the AMBARI documentation information for BIGTOP 3.3.0 https://ambari.apache.org/docs/3.0.0/introduction#bigtop-stack-330 which implies that Ambari 3.0.0+ will be using 3.3.0 and this is clearly not the case.
I don’t mean to harp on about it but when getting errors regarding 3.2.0 when I select 3.3.0 (or even 3.4.0 in Ambari build 3.1.0 when I tried that), it seems that merely BUILDING the software with maven does not address actual configuration issues. If I end up writing reams of information on git with the hope of getting some pointers for a solution, does not address the issue that these problems with installing/using 3.0.0 (the download link to the binaries) or BUILDING and then installing/using any other version, seem to generate and the lack of any reference to possible problems within the published documentation.
Again, I am not a coder/builder and get mystified by things until some blessed soul explains things in a different way which registers but, as far as I can tell, all the mavan/project (JUNIT) type tests seem to do is to test the build but not the actual install and attempts to use.
Marc
From: Jefferson Almeida <jr...@gmail.com>
Sent: Tuesday, January 13, 2026 2:09 PM
To: user@ambari.apache.org
Cc: dev@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
Hi Marc,
I understand your frustration with the project, but I think a few points need to be clarified, and some expectations need to be realigned.
First, the BIGTOP stack in Ambari follows a stack inheritance model, as described here:
https://ambari.apache.org/docs/2.7.8/ambari-design/stack-and-services/stack-inheritance
Because of this, not every service or file must be redefined or duplicated in each stack version. A stack such as 3.3.0 can legitimately reference artifacts inherited from 3.2.0 or earlier, even if a service was introduced or fully enabled later. This is expected behavior and not, by itself, an error or ambiguity.
Second, Ambari is a mature and stable project, but like any complex open-source software, it still has areas that can and should be improved. Those improvements, however, happen through constructive collaboration. Raising concerns is welcome, but doing so without proposing solutions, patches, or even concrete suggestions does not move the project forward.
Statements questioning the credibility of the software or the community, without engaging in the contribution process (JIRAs, patches, reviews, or design discussions), do not help resolve the issues you are experiencing.
If you believe there is a real inconsistency or bug, the best path forward is to:
* Open a JIRA with a clear technical description
* Propose a fix or at least a concrete improvement
* Engage with the community to validate the approach
The community only benefits when its members are willing to collaborate, share knowledge, and contribute — not just point out problems.
Best regards,
Jefferson Almeida
Em ter., 13 de jan. de 2026 às 05:09, Marc Hoppins <ma...@eset.com>> escreveu:
Hi, Brendan/All,
ambari-server/src/main/resources/stacks/3.3.0/RANGER/alerts.json references BIGTOP/3.2.0/services/RANGER/package/alerts/alert_ranger_admin_passwd_check.py
How is this ever going to work if 3.2.0 does not even have ranger ?
3.2.0/properties/stack_packages.json makes declarations for ranger-admin, ranger-tagsync and ranger-usersync but, again, RANGER does not appear to be a part of 3.2.0
Is this why I still see errors regarding 3.2.0 when I suggest I want 3.3.0?
I am still mystified by this software which has such useful potential but so much incredible ambiguity.
For the developers: WHY was a simple correction and rebuilt collection made available as soon as the typo was discovered? No mention in the official pages ANYWHERE that this problem exists, and that the prebuilt (downloadable) binaries will not operate as required.
Marc
From: Brenden Cobb <bc...@blackduck.com>>
Sent: Friday, December 5, 2025 11:00 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Hi Marc - Sorry for the delay… What happens when you run yum install hadoop_3_3_0 via CLI?
Your response suggests you were trying to install “Hadoop_3_0_0”
I would suggest double-checking building Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/building-from-source
And building Bigtop for Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/bigtop-guide
I also found the info here useful for building:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0
The “component did not advertise a version” message suggests something amiss on of the builds.
The stacks are specified here: https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/BIGTOP
I’m not a Ambari contributor, so I can only help so much based on my personal experience building ambari/bigtop and running on Rocky 8.
Cheers
From: Marc Hoppins <ma...@eset.com>>
Date: Thursday, November 27, 2025 at 5:57 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
Sorry for the delay. I decided to wipe the slate clean and begin from the start.
So, now I am thinking the important part is the actual source.
I followed your link and downloaded the ZIP. I corrected the tagsync typo and rebuilt. No problems. I installed, created a test cluster and re-installed to targets.
[cid:image001.png@01DC8607.3A45D3A0]
So I tried installing on one target via commandline: yum install -y Hadoop_3_0_0
Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded into the source somewhere. Surely this would make any attempt to upgrade a complete failure?
Where am I looking to fix in the source?
Marc
From: Brenden Cobb <bc...@blackduck.com>>
Sent: Thursday, November 20, 2025 10:25 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image002.png@01DC8607.3A45D3A0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image003.png@01DC8607.3A45D3A0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
Re: [EXT]Re: Help needed
Posted by Jefferson Almeida <jr...@gmail.com>.
Hi Marc,
I understand your frustration with the project, but I think a few points
need to be clarified, and some expectations need to be realigned.
First, the BIGTOP stack in Ambari follows a *stack inheritance model*, as
described here:
https://ambari.apache.org/docs/2.7.8/ambari-design/stack-and-services/stack-inheritance
Because of this, *not every service or file must be redefined or duplicated
in each stack version*. A stack such as 3.3.0 can legitimately reference
artifacts inherited from 3.2.0 or earlier, even if a service was introduced
or fully enabled later. This is expected behavior and not, by itself, an
error or ambiguity.
Second, Ambari is a mature and stable project, but like any complex
open-source software, it still has areas that can and should be improved.
Those improvements, however, happen through *constructive collaboration*.
Raising concerns is welcome, but doing so without proposing solutions,
patches, or even concrete suggestions does not move the project forward.
Statements questioning the credibility of the software or the community,
without engaging in the contribution process (JIRAs, patches, reviews, or
design discussions), do not help resolve the issues you are experiencing.
If you believe there is a real inconsistency or bug, the best path forward
is to:
-
Open a JIRA with a clear technical description
-
Propose a fix or at least a concrete improvement
-
Engage with the community to validate the approach
The community only benefits when its members are willing to collaborate,
share knowledge, and contribute — not just point out problems.
Best regards,
Jefferson Almeida
Em ter., 13 de jan. de 2026 às 05:09, Marc Hoppins <ma...@eset.com>
escreveu:
> Hi, Brendan/All,
>
>
>
> *ambari-server/src/main/resources/stacks/3.3.0/RANGER/alerts.json*
> references
> *BIGTOP/3.2.0/services/RANGER/package/alerts/alert_ranger_admin_passwd_check.py*
>
>
>
> How is this ever going to work if 3.2.0 does not even have ranger ?
>
>
>
> 3.2.0/properties/stack_packages.json makes declarations for ranger-admin,
> ranger-tagsync and ranger-usersync but, again, RANGER does not appear to be
> a part of 3.2.0
>
>
>
> Is this why I still see errors regarding 3.2.0 when I suggest I want 3.3.0?
>
>
>
> I am still mystified by this software which has such useful potential but
> so much incredible ambiguity.
>
>
>
> For the developers: WHY was a simple correction and rebuilt collection
> made available as soon as the typo was discovered? No mention in the
> official pages ANYWHERE that this problem exists, and that the prebuilt
> (downloadable) binaries will not operate as required.
>
>
>
> Marc
>
>
>
> *From:* Brenden Cobb <bc...@blackduck.com>
> *Sent:* Friday, December 5, 2025 11:00 PM
> *To:* user@ambari.apache.org
> *Subject:* Re: [EXT]Re: Help needed
>
>
>
> [External Sender]
>
> Hi Marc - Sorry for the delay… What happens when you run yum install
> hadoop_3_3_0 via CLI?
>
> Your response suggests you were trying to install “Hadoop_3_0_0”
>
>
>
>
>
> I would suggest double-checking building Ambari:
>
> https://ambari.apache.org/docs/3.0.0/ambari-dev/building-from-source
>
>
>
> And building Bigtop for Ambari:
>
> https://ambari.apache.org/docs/3.0.0/ambari-dev/bigtop-guide
>
>
>
> I also found the info here useful for building:
>
>
> https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0
>
>
>
>
>
> The “component did not advertise a version” message suggests something
> amiss on of the builds.
>
>
>
>
>
> The stacks are specified here:
> https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/BIGTOP
>
>
>
>
>
> I’m not a Ambari contributor, so I can only help so much based on my
> personal experience building ambari/bigtop and running on Rocky 8.
>
>
>
>
>
> Cheers
>
>
>
>
>
>
>
>
>
>
>
> *From: *Marc Hoppins <ma...@eset.com>
> *Date: *Thursday, November 27, 2025 at 5:57 AM
> *To: *user@ambari.apache.org <us...@ambari.apache.org>
> *Subject: *RE: [EXT]Re: Help needed
>
> Hi, Brendan,
>
> Sorry for the delay. I decided to wipe the slate clean and begin from the
> start.
>
>
>
> So, now I am thinking the important part is the actual source.
>
>
>
> I followed your link and downloaded the ZIP. I corrected the tagsync typo
> and rebuilt. No problems. I installed, created a test cluster and
> re-installed to targets.
>
>
>
>
>
> So I tried installing on one target via commandline: yum install -y
> Hadoop_3_0_0
>
>
>
> Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded
> into the source somewhere. Surely this would make any attempt to upgrade a
> complete failure?
>
>
>
> Where am I looking to fix in the source?
>
>
>
> Marc
>
>
>
> *From:* Brenden Cobb <bc...@blackduck.com>
> *Sent:* Thursday, November 20, 2025 10:25 PM
> *To:* user@ambari.apache.org
> *Subject:* Re: [EXT]Re: Help needed
>
>
>
> [External Sender]
>
> I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is
> trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo
> available? What happens when you try to execute the yum install command
> that is producing the error?
>
>
>
> *From: *Marc Hoppins <*marc.hoppins@eset.com.INVALID
> <ma...@eset.com.INVALID>*>
> *Date: *Thursday, November 20, 2025 at 3:49 AM
> *To: **user@ambari.apache.org <us...@ambari.apache.org>* <*user@ambari.apache.org
> <us...@ambari.apache.org>*>
> *Subject: *RE: [EXT]Re: Help needed
>
> Well, after doing all those steps…
>
>
>
>
>
> *From:* Brenden Cobb <*bcobb@blackduck.com.INVALID
> <bc...@blackduck.com.INVALID>*>
> *Sent:* Wednesday, November 19, 2025 9:03 PM
> *To:* *user@ambari.apache.org <us...@ambari.apache.org>*
> *Subject:* Re: [EXT]Re: Help needed
>
>
>
> [External Sender]
>
> Seems like there may be some artifacts from previous installation
>
>
>
> These are steps I have used before to clean up, prior to re-installing:
>
> *https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
> <https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114>*
>
>
>
>
>
>
>
> *From: *Marc Hoppins <*marc.hoppins@eset.com.INVALID
> <ma...@eset.com.INVALID>*>
> *Date: *Wednesday, November 19, 2025 at 9:15 AM
> *To: **user@ambari.apache.org <us...@ambari.apache.org>* <*user@ambari.apache.org
> <us...@ambari.apache.org>*>, *dev@ambari.apache.org
> <de...@ambari.apache.org>* <*dev@ambari.apache.org <de...@ambari.apache.org>*>
> *Subject: *RE: [EXT]Re: Help needed
>
> Hi, Brendan,
>
>
>
> I appreciate the information. I downloaded and rebuilt 3.0.0.
>
>
>
> First, ambari-server changed from a HASH=”hexnumber” to
> HASH=”${buildnumber}” which fails the server start.
>
>
>
> Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is
> failing host installs. Where am I likely to find this problem because
> selecting in the ambari UI is not making the right choice. I dumped the
> ambari database and started afresh but no joy.
>
>
>
>
>
> *From:* Brenden Cobb <*bcobb@blackduck.com.INVALID
> <bc...@blackduck.com.INVALID>*>
> *Sent:* Tuesday, November 18, 2025 8:05 PM
> *To:* *user@ambari.apache.org <us...@ambari.apache.org>*; *dev@ambari.apache.org
> <de...@ambari.apache.org>*
> *Subject:* [EXT]Re: Help needed
>
>
>
> [External Sender]
>
> Hi -
>
>
>
> The latest release of Ambari is version 3.0.0. Running a later build is
> likely to surface errors.
>
>
>
> To try and fix the Ranger issue from your previous email, I would suggest
> building Ambari version 3.0.0 *https://github.com/apache/ambari/tree/release-3.0.0
> <https://github.com/apache/ambari/tree/release-3.0.0>*, patched with the
> change in: *https://issues.apache.org/jira/browse/AMBARI-26427
> <https://issues.apache.org/jira/browse/AMBARI-26427>*
>
>
>
> *From: *Marc Hoppins <*marc.hoppins@eset.com.INVALID
> <ma...@eset.com.INVALID>*>
> *Date: *Tuesday, November 18, 2025 at 8:01 AM
> *To: **user@ambari.apache.org <us...@ambari.apache.org>* <*user@ambari.apache.org
> <us...@ambari.apache.org>*>, *dev@ambari.apache.org
> <de...@ambari.apache.org>* <*dev@ambari.apache.org <de...@ambari.apache.org>*>
> *Subject: *Help needed
>
> Hi, All…Anyone,
>
>
>
> I downloaded and tried 3.0.0 but got the ranger error regarding
> translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar
> with all of eclipse but assume I got things right as I saw no errors.
>
>
>
> I installed 3.1.0 and purged any packages on my target nodes. I then
> installed the ambari-agent on targets to 3.1.0.
>
>
>
> I started with a clean ambari database.
>
>
>
> I did not download and build either metrics or infra but stuck with the
> existing rpms from the 3.0.0 install.
>
>
>
> I was a bit concerned with the ‘build from source’ instructions as it is
> suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as
> 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
>
>
>
> Running the ambari server now, I see cluster install options for BIGTOP
> 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my
> repository setup with 3.3.0 and was expecting I could use that.
>
>
>
> Warnings and errors abound and when I checked the running process I saw a
> running agent process
>
>
>
> /usr/bin/python3
> /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
>
>
>
> If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to
> use 3.3.0 or 3.4.0 why are they included?
>
>
>
> Any information would be appreciated.
>
>
>
> Marc
>
Re: [EXT]Re: Help needed
Posted by Jefferson Almeida <jr...@gmail.com>.
Hi Marc,
I understand your frustration with the project, but I think a few points
need to be clarified, and some expectations need to be realigned.
First, the BIGTOP stack in Ambari follows a *stack inheritance model*, as
described here:
https://ambari.apache.org/docs/2.7.8/ambari-design/stack-and-services/stack-inheritance
Because of this, *not every service or file must be redefined or duplicated
in each stack version*. A stack such as 3.3.0 can legitimately reference
artifacts inherited from 3.2.0 or earlier, even if a service was introduced
or fully enabled later. This is expected behavior and not, by itself, an
error or ambiguity.
Second, Ambari is a mature and stable project, but like any complex
open-source software, it still has areas that can and should be improved.
Those improvements, however, happen through *constructive collaboration*.
Raising concerns is welcome, but doing so without proposing solutions,
patches, or even concrete suggestions does not move the project forward.
Statements questioning the credibility of the software or the community,
without engaging in the contribution process (JIRAs, patches, reviews, or
design discussions), do not help resolve the issues you are experiencing.
If you believe there is a real inconsistency or bug, the best path forward
is to:
-
Open a JIRA with a clear technical description
-
Propose a fix or at least a concrete improvement
-
Engage with the community to validate the approach
The community only benefits when its members are willing to collaborate,
share knowledge, and contribute — not just point out problems.
Best regards,
Jefferson Almeida
Em ter., 13 de jan. de 2026 às 05:09, Marc Hoppins <ma...@eset.com>
escreveu:
> Hi, Brendan/All,
>
>
>
> *ambari-server/src/main/resources/stacks/3.3.0/RANGER/alerts.json*
> references
> *BIGTOP/3.2.0/services/RANGER/package/alerts/alert_ranger_admin_passwd_check.py*
>
>
>
> How is this ever going to work if 3.2.0 does not even have ranger ?
>
>
>
> 3.2.0/properties/stack_packages.json makes declarations for ranger-admin,
> ranger-tagsync and ranger-usersync but, again, RANGER does not appear to be
> a part of 3.2.0
>
>
>
> Is this why I still see errors regarding 3.2.0 when I suggest I want 3.3.0?
>
>
>
> I am still mystified by this software which has such useful potential but
> so much incredible ambiguity.
>
>
>
> For the developers: WHY was a simple correction and rebuilt collection
> made available as soon as the typo was discovered? No mention in the
> official pages ANYWHERE that this problem exists, and that the prebuilt
> (downloadable) binaries will not operate as required.
>
>
>
> Marc
>
>
>
> *From:* Brenden Cobb <bc...@blackduck.com>
> *Sent:* Friday, December 5, 2025 11:00 PM
> *To:* user@ambari.apache.org
> *Subject:* Re: [EXT]Re: Help needed
>
>
>
> [External Sender]
>
> Hi Marc - Sorry for the delay… What happens when you run yum install
> hadoop_3_3_0 via CLI?
>
> Your response suggests you were trying to install “Hadoop_3_0_0”
>
>
>
>
>
> I would suggest double-checking building Ambari:
>
> https://ambari.apache.org/docs/3.0.0/ambari-dev/building-from-source
>
>
>
> And building Bigtop for Ambari:
>
> https://ambari.apache.org/docs/3.0.0/ambari-dev/bigtop-guide
>
>
>
> I also found the info here useful for building:
>
>
> https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0
>
>
>
>
>
> The “component did not advertise a version” message suggests something
> amiss on of the builds.
>
>
>
>
>
> The stacks are specified here:
> https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/BIGTOP
>
>
>
>
>
> I’m not a Ambari contributor, so I can only help so much based on my
> personal experience building ambari/bigtop and running on Rocky 8.
>
>
>
>
>
> Cheers
>
>
>
>
>
>
>
>
>
>
>
> *From: *Marc Hoppins <ma...@eset.com>
> *Date: *Thursday, November 27, 2025 at 5:57 AM
> *To: *user@ambari.apache.org <us...@ambari.apache.org>
> *Subject: *RE: [EXT]Re: Help needed
>
> Hi, Brendan,
>
> Sorry for the delay. I decided to wipe the slate clean and begin from the
> start.
>
>
>
> So, now I am thinking the important part is the actual source.
>
>
>
> I followed your link and downloaded the ZIP. I corrected the tagsync typo
> and rebuilt. No problems. I installed, created a test cluster and
> re-installed to targets.
>
>
>
>
>
> So I tried installing on one target via commandline: yum install -y
> Hadoop_3_0_0
>
>
>
> Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded
> into the source somewhere. Surely this would make any attempt to upgrade a
> complete failure?
>
>
>
> Where am I looking to fix in the source?
>
>
>
> Marc
>
>
>
> *From:* Brenden Cobb <bc...@blackduck.com>
> *Sent:* Thursday, November 20, 2025 10:25 PM
> *To:* user@ambari.apache.org
> *Subject:* Re: [EXT]Re: Help needed
>
>
>
> [External Sender]
>
> I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is
> trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo
> available? What happens when you try to execute the yum install command
> that is producing the error?
>
>
>
> *From: *Marc Hoppins <*marc.hoppins@eset.com.INVALID
> <ma...@eset.com.INVALID>*>
> *Date: *Thursday, November 20, 2025 at 3:49 AM
> *To: **user@ambari.apache.org <us...@ambari.apache.org>* <*user@ambari.apache.org
> <us...@ambari.apache.org>*>
> *Subject: *RE: [EXT]Re: Help needed
>
> Well, after doing all those steps…
>
>
>
>
>
> *From:* Brenden Cobb <*bcobb@blackduck.com.INVALID
> <bc...@blackduck.com.INVALID>*>
> *Sent:* Wednesday, November 19, 2025 9:03 PM
> *To:* *user@ambari.apache.org <us...@ambari.apache.org>*
> *Subject:* Re: [EXT]Re: Help needed
>
>
>
> [External Sender]
>
> Seems like there may be some artifacts from previous installation
>
>
>
> These are steps I have used before to clean up, prior to re-installing:
>
> *https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
> <https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114>*
>
>
>
>
>
>
>
> *From: *Marc Hoppins <*marc.hoppins@eset.com.INVALID
> <ma...@eset.com.INVALID>*>
> *Date: *Wednesday, November 19, 2025 at 9:15 AM
> *To: **user@ambari.apache.org <us...@ambari.apache.org>* <*user@ambari.apache.org
> <us...@ambari.apache.org>*>, *dev@ambari.apache.org
> <de...@ambari.apache.org>* <*dev@ambari.apache.org <de...@ambari.apache.org>*>
> *Subject: *RE: [EXT]Re: Help needed
>
> Hi, Brendan,
>
>
>
> I appreciate the information. I downloaded and rebuilt 3.0.0.
>
>
>
> First, ambari-server changed from a HASH=”hexnumber” to
> HASH=”${buildnumber}” which fails the server start.
>
>
>
> Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is
> failing host installs. Where am I likely to find this problem because
> selecting in the ambari UI is not making the right choice. I dumped the
> ambari database and started afresh but no joy.
>
>
>
>
>
> *From:* Brenden Cobb <*bcobb@blackduck.com.INVALID
> <bc...@blackduck.com.INVALID>*>
> *Sent:* Tuesday, November 18, 2025 8:05 PM
> *To:* *user@ambari.apache.org <us...@ambari.apache.org>*; *dev@ambari.apache.org
> <de...@ambari.apache.org>*
> *Subject:* [EXT]Re: Help needed
>
>
>
> [External Sender]
>
> Hi -
>
>
>
> The latest release of Ambari is version 3.0.0. Running a later build is
> likely to surface errors.
>
>
>
> To try and fix the Ranger issue from your previous email, I would suggest
> building Ambari version 3.0.0 *https://github.com/apache/ambari/tree/release-3.0.0
> <https://github.com/apache/ambari/tree/release-3.0.0>*, patched with the
> change in: *https://issues.apache.org/jira/browse/AMBARI-26427
> <https://issues.apache.org/jira/browse/AMBARI-26427>*
>
>
>
> *From: *Marc Hoppins <*marc.hoppins@eset.com.INVALID
> <ma...@eset.com.INVALID>*>
> *Date: *Tuesday, November 18, 2025 at 8:01 AM
> *To: **user@ambari.apache.org <us...@ambari.apache.org>* <*user@ambari.apache.org
> <us...@ambari.apache.org>*>, *dev@ambari.apache.org
> <de...@ambari.apache.org>* <*dev@ambari.apache.org <de...@ambari.apache.org>*>
> *Subject: *Help needed
>
> Hi, All…Anyone,
>
>
>
> I downloaded and tried 3.0.0 but got the ranger error regarding
> translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar
> with all of eclipse but assume I got things right as I saw no errors.
>
>
>
> I installed 3.1.0 and purged any packages on my target nodes. I then
> installed the ambari-agent on targets to 3.1.0.
>
>
>
> I started with a clean ambari database.
>
>
>
> I did not download and build either metrics or infra but stuck with the
> existing rpms from the 3.0.0 install.
>
>
>
> I was a bit concerned with the ‘build from source’ instructions as it is
> suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as
> 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
>
>
>
> Running the ambari server now, I see cluster install options for BIGTOP
> 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my
> repository setup with 3.3.0 and was expecting I could use that.
>
>
>
> Warnings and errors abound and when I checked the running process I saw a
> running agent process
>
>
>
> /usr/bin/python3
> /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
>
>
>
> If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to
> use 3.3.0 or 3.4.0 why are they included?
>
>
>
> Any information would be appreciated.
>
>
>
> Marc
>
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com>.
Hi, Brendan/All,
ambari-server/src/main/resources/stacks/3.3.0/RANGER/alerts.json references BIGTOP/3.2.0/services/RANGER/package/alerts/alert_ranger_admin_passwd_check.py
How is this ever going to work if 3.2.0 does not even have ranger ?
3.2.0/properties/stack_packages.json makes declarations for ranger-admin, ranger-tagsync and ranger-usersync but, again, RANGER does not appear to be a part of 3.2.0
Is this why I still see errors regarding 3.2.0 when I suggest I want 3.3.0?
I am still mystified by this software which has such useful potential but so much incredible ambiguity.
For the developers: WHY was a simple correction and rebuilt collection made available as soon as the typo was discovered? No mention in the official pages ANYWHERE that this problem exists, and that the prebuilt (downloadable) binaries will not operate as required.
Marc
From: Brenden Cobb <bc...@blackduck.com>
Sent: Friday, December 5, 2025 11:00 PM
To: user@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
Hi Marc - Sorry for the delay… What happens when you run yum install hadoop_3_3_0 via CLI?
Your response suggests you were trying to install “Hadoop_3_0_0”
I would suggest double-checking building Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/building-from-source
And building Bigtop for Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/bigtop-guide
I also found the info here useful for building:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0
The “component did not advertise a version” message suggests something amiss on of the builds.
The stacks are specified here: https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/BIGTOP
I’m not a Ambari contributor, so I can only help so much based on my personal experience building ambari/bigtop and running on Rocky 8.
Cheers
From: Marc Hoppins <ma...@eset.com>>
Date: Thursday, November 27, 2025 at 5:57 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
Sorry for the delay. I decided to wipe the slate clean and begin from the start.
So, now I am thinking the important part is the actual source.
I followed your link and downloaded the ZIP. I corrected the tagsync typo and rebuilt. No problems. I installed, created a test cluster and re-installed to targets.
[cid:image003.png@01DC846A.228B5A30]
So I tried installing on one target via commandline: yum install -y Hadoop_3_0_0
Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded into the source somewhere. Surely this would make any attempt to upgrade a complete failure?
Where am I looking to fix in the source?
Marc
From: Brenden Cobb <bc...@blackduck.com>>
Sent: Thursday, November 20, 2025 10:25 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image004.png@01DC846A.228B5A30]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image005.png@01DC846A.228B5A30]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com>.
I posted in there that the install worked for a package using CLI. That, I do not have to point out, completely misses the objective of having a tool to install, manage, monitor.
So, whether I build from 3.0.0 (your link) or download the latest trunk (3.1.0), the result is the same: an error looking for 3.2.0 somewhere. The linked release (from the documentation) did not have this problem but it does have the translations error.
If I look in the POM for the release 3.0 it seems as though 3.2 is the bulk of the install and 3.3 is just ranger. I am not au fait with these things so not completely sure what I am looking for.
From: Brenden Cobb <bc...@blackduck.com>
Sent: Friday, December 5, 2025 11:00 PM
To: user@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
Hi Marc - Sorry for the delay… What happens when you run yum install hadoop_3_3_0 via CLI?
Your response suggests you were trying to install “Hadoop_3_0_0”
I would suggest double-checking building Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/building-from-source
And building Bigtop for Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/bigtop-guide
I also found the info here useful for building:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0
The “component did not advertise a version” message suggests something amiss on of the builds.
The stacks are specified here: https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/BIGTOP
I’m not a Ambari contributor, so I can only help so much based on my personal experience building ambari/bigtop and running on Rocky 8.
Cheers
From: Marc Hoppins <ma...@eset.com>>
Date: Thursday, November 27, 2025 at 5:57 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
Sorry for the delay. I decided to wipe the slate clean and begin from the start.
So, now I am thinking the important part is the actual source.
I followed your link and downloaded the ZIP. I corrected the tagsync typo and rebuilt. No problems. I installed, created a test cluster and re-installed to targets.
[cid:image003.png@01DC681C.26B40FE0]
So I tried installing on one target via commandline: yum install -y Hadoop_3_0_0
Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded into the source somewhere. Surely this would make any attempt to upgrade a complete failure?
Where am I looking to fix in the source?
Marc
From: Brenden Cobb <bc...@blackduck.com>>
Sent: Thursday, November 20, 2025 10:25 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image004.png@01DC681C.26B40FE0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image005.png@01DC681C.26B40FE0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
Re: [EXT]Re: Help needed
Posted by Brenden Cobb <bc...@blackduck.com>.
Hi Marc - Sorry for the delay… What happens when you run yum install hadoop_3_3_0 via CLI?
Your response suggests you were trying to install “Hadoop_3_0_0”
I would suggest double-checking building Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/building-from-source
And building Bigtop for Ambari:
https://ambari.apache.org/docs/3.0.0/ambari-dev/bigtop-guide
I also found the info here useful for building:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0
The “component did not advertise a version” message suggests something amiss on of the builds.
The stacks are specified here: https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/BIGTOP
I’m not a Ambari contributor, so I can only help so much based on my personal experience building ambari/bigtop and running on Rocky 8.
Cheers
From: Marc Hoppins <ma...@eset.com>
Date: Thursday, November 27, 2025 at 5:57 AM
To: user@ambari.apache.org <us...@ambari.apache.org>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
Sorry for the delay. I decided to wipe the slate clean and begin from the start.
So, now I am thinking the important part is the actual source.
I followed your link and downloaded the ZIP. I corrected the tagsync typo and rebuilt. No problems. I installed, created a test cluster and re-installed to targets.
[cid:image003.png@01DC5F94.DBAF0070]
So I tried installing on one target via commandline: yum install -y Hadoop_3_0_0
Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded into the source somewhere. Surely this would make any attempt to upgrade a complete failure?
Where am I looking to fix in the source?
Marc
From: Brenden Cobb <bc...@blackduck.com>
Sent: Thursday, November 20, 2025 10:25 PM
To: user@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image001.png@01DC5F94.68958460]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image002.png@01DC5F94.68958460]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com>.
Hi, Brendan,
Sorry for the delay. I decided to wipe the slate clean and begin from the start.
So, now I am thinking the important part is the actual source.
I followed your link and downloaded the ZIP. I corrected the tagsync typo and rebuilt. No problems. I installed, created a test cluster and re-installed to targets.
[cid:image003.png@01DC5F94.DBAF0070]
So I tried installing on one target via commandline: yum install -y Hadoop_3_0_0
Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded into the source somewhere. Surely this would make any attempt to upgrade a complete failure?
Where am I looking to fix in the source?
Marc
From: Brenden Cobb <bc...@blackduck.com>
Sent: Thursday, November 20, 2025 10:25 PM
To: user@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image001.png@01DC5F94.68958460]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image002.png@01DC5F94.68958460]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com>.
I appreciate the info.
I am wondering if this is widespread.
I downloaded the ZIP, I didn’t use clone.
I am also wondering why no one involved in the project just didn’t fix the typo, rebuild and put fixed RPMs up in the same place? I ask as fixing a typo by adding a single character should not result in a final build size of some significant difference. Yet building the package using the linked version you gave me does have vastly more than a byte’s worth of difference.
From: Brenden Cobb <bc...@blackduck.com>
Sent: Thursday, November 20, 2025 10:25 PM
To: user@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image001.png@01DC5D2F.C780B7E0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image002.png@01DC5D2F.C780B7E0]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
Re: [EXT]Re: Help needed
Posted by Brenden Cobb <bc...@blackduck.com>.
I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo available? What happens when you try to execute the yum install command that is producing the error?
From: Marc Hoppins <ma...@eset.com.INVALID>
Date: Thursday, November 20, 2025 at 3:49 AM
To: user@ambari.apache.org <us...@ambari.apache.org>
Subject: RE: [EXT]Re: Help needed
Well, after doing all those steps…
[cid:image002.png@01DC5A02.ECD88700]
From: Brenden Cobb <bc...@blackduck.com.INVALID>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image003.png@01DC5A02.ECD88700]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com.INVALID>.
Well, after doing all those steps…
[cid:image002.png@01DC5A02.ECD88700]
From: Brenden Cobb <bc...@blackduck.com.INVALID>
Sent: Wednesday, November 19, 2025 9:03 PM
To: user@ambari.apache.org
Subject: Re: [EXT]Re: Help needed
[External Sender]
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image003.png@01DC5A02.ECD88700]
From: Brenden Cobb <bc...@blackduck.com.INVALID>>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>; dev@ambari.apache.org<ma...@ambari.apache.org>
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
Re: [EXT]Re: Help needed
Posted by Brenden Cobb <bc...@blackduck.com.INVALID>.
Seems like there may be some artifacts from previous installation
These are steps I have used before to clean up, prior to re-installing:
https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114
From: Marc Hoppins <ma...@eset.com.INVALID>
Date: Wednesday, November 19, 2025 at 9:15 AM
To: user@ambari.apache.org <us...@ambari.apache.org>, dev@ambari.apache.org <de...@ambari.apache.org>
Subject: RE: [EXT]Re: Help needed
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image001.png@01DC5964.CF6B4E30]
From: Brenden Cobb <bc...@blackduck.com.INVALID>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org; dev@ambari.apache.org
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc
RE: [EXT]Re: Help needed
Posted by Marc Hoppins <ma...@eset.com.INVALID>.
Hi, Brendan,
I appreciate the information. I downloaded and rebuilt 3.0.0.
First, ambari-server changed from a HASH=”hexnumber” to HASH=”${buildnumber}” which fails the server start.
Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is failing host installs. Where am I likely to find this problem because selecting in the ambari UI is not making the right choice. I dumped the ambari database and started afresh but no joy.
[cid:image001.png@01DC5964.CF6B4E30]
From: Brenden Cobb <bc...@blackduck.com.INVALID>
Sent: Tuesday, November 18, 2025 8:05 PM
To: user@ambari.apache.org; dev@ambari.apache.org
Subject: [EXT]Re: Help needed
[External Sender]
Hi -
The latest release of Ambari is version 3.0.0. Running a later build is likely to surface errors.
To try and fix the Ranger issue from your previous email, I would suggest building Ambari version 3.0.0 https://github.com/apache/ambari/tree/release-3.0.0, patched with the change in: https://issues.apache.org/jira/browse/AMBARI-26427
From: Marc Hoppins <ma...@eset.com.INVALID>>
Date: Tuesday, November 18, 2025 at 8:01 AM
To: user@ambari.apache.org<ma...@ambari.apache.org> <us...@ambari.apache.org>>, dev@ambari.apache.org<ma...@ambari.apache.org> <de...@ambari.apache.org>>
Subject: Help needed
Hi, All…Anyone,
I downloaded and tried 3.0.0 but got the ranger error regarding translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar with all of eclipse but assume I got things right as I saw no errors.
I installed 3.1.0 and purged any packages on my target nodes. I then installed the ambari-agent on targets to 3.1.0.
I started with a clean ambari database.
I did not download and build either metrics or infra but stuck with the existing rpms from the 3.0.0 install.
I was a bit concerned with the ‘build from source’ instructions as it is suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9.
Running the ambari server now, I see cluster install options for BIGTOP 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my repository setup with 3.3.0 and was expecting I could use that.
Warnings and errors abound and when I checked the running process I saw a running agent process
/usr/bin/python3 /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package….
If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to use 3.3.0 or 3.4.0 why are they included?
Any information would be appreciated.
Marc