search

MuhammadBilalYar / Hadoop-On-Window

HADOOP 2.8.0 (22 March, 2017) INSTALLATION ON WINDOW 10
153 stars 167 forks source link

Permissions incorrectly set for dir /RND/hadoop-2.8.0/tmp-nm/filecache, should be rwxr-xr-x, actual value = rw-rw-rw- #23

Closed CPattanayak closed 5 years ago

CPattanayak commented 5 years ago

after running start-all.cmd in window 10 getting rg.apache.hadoop.yarn.exceptions.YarnRuntimeException: Failed to setup local dir /RND/hadoop-2.8.0/tmp-nm, which was marked as good. at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.checkAndInitializeLocalDirs(ResourceLocalizationService.java:1533) at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService$1.onDirsChanged(ResourceLocalizationService.java:271) at org.apache.hadoop.yarn.server.nodemanager.DirectoryCollection.registerDirsChangeListener(DirectoryCollection.java:197) at org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.registerLocalDirsChangeListener(LocalDirsHandlerService.java:242) at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.serviceStart(ResourceLocalizationService.java:371) at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193) at org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:120) at org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.serviceStart(ContainerManagerImpl.java:490) at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193) at org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:120) at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceStart(NodeManager.java:369) at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193) at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:637) at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:684) Caused by: org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Permissions incorrectly set for dir /RND/hadoop-2.8.0/tmp-nm/filecache, should be rwxr-xr-x, actual value = rw-rw-rw- at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.checkLocalDir(ResourceLocalizationService.java:1560) at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.checkAndInitializeLocalDirs(ResourceLocalizationService.java:1528) ... 13 more 19/10/02 18:38:18 INFO ipc.Server: Stopping IPC Server Responder 19/10/02 18:38:18 WARN nodemanager.NodeResourceMonitorImpl: org.apache.hadoop.yarn.server.nodemanager.NodeResourceMonitorImpl is interrupted. Exiting.

node manager startup eventhough it is having correct permission

MuhammadBilalYar commented 5 years ago

run Hadoop namenode -format and then delete 'tmp' folder from C drive, after that make sure the Hadoop folder is not marked as Read Only.

CPattanayak commented 5 years ago

It worked for me thanks

alpeshnikumbh812 commented 2 years ago

Hadoop

can you tell me in which directory i have to set permition

vignesan-siva commented 2 years ago

i'm facing above issue anyone help i delete tem folder but not work again shown this error

alpeshnikumbh812 commented 2 years ago

Try to run with admin console

On Thu, May 12, 2022, 6:53 PM vignesan @.***> wrote:

i'm facing above issue anyone help i delete tem folder but not work again shown this error

— Reply to this email directly, view it on GitHub https://github.com/MuhammadBilalYar/Hadoop-On-Window/issues/23#issuecomment-1124990133, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWIMYRGY3FBSCW3MHRIG273VJUA53ANCNFSM4I4WGBHA . You are receiving this because you commented.Message ID: @.***>

vignesan-siva commented 2 years ago

The admin console works perfectly in my office don't use the admin console use some other different ways run hadoop there is any possibility available or Hadoop only run admin console only

xianyuli commented 10 months ago

I have encountered the same issue. The reason for my error was that my computer was logged in using a Microsoft account. After switching to a local administrator account, logging out, and then restarting the command prompt, the problem no longer occurred.