@rizalt  There is very little detail in your post. NiFi will run as whatever user is used to start it unless the "run.as" property is set in the NiFi bootstrap.conf file. If the user trying to execute the "./nifi.sh start" command is not the root user and you set the "run.as" property to "root", that user would need sudo permissions in linux to start NiFi as the root user.    The "run.as" property is ignored on Windows where the service will always be owned by user that starts it. NOTE: Starting the service as a different user then it was previously started at will not trigger a change in file ownership in NiFi directories. You would need to update file ownership manually be starting as a different issue (this includes all NiFi's repositories). While "root" user has access to all files regardless of owner, issues will exist if no root user launches app and files are owned by another user including root. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@rizalt  Yes, the Key Version Numbers (KVNO) of different principals can indeed be different. Each principal in Kerberos can have its own KVNO, which is an identifier that increments each time the key for that principal is changed. Reference: https://web.mit.edu/kerberos/www/krb5-latest/doc/user/user_commands/kvno.html#:~:text=specified%20Kerberos%20principals   Regards, Chethan YM ... View more

Thanks for the reply @shubham_sharma, I'm not using AD account just kerberos ... View more

@rizalt It's hard to talk to a solution here without a lot more details (version of stack, ambari, java, etc).  That said,  some of the hits I find against this error are from 2017(many years ago).  There is a great risk to operate Ambari as it is no longer supported and available within the Cloudera ecosystem.       I would recommend you evaluate modern solutions (CDP) for the same stack of services you are familar with in Ambari. ... View more

Hi @rizalt  The error is because you have not provided keytab path here the command should look like below: > klist -k example.keytab To create the keytab you can refer any of below steps: $ ktutil ktutil: addent -password -p myusername@FEDORAPROJECT.ORG -k 42 -f Password for myusername@FEDORAPROJECT.ORG: ktutil: wkt /tmp/kt/fedora.keytab ktutil: q Then kinit -kt /tmp/kt/fedora.keytab myusername@FEDORAPROJECT.ORG Note: Replace the username and REALM as per your cluster configurations. Regards, Chethan YM ... View more

I tried command kinit to make sure the password is correct, but message kinit is " password incorrect while getting initial credential" like below   root@master1:~# kinit nm/slave1.hadoop.com@HADOOP.COM Password for nm/slave1.hadoop.com@HADOOP.COM: kinit: Password incorrect while getting initial credentials   What should recreate principal/change the password ? Please give me suggestion, I'm sure the password is correct   ... View more

@Shelton   I'm using Ubuntu 22.04 & using ODP (https://clemlabs.s3.eu-west-3.amazonaws.com/ubuntu22/odp-release/1.2.2.0-46/ODP) ... View more

@Scharan  My Hostname in my kdc server   *** System restart required *** Last login: Thu May 30 07:23:57 2024 from 192.168.7.211 root@admin:~# hostname admin.com root@admin:~#   in my client host   root@slave2:~# ping admin.com PING admin.com (192.168.7.4) 56(84) bytes of data. 64 bytes from admin.com (192.168.7.4): icmp_seq=1 ttl=64 time=0.608 ms 64 bytes from admin.com (192.168.7.4): icmp_seq=2 ttl=64 time=0.669 ms 64 bytes from admin.com (192.168.7.4): icmp_seq=3 ttl=64 time=0.561 ms 64 bytes from admin.com (192.168.7.4): icmp_seq=4 ttl=64 time=1.94 ms   ... View more

what are you setting in /etc/hostname ?  the same issue in my setup Kerberos ... View more

@rizalt I had a same bug when used ODP stack to deploy Ambari.  After debug, I found code in ambari-agent bug when runtime to try start Hive Server2. Problem: This below codes output {out} parameter to handle hdfs path, but this code returned not valid hdfs URI   163 metatool_cmd = format("hive --config {conf_dir} --service metatool") 164 cmd = as_user(format("{metatool_cmd} -listFSRoot", env={'PATH': execution_path}), params.hive_user) \ 165 + format(" 2>/dev/null | grep hdfs:// | cut -f1,2,3 -d '/' | grep -v '{fs_root}' | head -1") 166 code, out = shell.call(cmd)     2024-04-03 07:40:48,317 - call['ambari-sudo.sh su hive -l -s /bin/bash -c 'hive --config /usr/odp/current/hive-server2/conf/ --service metatool -listFSRoot' 2>/dev/null | grep hdfs:// | cut -f1,2,3 -d '/' | grep -v 'hdfs://vm-ambari.internal.cloudapp.net:8020' | head -1'] {} 2024-04-03 07:40:58,721 - call returned (0, '07:40:53.268 [main] DEBUG org.apache.hadoop.fs.FileSystem - hdfs:// = class org.apache.hadoop.hdfs.DistributedFileSystem from ') To fix: Step 1: edit row 170 in file "/var/lib/ambari-agent/cache/stacks/ODP/1.0/services/HIVE/package/scripts/hive_service.py" as below: I hard code old_path to valid URI, this help by pass updateLocation config   # cmd = format("{metatool_cmd} -updateLocation {fs_root} {out}") cmd = format("{metatool_cmd} -updateLocation {fs_root} hdfs://oldpath")   You can see as below image: Step 2: Restart ambari agent   sudo ambari-agent restart   Step 3: Try to restart Hive server2 in Ambari  Service started successful. ... View more