Skip to main content
Pedro_E
Pedro_E
Gold ⭐️
December 9, 2025
Solved

Can not start yarn Node Manager

Hello there, I'm having a problem while trying to start a newly added node's yarn NodeMgr.

When I start it via Cloudera Manager console, I've got this in logs:

2025-12-09 10:15:52,431 ERROR org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl: Unexpected error starting NodeStatusUpdater
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Received SHUTDOWN signal from Resourcemanager, Registration of NodeManager failed, Message from ResourceManager: Disallowed NodeManager from cloudera06apl.claro.amx, Sending SHUTDOWN signal to the NodeManager.
at org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.registerWithRM(NodeStatusUpdaterImpl.java:426)
at org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.serviceStart(NodeStatusUpdaterImpl.java:272)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
at org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:121)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:975)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:1054)
2025-12-09 10:15:52,432 INFO org.apache.hadoop.service.AbstractService: Service org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl failed in state STARTED
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Received SHUTDOWN signal from Resourcemanager, Registration of NodeManager failed, Message from ResourceManager: Disallowed NodeManager from cloudera06apl.claro.amx, Sending SHUTDOWN signal to the NodeManager.

 

What am I missing?


Regards.

Pedro_E
Pedro_EAnswer
Gold ⭐️
December 16, 2025

Hello Vidya, the question was answered. However, it was not what other used replied.

It was that allow-nodes.txt was included the newly added host, but the process that was running the yarn node manager wasn't aware of that modification. What I had to do was Stop the yarn process, remove older files of yarn nm (/var/run/cloudera-scm-agent/process/*yarn-NODEMANAGER*) and then start it again.

View in thread

4 replies

vafs
Gold ⭐️⭐️⭐️
vafs
Gold ⭐️⭐️⭐️
December 9, 2025

Hello @Pedro_E, 

Thanks for being part of our Cloudera Community. 

I was checking the log and error and there is no much information more than that: 

org.apache.hadoop.yarn.exceptions.YarnRuntimeException: org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Received SHUTDOWN signal from Resourcemanager, Registration of NodeManager failed, Message from ResourceManager: Disallowed NodeManager from host.company.com, Sending SHUTDOWN signal to the NodeManager.

Note: you uploaded full log with hostnames and more, maybe you want to edit that to exclude private information. 

That error is telling us the RM is rejecting the NM to be registered. 
This could be for an issue with a busy port or name resolution. 

Make sure that RM can resolve the FQDN properly, and same on the NM with the RM name. 
If not, solve that issue by fixing DNS or adding the info to hosts file. 

Also, if possible, restart the OS on that NM, that will clear any hanging process that may be using the ports needed for this registration. 

If you still face the issue, it would be worth seeing the RM log when you face the issue with the registration. 

Translate
Regards, Andrés Fallas -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs-up button.
VidyaSargur
Community Manager
VidyaSargur
Community Manager
December 16, 2025

@Pedro_E, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution to help others find the answer more easily in the future.

Translate
Regards, Vidya Sargur, Community Manager Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.
Pedro_E
Pedro_EAuthorAnswer
Gold ⭐️
December 16, 2025

Hello Vidya, the question was answered. However, it was not what other used replied.

It was that allow-nodes.txt was included the newly added host, but the process that was running the yarn node manager wasn't aware of that modification. What I had to do was Stop the yarn process, remove older files of yarn nm (/var/run/cloudera-scm-agent/process/*yarn-NODEMANAGER*) and then start it again.

Translate
    VidyaSargur
    Community Manager
    VidyaSargur
    Community Manager
    December 17, 2025

    Thanks for responding with a resolution that worked for you, @Pedro_E. I'll mark your response as a solution. 

    Translate
    Regards, Vidya Sargur, Community Manager Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.
    Terms & ConditionsAccessibility statement