I’ve submitted a topology and it submits fine but the spout never emits a tuple 
and the worker.log is never created. If I browse to where the worker.log should 
be created, the only thing that exists is the worker.yaml file. Below is the 
only real information I’m seeing in the supervisor.log. Has anyone experience 
an issue like this? Neither the spout nor the bolt is throwing an exception.

2017-08-02 15:30:18.956 o.a.s.d.supervisor [INFO] Creating symlinks for 
worker-id: 9514f5b9-5b1b-4d24-af46-079ba79ef984 storm-id: test_0-23-1501705445 
to its port artifacts directory
2017-08-02 15:30:18.958 o.a.s.d.supervisor [INFO] Creating symlinks for 
worker-id: 9514f5b9-5b1b-4d24-af46-079ba79ef984 storm-id: test_0-23-1501705445 
for files(1): ("resources")
2017-08-02 15:30:18.959 o.a.s.d.supervisor [INFO] Running as user:<redacted> 
command:("/<PATH>/storm/bin/worker-launcher" "<redacted>" "worker" 
"/<PATH>/storm/workers/9514f5b9-5b1b-4d24-af46-079ba79ef984" 
"/<PATH>/storm/workers/9514f5b9-5b1b-4d24-af46-079ba79ef984/storm-worker-script.sh")
2017-08-02 15:30:18.962 o.a.s.d.supervisor [INFO] 
9514f5b9-5b1b-4d24-af46-079ba79ef984 still hasn't started
2017-08-02 15:30:18.963 o.a.s.util [WARN] Worker Process 
9514f5b9-5b1b-4d24-af46-079ba79ef984:main : command provided worker
2017-08-02 15:30:18.963 o.a.s.util [WARN] Worker Process 
9514f5b9-5b1b-4d24-af46-079ba79ef984:main : user is <redacted>
2017-08-02 15:30:18.963 o.a.s.util [WARN] Worker Process 
9514f5b9-5b1b-4d24-af46-079ba79ef984:Failure to exec app initialization process 
- No such file or directory
2017-08-02 15:30:19.003 o.a.s.d.supervisor [INFO] Worker Process 
9514f5b9-5b1b-4d24-af46-079ba79ef984 exited with code: 255
2017-08-02 15:30:19.463 o.a.s.d.supervisor [INFO] 
9514f5b9-5b1b-4d24-af46-079ba79ef984 still hasn't started

Rick Magnuson | Lead Data Engineer

Reply via email to