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 <[email protected]> Date: Tuesday, November 18, 2025 at 8:01 AM To: [email protected] <[email protected]>, [email protected] <[email protected]> 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
