Member since
07-25-2020
34
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
9120 | 02-15-2021 04:30 AM |
04-06-2021
10:54 PM
@emeric I am afraid that MondoDB is not supported and hardly will work with Cloudera as this is NoSQL DB while the Cloudera Manager and other CDH service which requires database is needs to be RDBMS. So you have to go with any RDBMS listed in the supported matrix. https://docs.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_database_requirements.html
... View more
03-18-2021
03:47 AM
@Shelton I sent you a request.
... View more
03-14-2021
09:02 PM
We are seeing port bind exception in the error stack trace which basically means the secondary NN service is unable to register itself on that port. Port 50090 is the internal port defined by this property "dfs.secondary.http.address or dfs.namenode. secondary. http-address". So please run "netstat -anp | grep 50090" and see which process is using the port in question. Stop that process and try starting Secondary NN service or else we need to change the default port in the abovementioned property to some other non-used port.
... View more
02-15-2021
04:30 AM
I found my log4j.properties file (my case ./workspace/training/conf/log4j.properties) and i and added these two lines and it solved the problem : log4j.appender.RFA=org.apache.log4j.ConsoleAppender log4j.appender.RFA.layout=org.apache.log4j.PatternLayout
... View more
10-20-2020
12:04 PM
@emeric Looking at your logs seems to be a port issue and you have to check if port is listening or not.
... View more
10-12-2020
06:10 AM
Here is what my amabri agent logs look like. I don't understand anything.
... View more
09-29-2020
07:30 AM
I already had many alerts for errors before even trying to start the services. Here is a folder with screenshots of all the alerts.
... View more
08-20-2020
04:26 PM
I did a trial installation using cloudera-manager-installer.bin. I have been looking for a solution of this problem for weeks now, without being able to find one. Any ideas on how i can resolve this?
... View more
08-06-2020
01:45 AM
1 Kudo
Hello @emeric , the "kinit: KDC has no support for encryption type while getting initial credentials" usually occurs after configuring encryption types that do not match the ones present in the tgt principal (such as krbtgt/CLOUDERA@CLOUDERA) in the KDC. This can also happen while starting a service where the enctypes in the krbtgt principal do not match those used in service keytab. From an earlier Community post: Please compare the Kerberos server and client configurations and reconfigure krb5.conf on all your nodes to explicitly use the supported encryption type. The documentation describes: "Kerberos client OS-specific packages must be installed on all cluster hosts and client hosts that will authenticate using Kerberos." Wondering if some missing packages might be the issue? Kind regards: Ferenc
... View more