Reply
New Contributor
Posts: 3
Registered: ‎02-07-2018

Failed to start LSB: Hadoop resourcemanager.

Hi I tried installing clouderas cdh5 in pseudo mode on ubuntu 16.04. When trying to 

hadoop jar /usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar grep input output23 'dfs[a-z.]+'

 the job does not end and i get 

   18/02/07 21:38:48 INFO ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 6 time(s); retry      policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)

 

Finally when trying to restart yarn I get 

● hadoop-yarn-resourcemanager.service - LSB: Hadoop resourcemanager
   Loaded: loaded (/etc/init.d/hadoop-yarn-resourcemanager; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since mié 2018-02-07 21:43:03 -03; 28s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 12669 ExecStop=/etc/init.d/hadoop-yarn-resourcemanager stop (code=exited, status=0/SUCCESS)
  Process: 12708 ExecStart=/etc/init.d/hadoop-yarn-resourcemanager start (code=exited, status=1/FAILURE)

feb 07 21:42:57 felipe-MS-7A63 su[12800]: pam_unix(su:session): session opened for user yarn by (uid=0)
feb 07 21:42:57 felipe-MS-7A63 hadoop-yarn-resourcemanager[12708]: starting resourcemanager, logging to /var/log/hadoop-yarn/yarn-yarn-resourcemanager
feb 07 21:42:58 felipe-MS-7A63 hadoop-yarn-resourcemanager[12708]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
feb 07 21:42:58 felipe-MS-7A63 hadoop-yarn-resourcemanager[12708]: SLF4J: Defaulting to no-operation (NOP) logger implementation
feb 07 21:42:58 felipe-MS-7A63 hadoop-yarn-resourcemanager[12708]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
feb 07 21:43:03 felipe-MS-7A63 hadoop-yarn-resourcemanager[12708]:  * Failed to start Hadoop resourcemanager. Return value: 1
feb 07 21:43:03 felipe-MS-7A63 systemd[1]: hadoop-yarn-resourcemanager.service: Control process exited, code=exited status=1
feb 07 21:43:03 felipe-MS-7A63 systemd[1]: Failed to start LSB: Hadoop resourcemanager.
feb 07 21:43:03 felipe-MS-7A63 systemd[1]: hadoop-yarn-resourcemanager.service: Unit entered failed state.
feb 07 21:43:03 felipe-MS-7A63 systemd[1]: hadoop-yarn-resourcemanager.service: Failed with result 'exit-code'.

[2]+  Stopped                 systemctl status hadoop-yarn-resourcemanager.service

and 

 

-- Unit hadoop-yarn-resourcemanager.service has failed.
-- 
-- The result is failed.
feb 07 21:43:03 felipe-MS-7A63 systemd[1]: hadoop-yarn-resourcemanager.service: Unit entered failed state.
feb 07 21:43:03 felipe-MS-7A63 systemd[1]: hadoop-yarn-resourcemanager.service: Failed with result 'exit-code'.
feb 07 21:43:03 felipe-MS-7A63 sudo[12663]: pam_unix(sudo:session): session closed for user root
feb 07 21:43:18 felipe-MS-7A63 dhclient[1365]: DHCPREQUEST of 192.168.0.106 on enp0s31f6 to 192.168.0.1 port 67 (xid=0x7b784668)
feb 07 21:43:19 felipe-MS-7A63 dhclient[1365]: DHCPACK of 192.168.0.106 from 192.168.0.1
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   address 192.168.0.106
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   plen 24 (255.255.255.0)
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   gateway 192.168.0.1
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   server identifier 192.168.0.1
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   lease time 3600
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   nameserver '200.115.192.29'
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   nameserver '200.115.192.89'
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   nameserver '200.115.192.30'
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6819]   domain name 'cpe.telecentro.net.ar'
feb 07 21:43:19 felipe-MS-7A63 NetworkManager[965]: <info>  [1518050599.6820] dhcp4 (enp0s31f6): state changed bound -> bound
feb 07 21:43:19 felipe-MS-7A63 dbus[959]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-
feb 07 21:43:19 felipe-MS-7A63 systemd[1]: Starting Network Manager Script Dispatcher Service...
-- Subject: Unit NetworkManager-dispatcher.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit NetworkManager-dispatcher.service has begun starting up.
feb 07 21:43:19 felipe-MS-7A63 dbus[959]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
feb 07 21:43:19 felipe-MS-7A63 systemd[1]: Started Network Manager Script Dispatcher Service.
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit NetworkManager-dispatcher.service has finished starting up.
-- 
-- The start-up result is done.
feb 07 21:43:19 felipe-MS-7A63 nm-dispatcher[13139]: req:1 'dhcp4-change' [enp0s31f6]: new request (1 scripts)
feb 07 21:43:19 felipe-MS-7A63 nm-dispatcher[13139]: req:1 'dhcp4-change' [enp0s31f6]: start running ordered scripts...
feb 07 21:43:19 felipe-MS-7A63 dhclient[1365]: bound to 192.168.0.106 -- renewal in 1379 seconds.
feb 07 21:45:01 felipe-MS-7A63 CRON[13515]: pam_unix(cron:session): session opened for user root by (uid=0)
feb 07 21:45:01 felipe-MS-7A63 CRON[13516]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
feb 07 21:45:01 felipe-MS-7A63 CRON[13515]: pam_unix(cron:session): session closed for user root

Than you in advance any help will be well apreciated.

 

Champion
Posts: 744
Registered: ‎05-16-2016

Re: Failed to start LSB: Hadoop resourcemanager.

[ Edited ]

what is the status on namenode ? secondary namenode ? 

did you configure /etc/host - ? 

could you share the full stack trace of Resouce manager logs with exception / error 

Highlighted
New Contributor
Posts: 3
Registered: ‎02-07-2018

Re: Failed to start LSB: Hadoop resourcemanager.

Hi, thank you.

Regarding namenodes upon installation I get 

 

 

invoke-rc.d: initscript hadoop-hdfs-namenode, action "start" failed.
● hadoop-hdfs-namenode.service - LSB: Hadoop namenode
   Loaded: loaded (/etc/init.d/hadoop-hdfs-namenode; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since mié 2018-02-14 10:52:48 -03; 2ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 10252 ExecStart=/etc/init.d/hadoop-hdfs-namenode start (code=exited, status=1/FAILURE)

feb 14 10:52:39 felipe-MS-7A63 su[10270]: pam_unix(su:session): session open...)
feb 14 10:52:39 felipe-MS-7A63 hadoop-hdfs-namenode[10252]: starting namenode...
feb 14 10:52:40 felipe-MS-7A63 hadoop-hdfs-namenode[10252]: SLF4J: Failed to ...
feb 14 10:52:40 felipe-MS-7A63 hadoop-hdfs-namenode[10252]: SLF4J: Defaulting...
feb 14 10:52:40 felipe-MS-7A63 hadoop-hdfs-namenode[10252]: SLF4J: See http:/...
feb 14 10:52:48 felipe-MS-7A63 hadoop-hdfs-namenode[10252]:  * Failed to star...
feb 14 10:52:48 felipe-MS-7A63 systemd[1]: hadoop-hdfs-namenode.service: Con...1
feb 14 10:52:48 felipe-MS-7A63 systemd[1]: Failed to start LSB: Hadoop namenode.
feb 14 10:52:48 felipe-MS-7A63 systemd[1]: hadoop-hdfs-namenode.service: Uni....
feb 14 10:52:48 felipe-MS-7A63 systemd[1]: hadoop-hdfs-namenode.service: Fai....
Hint: Some lines were ellipsized, use -l to show in full.
Setting up hadoop-hdfs-datanode (2.6.0+cdh5.14.0+2715-1.cdh5.14.0.p0.47~trusty-cdh5.14.0) ...
Job for hadoop-hdfs-datanode.service failed because the control process exited with error code. See "systemctl status hadoop-hdfs-datanode.service" and "journalctl -xe" for details.
invoke-rc.d: initscript hadoop-hdfs-datanode, action "start" failed.
● hadoop-hdfs-datanode.service - LSB: Hadoop datanode
   Loaded: loaded (/etc/init.d/hadoop-hdfs-datanode; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since mié 2018-02-14 10:52:57 -03; 2ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 10419 ExecStart=/etc/init.d/hadoop-hdfs-datanode start (code=exited, status=1/FAILURE)

feb 14 10:52:48 felipe-MS-7A63 su[10437]: pam_unix(su:session): session open...)
feb 14 10:52:48 felipe-MS-7A63 hadoop-hdfs-datanode[10419]: starting datanode...
feb 14 10:52:49 felipe-MS-7A63 hadoop-hdfs-datanode[10419]: SLF4J: Failed to ...
feb 14 10:52:49 felipe-MS-7A63 hadoop-hdfs-datanode[10419]: SLF4J: Defaulting...
feb 14 10:52:49 felipe-MS-7A63 hadoop-hdfs-datanode[10419]: SLF4J: See http:/...
feb 14 10:52:57 felipe-MS-7A63 hadoop-hdfs-datanode[10419]:  * Failed to star...
feb 14 10:52:57 felipe-MS-7A63 systemd[1]: hadoop-hdfs-datanode.service: Con...1
feb 14 10:52:57 felipe-MS-7A63 systemd[1]: Failed to start LSB: Hadoop datanode.
feb 14 10:52:57 felipe-MS-7A63 systemd[1]: hadoop-hdfs-datanode.service: Uni....
feb 14 10:52:57 felipe-MS-7A63 systemd[1]: hadoop-hdfs-datanode.service: Fai....
Hint: Some lines were ellipsized, use -l to show in full.
Setting up hadoop-hdfs-secondarynamenode (2.6.0+cdh5.14.0+2715-1.cdh5.14.0.p0.47~trusty-cdh5.14.0) ...
Job for hadoop-hdfs-secondarynamenode.service failed because the control process exited with error code. See "systemctl status hadoop-hdfs-secondarynamenode.service" and "journalctl -xe" for details.
invoke-rc.d: initscript hadoop-hdfs-secondarynamenode, action "start" failed.
● hadoop-hdfs-secondarynamenode.service - LSB: Hadoop secondarynamenode
   Loaded: loaded (/etc/init.d/hadoop-hdfs-secondarynamenode; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since mié 2018-02-14 10:53:06 -03; 2ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 10630 ExecStart=/etc/init.d/hadoop-hdfs-secondarynamenode start (code=exited, status=1/FAILURE)

feb 14 10:52:57 felipe-MS-7A63 su[10648]: pam_unix(su:session): session open...)
feb 14 10:52:57 felipe-MS-7A63 hadoop-hdfs-secondarynamenode[10630]: starting...
feb 14 10:52:58 felipe-MS-7A63 hadoop-hdfs-secondarynamenode[10630]: SLF4J: F...
feb 14 10:52:58 felipe-MS-7A63 hadoop-hdfs-secondarynamenode[10630]: SLF4J: D...
feb 14 10:52:58 felipe-MS-7A63 hadoop-hdfs-secondarynamenode[10630]: SLF4J: S...
feb 14 10:53:06 felipe-MS-7A63 hadoop-hdfs-secondarynamenode[10630]:  * Faile...
feb 14 10:53:06 felipe-MS-7A63 systemd[1]: hadoop-hdfs-secondarynamenode.ser...1
feb 14 10:53:06 felipe-MS-7A63 systemd[1]: Failed to start LSB: Hadoop secon....
feb 14 10:53:06 felipe-MS-7A63 systemd[1]: hadoop-hdfs-secondarynamenode.ser....
feb 14 10:53:06 felipe-MS-7A63 systemd[1]: hadoop-hdfs-secondarynamenode.ser....

 

 

Regarding the configuration of /etc/host If I understand correctly, I am not asked to do it manually here https://www.cloudera.com/documentation/enterprise/5-4-x/topics/cdh_qs_yarn_pseudo.html

 

Regarding the full stack trace logs could you point me in the right direction to find them? I found the changelogs, but I do not know if they are the same thing.

 

Announcements