Member since
07-16-2016
22
Posts
0
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3808 | 08-17-2017 03:33 AM | |
2877 | 08-10-2017 06:40 AM | |
2176 | 12-23-2016 02:07 AM |
08-17-2017
03:33 AM
I've reinstalled Hive and it's solved! Thanks
... View more
08-16-2017
05:15 AM
Hi, I've installed cloudera manager with Hive but when I'm trying to start the role, it gives me: PSQLException: FATAL: password authentication failed for user "hive" How fix it? Thanks and sorry for my English!
... View more
Labels:
- Labels:
-
Apache Hive
-
Cloudera Manager
08-14-2017
02:52 AM
Hi, I can't understand why capactiy is 0: afe mode is ON
Configured Capacity: 0 (0 B)
Present Capacity: 0 (0 B)
DFS Remaining: 0 (0 B)
DFS Used: 0 (0 B)
DFS Used%: NaN%
Under replicated blocks: 0
Blocks with corrupt replicas: 0
Missing blocks: 0
Missing blocks (with replication factor 1): 0
-------------------------------------------------
report: Access denied for user root. Superuser privilege is required
root@clusterb1:/var/log/hadoop-mapreduce# sudo -u hdfs dfsadmin -report
sudo: dfsadmin: orden no encontrada
root@clusterb1:/var/log/hadoop-mapreduce# sudo -u hdfs hdfs dfsadmin -report
Safe mode is ON
Configured Capacity: 0 (0 B)
Present Capacity: 0 (0 B)
DFS Remaining: 0 (0 B)
DFS Used: 0 (0 B)
DFS Used%: NaN%
Under replicated blocks: 0
Blocks with corrupt replicas: 0
Missing blocks: 0
Missing blocks (with replication factor 1): 0
-------------------------------------------------
Dead datanodes (4):
Name: 192.168.1.114:50010 (clusterb4.dummy.es)
Hostname: clusterb4.dummy.es
Decommission Status : Normal
Configured Capacity: 0 (0 B)
DFS Used: 0 (0 B)
Non DFS Used: 0 (0 B)
DFS Remaining: 0 (0 B)
DFS Used%: 100.00%
DFS Remaining%: 0.00%
Configured Cache Capacity: 0 (0 B)
Cache Used: 0 (0 B)
Cache Remaining: 0 (0 B)
Cache Used%: 100.00%
Cache Remaining%: 0.00%
Xceivers: 0
Last contact: Thu Jan 01 01:00:00 CET 1970
Name: 192.168.1.115:50010 (clusterb5.dummy.es)
Hostname: clusterb5.dummy.es
Decommission Status : Normal
Configured Capacity: 0 (0 B)
DFS Used: 0 (0 B)
Non DFS Used: 0 (0 B)
DFS Remaining: 0 (0 B)
DFS Used%: 100.00%
DFS Remaining%: 0.00%
Configured Cache Capacity: 0 (0 B)
Cache Used: 0 (0 B)
Cache Remaining: 0 (0 B)
Cache Used%: 100.00%
Cache Remaining%: 0.00%
Xceivers: 0
Last contact: Thu Jan 01 01:00:00 CET 1970
Name: 192.168.1.112:50010 (clusterb2.dummy.es)
Hostname: clusterb2.dummy.es
Decommission Status : Normal
Configured Capacity: 0 (0 B)
DFS Used: 0 (0 B)
Non DFS Used: 0 (0 B)
DFS Remaining: 0 (0 B)
DFS Used%: 100.00%
DFS Remaining%: 0.00%
Configured Cache Capacity: 0 (0 B)
Cache Used: 0 (0 B)
Cache Remaining: 0 (0 B)
Cache Used%: 100.00%
Cache Remaining%: 0.00%
Xceivers: 0
Last contact: Thu Jan 01 01:00:00 CET 1970
Name: 192.168.1.113:50010 (clusterb3.dummy.es)
Hostname: clusterb3.dummy.es
Decommission Status : Normal
Configured Capacity: 0 (0 B)
DFS Used: 0 (0 B)
Non DFS Used: 0 (0 B)
DFS Remaining: 0 (0 B)
DFS Used%: 100.00%
DFS Remaining%: 0.00%
Configured Cache Capacity: 0 (0 B)
Cache Used: 0 (0 B)
Cache Remaining: 0 (0 B)
Cache Used%: 100.00%
Cache Remaining%: 0.00%
Xceivers: 0
Last contact: Thu Jan 01 01:00:00 CET 1970
Someone knows why is 0? I'm using lxc but I think that is not a problem. Thanks!
... View more
Labels:
- Labels:
-
Manual Installation
08-10-2017
06:05 AM
Hi, I'm trying to install cloudera manager with lxc. I've set up 4 nodes and my local node. When I'm trying to install software from cloudera wizard it says me: Authentication error. "Exhausted available authentication methods"
... View more
Labels:
- Labels:
-
Cloudera Manager
12-23-2016
02:07 AM
Solved! the problem was that I clone lxc container and the /etc/hosts was the same in all machines. I've modified the /etc/hosts and all ok
... View more
12-23-2016
01:32 AM
Hi, I'm trying to instal cloudera manager in some host virutalized with lxc. In one installation is completed but in the rest of host failed with these error: Error en la instalación. Error al recibir el latido del agente. •Asegúrese de que el nombre del host está configurado correctamente.
•Asegúrese de que el puerto 7182 es accesible en Cloudera Manager Server (compruebe las reglas del firewall).
•Asegúrese de que los puertos 9000 y 9001 no están en uso para el host que se va a agregar.
•Compruebe los registros de agente en /var/log/cloudera-scm-agent/ en el host que va a agregar. (Algunos registros se pueden encontrar en los detalles de instalación).
•Si la opción Utilizar el cifrado de TLS para los agentes está activada en Cloudera Manager (Administración -> Ajustes -> Seguridad), compruebe que /etc/cloudera-scm-agent/config.ini tiene use_tls=1 en el host que se agrega. Reinicie el agente correspondiente y haga clic en el vínculo Reintentar aquí. Someone could help me please? Thanks!
... View more
Labels:
- Labels:
-
Manual Installation