@jkoral FYI   ➤ Based on the logs provided, the checkpoint failure is caused by an authentication mismatch during the FSImage upload process, further complicated by an underlying storage type configuration issue   ➤ Primary Reason: Authentication Failure (403 Forbidden) The Standby NameNode (SNN) successfully performs the checkpoint locally but fails to upload the merged fsimage back to the Active NameNode (NN). -The Error: The SNN logs report: java.io.IOException: Exception during image upload: Response: 403 (Forbidden), Message: Non-exception fault: Authentication failed. -The Mechanism: After merging the edits, the SNN attempts to POST the new image to the NN via HTTP. The NN rejects this request because it cannot verify the identity of the SNN, which is common in new clusters where Kerberos or shared secret configurations are not fully synchronized.     ➤ Recommended Fixes Verify HTTP Authentication: Check the dfs.namenode.secondary.http-address and dfs.namenode.http-address settings. Ensure the hdfs user has consistent permissions across both hosts. Check Firewall/SELinux: Since this is RHEL9, ensure that the SNN can communicate with the NN on port 9870 (or 9871 if SSL is enabled). ... View more

Kshitij, Wow, that worked like a charm. When I was granting privileges to the database, I was using the following statement for all three of those including the actual password, but that did not work for me. GRANT ALL ON rman.* TO 'rman'@'%' IDENTIFIED BY 'password'; I am not really a DB person, so figured I would get the right solution from someone that is. I was going to say to keep an eye for my next posted issue regarding HDFS, but it looks like after fixing the DB issue and after restarting HDFS, we are all GREEN now!!! ... View more

Sorry about that. I'll keep that in mind for the future. I was able to resolve the issue though. Thank you.  ... View more

Thank you very much. I have setup the timezone in my.cnf. ... View more