Good advice. Still, at least for localhost a solution would be good (which might point to a larger problem). I submitted a topology to Storm that's installed on my local system and accessed it with both localhost:8080 and http://192.168.x.x:8080
But when I try to view the worker log by clicking on the port hyperlink, I'm taken to: http://localhost:8000/log?file=MyTopo-1-1469209494%2F6704%2Fworker.log which shows "Unable to connect Firefox can't establish a connection to the server at localhost:8000." Even tried substituting "localhost" with http://192.168.x.x:8000/log?file=MyTopo-1-1469209494%2F6704%2Fworker.log Still no luck. On Wed, Jul 27, 2016 at 12:02 PM, Erik Weathers <[email protected]> wrote: > It's an interesting question. Storm has no idea what your AWS instances' > "public" and "private" IPs are, so your proposal of having storm have links > for both IPs doesn't seem like a fit. > > Are you *sure* you even *want* to be able to do what you are proposing? > i.e., it sounds to me like your storm nimbus UI is exposed to the outside > world for anyone to hit, which sounds like a bad idea. And you probably > *really* don't want the worker log files (the "6700 port hyperlink is a > link to the logviewer which runs on the individual worker nodes and is on > port 8000 by default) to be exposed to the outside world. And with the > newer versions of storm there are even more artifacts, such as the topology > jars that are exposed via the logviewer. > > I think the recommended way to deal with Storm in AWS is to run in an > Amazon VPC and use a VPN so that you are only referencing private IPs and > not exposing any of this stuff to the outside world. > > - Erik > > On Tue, Jul 26, 2016 at 9:54 PM, Navin Ipe < > [email protected]> wrote: > >> Hi, >> >> When I run storm locally, I use localhost:8080/index.html to access the >> Storm UI. But when I click on one of the 6700 port hyperlinks on the UI, it >> tries to take me to the log on 192.168.x.x. >> Same way, when I run Storm on AWS, I submit the jar via the commandline >> and when I use the public IP to view the Storm UI, Storm provides me the >> 6700 port hyperlink as the private IP for viewing the worker.log file. >> >> In both cases, I'm unable to view the log file from the UI because of an >> IP mismatch. >> Is this something that can be fixed? Perhaps provide two hyperlinks; one >> with the private IP and one with the public IP? >> >> -- >> Regards, >> Navin >> > > -- Regards, Navin
