Support Questions

Find answers, ask questions, and share your expertise

Storm word count Topology fails

avatar
Rising Star

I am trying to run a word count topology to test storm. But getting following error in supervisor.log

2017-06-27 08:29:55 b.s.config [INFO] SET worker-user 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a xbblwv5 
2017-06-27 08:29:55 b.s.d.supervisor [INFO] Running as user:storm command:("/usr/hdp/2.2.6.0-2800/storm/bin/worker-launcher" “storm” "worker" "/disk/hadoop/storm/workers/6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a" "/disk/hadoop/storm/workers/6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a/storm-worker-script.sh") 
2017-06-27 08:29:55 b.s.util [WARN] Worker Process 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a:Invalid permissions on worker-launcher binary. 
2017-06-27 08:29:55 b.s.util [WARN] Worker Process 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a:The configured nodemanager group 501 is different from the group of the executable 0 
2017-06-27 08:29:55 b.s.d.supervisor [INFO] 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a still hasn't started 
2017-06-27 08:29:55 b.s.d.supervisor [INFO] Worker Process 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a exited with code: 22 
2017-06-27 08:29:55 b.s.d.supervisor [INFO] 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a still hasn't started 
2017-06-27 08:29:56 b.s.d.supervisor [INFO] 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a still hasn't started 
2017-06-27 08:29:56 b.s.d.supervisor [INFO] 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a still hasn't started 
2017-06-27 08:29:57 b.s.d.supervisor [INFO] 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a still hasn't started 
2017-06-27 08:29:57 b.s.d.supervisor [INFO] 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a still hasn't started 
2017-06-27 08:29:58 b.s.d.supervisor [INFO] 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a still hasn't started 
2017-06-27 08:29:58 b.s.d.supervisor [INFO] 6f0c4ad9-a6c2-4c4c-9e48-4f9da485bd2a still hasn't started 
1 ACCEPTED SOLUTION

avatar
Rising Star

The error message points that the permissions on worker-launcher binary are not correct. Please check that the permissions on worker-launcher binary. It should be owned by root:hadoop or the group parameter configured in worker-launcher.cfg.

From the log message it appears that the group ownership is root.

Also note that the permissions on the binary should be 6550 else it would fail again after you change the group ownership. Here is the output of the ownership from my test system.

# stat /usr/hdp/2.5.0.0-1133/storm/bin/worker-launcher
  File: `/usr/hdp/2.5.0.0-1133/storm/bin/worker-launcher'
  Size: 56848     	Blocks: 112        IO Block: 4096   regular file
Device: fc01h/64513d	Inode: 1444319     Links: 1
Access: (6550/-r-sr-s---)  Uid: (    0/    root)   Gid: (  501/  hadoop)
Access: 2016-08-03 13:25:37.000000000 +0000
Modify: 2016-08-03 13:25:37.000000000 +0000
Change: 2016-11-19 13:23:02.764000118 +0000

View solution in original post

2 REPLIES 2

avatar
Rising Star

The error message points that the permissions on worker-launcher binary are not correct. Please check that the permissions on worker-launcher binary. It should be owned by root:hadoop or the group parameter configured in worker-launcher.cfg.

From the log message it appears that the group ownership is root.

Also note that the permissions on the binary should be 6550 else it would fail again after you change the group ownership. Here is the output of the ownership from my test system.

# stat /usr/hdp/2.5.0.0-1133/storm/bin/worker-launcher
  File: `/usr/hdp/2.5.0.0-1133/storm/bin/worker-launcher'
  Size: 56848     	Blocks: 112        IO Block: 4096   regular file
Device: fc01h/64513d	Inode: 1444319     Links: 1
Access: (6550/-r-sr-s---)  Uid: (    0/    root)   Gid: (  501/  hadoop)
Access: 2016-08-03 13:25:37.000000000 +0000
Modify: 2016-08-03 13:25:37.000000000 +0000
Change: 2016-11-19 13:23:02.764000118 +0000

avatar
Rising Star