Запуск файловой системы Hadoop с разрешением `start-dfs.sh` запрещен
Я пытаюсь установить hbase one как отдельный узел, но у меня есть проблема с запуском файловой системы Hadoop с start-dfs.sh:
mike@mike-thinks:/usr/local/hadoop/sbin$ ./start-dfs.sh
Incorrect configuration: namenode address dfs.namenode.servicerpc-address or dfs.namenode.rpc-address is not configured.
Starting namenodes on []
./start-dfs.sh: line 61: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
./start-dfs.sh: line 74: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
Starting secondary namenodes [0.0.0.0]
./start-dfs.sh: line 87: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
И с sudo:
mike@mike-thinks:/usr/local/hadoop/sbin$ sudo ./start-dfs.sh
[sudo] password for mike:
Incorrect configuration: namenode address dfs.namenode.servicerpc-address or dfs.namenode.rpc-address is not configured.
Starting namenodes on []
./start-dfs.sh: line 61: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
./start-dfs.sh: line 74: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
Starting secondary namenodes [0.0.0.0]
./start-dfs.sh: line 87: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
Так Я сделал sudo chmod +x /usr/local/hadoop/sbin/
mike@mike-thinks:/usr/local/hadoop/sbin$ sudo chmod +x /usr/local/hadoop/sbin/
[sudo] password for mike:
mike@mike-thinks:/usr/local/hadoop/sbin$ ./start-dfs.sh
Incorrect configuration: namenode address dfs.namenode.servicerpc-address or dfs.namenode.rpc-address is not configured.
Starting namenodes on []
./start-dfs.sh: line 61: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
./start-dfs.sh: line 74: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
Starting secondary namenodes [0.0.0.0]
./start-dfs.sh: line 87: /usr/local/hadoop/sbin/hadoop-daemons.sh: Permission denied
Я еще не пытался перейти к sshd_config, изменить PermitRootLogin без пароля -> PermitRootLogin yes и выполнить ssh-перезапуск, как предполагает gsamaras в , связанный с этим вопрос но вряд ли это будет связано.
Я сделал chmod +x *.sh, и это решило проблему. И теперь у меня есть ошибка Incorrect configuration:
mike@mike-thinks:/usr/local/hadoop/sbin$ ./start-dfs.sh
Incorrect configuration: namenode address dfs.namenode.servicerpc-address or dfs.namenode.rpc-address is not configured.
Starting namenodes on []
localhost: mkdir: cannot create directory ‘/usr/local/hadoop/logs’: Permission denied
localhost: chown: cannot access '/usr/local/hadoop/logs': No such file or directory
localhost: starting namenode, logging to /usr/local/hadoop/logs/hadoop-mike-namenode-mike-thinks.out
localhost: /usr/local/hadoop/sbin/hadoop-daemon.sh: line 159: /usr/local/hadoop/logs/hadoop-mike-namenode-mike-thinks.out: No such file or directory
localhost: head: cannot open '/usr/local/hadoop/logs/hadoop-mike-namenode-mike-thinks.out' for reading: No such file or directory
localhost: /usr/local/hadoop/sbin/hadoop-daemon.sh: line 177: /usr/local/hadoop/logs/hadoop-mike-namenode-mike-thinks.out: No such file or directory
localhost: /usr/local/hadoop/sbin/hadoop-daemon.sh: line 178: /usr/local/hadoop/logs/hadoop-mike-namenode-mike-thinks.out: No such file or directory
localhost: mkdir: cannot create directory ‘/usr/local/hadoop/logs’: Permission denied
localhost: chown: cannot access '/usr/local/hadoop/logs': No such file or directory
localhost: starting datanode, logging to /usr/local/hadoop/logs/hadoop-mike-datanode-mike-thinks.out
localhost: /usr/local/hadoop/sbin/hadoop-daemon.sh: line 159: /usr/local/hadoop/logs/hadoop-mike-datanode-mike-thinks.out: No such file or directory
localhost: head: cannot open '/usr/local/hadoop/logs/hadoop-mike-datanode-mike-thinks.out' for reading: No such file or directory
localhost: /usr/local/hadoop/sbin/hadoop-daemon.sh: line 177: /usr/local/hadoop/logs/hadoop-mike-datanode-mike-thinks.out: No such file or directory
localhost: /usr/local/hadoop/sbin/hadoop-daemon.sh: line 178: /usr/local/hadoop/logs/hadoop-mike-datanode-mike-thinks.out: No such file or directory
Starting secondary namenodes [0.0.0.0]
The authenticity of host '0.0.0.0 (0.0.0.0)' can't be established.
ECDSA key fingerprint is SHA256:/s7X8QMliB6FVx5bde5AaCycprQ/B+NtcTXrInrXxJM.
Are you sure you want to continue connecting (yes/no)? no
0.0.0.0: Host key verification failed.
0
задан ThePassenger
5 December 2017 в 17:10
поделиться
1 ответ
# Create the .ssh directory:
$ mkdir ~/.ssh
# Set the right permissions:
$ chmod 700 ~/.ssh
# Create the authorized_keys file:
$ touch ~/.ssh/authorized_keys
# Set the right permissions:
$ chmod 600 ~/.ssh/authorized_keys
Разрешения важны! Он не будет работать без необходимых разрешений!
Теперь вы можете добавить открытый ключ в файл authorized_keys:
$ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
И, наконец, вы можете выполнить:
$ ./start-dfs.sh
0
ответ дан Simon Sudler
5 December 2017 в 17:10
поделиться