Member since
04-22-2014
1218
Posts
341
Kudos Received
157
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 26248 | 03-03-2020 08:12 AM | |
| 16395 | 02-28-2020 10:43 AM | |
| 4716 | 12-16-2019 12:59 PM | |
| 4472 | 11-12-2019 03:28 PM | |
| 6657 | 11-01-2019 09:01 AM |
01-03-2018
10:53 AM
@DataYogi, IPv4 is a function of your OS networking, so that is a matter for your host and network configuration. My point is that if you are unfamiliar with how database servers and other servers interact over IPv6, perhaps it would be best to only use IPv4 for now. See the following postgres information regarding addresses (including IPv6) https://www.postgresql.org/docs/9.3/static/auth-pg-hba-conf.html It appears you were missing the /64 subnet portion of the IP as your interface shows: inet6 addr: 2402:1f00:8001:281::/64 Scope:Global I believe either of the following in the pg_hba.conf file would allow access from that one host: host hue hue 2402:1f00:8001:281::/64 md5 or host hue hue 2402:1f00:8001:281::/128 md5 Unless you need to restrict access, you can add lines to allow access from any host that is IPv6 with the following: host hue hue ::0/0 md5 NOTE: Make sure you ensure there are no servers connecting to the embedded postgres database and restart from the command line with "service cloudera-scm-server-db restart" after making any changes to ensure they took effect.
... View more
12-29-2017
09:49 AM
Sorry for the late reply; glad you did it and now you know it was the perfect solution. Cheers!
... View more
12-12-2017
02:44 PM
Apparently, the problem was with the 'repodata' I had. The issue got resolved once I created the new repodata for my install-dir where I had all my install files. I downloaded and installed 'createrepo' tool first and then ran the following using the tool: createrepo /home/cloudera/install-files This created a new repodata dir and the files and after this my installation succeeded without any error.
... View more
11-30-2017
12:53 AM
To clarify we don't have HA setup for mysql, but do use external mysql database for CDH services, which is located on one of the namenodes (we have HA Hadoop cluster). Cloudera management services use another mysql database on another host.
... View more
11-26-2017
05:26 PM
Thanks for the reply, after I rebooted the OS, the mysql will not start again.
... View more
11-23-2017
01:54 AM
1 Kudo
Thanks , After verifying logs : I have change the hostname without special characters and updated the hostname entry in /etc/sysconfig/network and Adjusted Custom security group in AWS console after that installation was succussful. Now we want to customize the Security group in AWS, could please suggest which are protocols and services and ports need to open for cloudera. Thanks alot for your help...
... View more
11-23-2017
12:37 AM
Hi Ben, Thank you very much for your explanations. Especially I appreciated your clarification about service/client configuration difference and how to enable client configuration for yarn. It solves my issue, thanks a million. Regards, Sz
... View more
11-19-2017
05:01 AM
1 Kudo
@PSG01 No problem. Check out this documentation for some background on where the charts data comes from: https://www.cloudera.com/documentation/enterprise/latest/topics/cm_dg_chart_time_series_data.html metrics are stored in the Host Monitor and Service Monitor. The data used in chart building is avaiable via the tsquery results. The actual data is stored in leveldb files on disk (by default in /var/lib/cloudera-host-monitor and /var/lib/cloudera-service-monitor) If you wish to view the metrics in JSON format you can click on the properties icon in the chart and choose "Export JSON" -Ben
... View more
11-13-2017
11:31 AM
I continued the resolution of this issue in another thread specific to the error: ls: Operation category READ is not supported in state standby The solution is marked on that thread, however, a quick summary was that I needed to add the Failover Controller role to a node in my cluster, enable Automatic Failover, and then restart the cluster for it all to kick in.
... View more
11-09-2017
07:37 AM
I've discovered by painful experience that this might be caused by having more than one oracle java installed, and even worse, any version of openjdk java. Namely, make sure you have added the ca you used for the ssl to the java keystore of the java version you are using (you can find that out in process list). Also, make sure that keytool you are using is belonging to this version of java - so it's best to have only one version installed, or (if that is unavoidable), use the full path to keytool. Hope it helps.
... View more