Java errors in Storm UI after installation
See original GitHub issueReceiving these errors once installation was complete via ansible: Looks like I didnt install something or forgot to do a step in installation.
java.lang.RuntimeException: org.apache.storm.multilang.NoOutputException: Pipe to subprocess seems to be broken! No output read. Serializer Exception: /opt/spamscope/venv/local/lib/python2.7/site-pack
--
Any help would be appreciated!
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Error when hitting the storm-ui URL - Google Groups
I start the storm-ui by running the command bin/storm ui. When i hit the URL 'localhost:8080' i get this error: org.apache.thrift7.transport.
Read more >Storm Ui error kafka spout, not using HDP - java - Stack Overflow
When I go to my StormUI I get the following message Offset lags for kafka not supported for older versions. Please update kafka...
Read more >Troubleshooting - Apache Storm
This page lists issues people have run into when using Storm along with their solutions. Worker processes are crashing on startup with no...
Read more >Storm UI Error on fresh setup of cluster #37 - GitHub
Everything seems to be setup fine and all the 4 nodes (zookeeper,nimbus,supervisor1,supervisor2) are running. But when I launch the storm UI ...
Read more >Storm UI Internal Server Error for remote cluster
I face the error below in my Storm UI: org.apache.thrift7.transport.TTransportException: java.net.ConnectException: Connection refused
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah I see that now. Added and works now. Great thank you!
I understood. Don’t use hack. In ansible install I used a configuration file test that doesn’t have a new configuration parameters. So add this and it will work.