thank you for that, the installation finished that step and has now only 2 steps left, unfortunately hops:nm failed
hops::nm | FAILED| retry skip log| 73455
e[32m- change mode from ‘’ to '0774’e[0m
e[32m- change owner from ‘’ to 'root’e[0m
e[32m- restore selinux security contexte[0m
e[0m * kagent_config[nodemanager] action systemd_reload
* bash[start-if-not-running-nodemanager] action run[2020-08-11T10:58:32-04:00] ERROR: bash[start-if-not-running-nodemanager] (/tmp/chef-solo/cookbooks/kagent/providers/config.rb line 49) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received ‘1’
---- Begin output of “bash” “/chef-script20200811-26266-1o725ri” ----
STDOUT:
STDERR: Job for nodemanager.service failed because the control process exited with error code. See “systemctl status nodemanager.service” and “journalctl -xe” for details.
---- End output of “bash” “/chef-script20200811-26266-1o725ri” ----
Ran “bash” “/chef-script20200811-26266-1o725ri” returned 1; ignore_failure is set, continuing
e[0m
================================================================================e[0m
e[31mError executing action `run` on resource 'bash[start-if-not-running-nodemanager]'e[0m
================================================================================e[0m
e[0m Mixlib::ShellOut::ShellCommandFailede[0m
------------------------------------e[0m
Expected process to exit with [0], but received ‘1’
e[0m ---- Begin output of “bash” “/chef-script20200811-26266-1o725ri” ----
e[0m STDOUT:
e[0m STDERR: Job for nodemanager.service failed because the control process exited with error code. See “systemctl status nodemanager.service” and “journalctl -xe” for details.
e[0m ---- End output of “bash” “/chef-script20200811-26266-1o725ri” ----
e[0m Ran “bash” “/chef-script20200811-26266-1o725ri” returned 1e[0m
e[0m Resource Declaration:e[0m
journalctl -xe
Aug 11 12:37:10 per320-2.server airflow_runner.sh[33874]: [2020-08-11 12:37:10,418] {jobs.py:1559} INFO - Harvesting DAG parsing results
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: 2020-08-11 10:58:30,811 INFO org.apache.hadoop.yarn.server.nodemanager.NodeManager: STARTUP_MSG:
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: /************************************************************
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: STARTUP_MSG: Starting NodeManager
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: STARTUP_MSG: user = yarn
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: STARTUP_MSG: host = per320-2.server/192.168.0.230
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: STARTUP_MSG: args = []
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: STARTUP_MSG: version = 2.8.2.10-RC1
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: STARTUP_MSG: classpath = /srv/hops/hadoop/etc/hadoop:/srv/hops/hadoop/etc/hadoop:/srv/hops/hadoop/et
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: STARTUP_MSG: build = git@github.com:hopshadoop/hops.git -r abc3abcdf67a1e49fd6d0b8b381a23a677996a18;
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: STARTUP_MSG: java = 1.8.0_262
Aug 11 12:37:11 per320-2.server systemd[1]: nodemanager.service: control process exited, code=exited status=1
Aug 11 12:37:11 per320-2.server start-nm.sh[19924]: /srv/hops/hadoop/sbin/start-nm.sh: line 24: kill: (19965) - No such process
Aug 11 12:37:11 per320-2.server systemd[1]: Failed to start NodeManager. The Processing Nodes for YARN…
– Subject: Unit nodemanager.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit nodemanager.service has failed.
–
– The result is failed.