Please ignore my earlier mail .. Perhaps I just pasted the message without reading it fully ..Changing the *instance-1.c.apache-storm.internal* to my hostname did the trick :P ..I can now see those log messages ..
On Sat, Oct 24, 2015 at 7:34 PM, Ankur Garg <ankurga...@gmail.com> wrote: > Thanks Satish for replying . > > My logviewer is running but still when i click on the port on the storm ui > it returns "The server at *instance-1.c.apache-storm.internal* can't be > found, because the DNS lookup failed" . > > Also , can u or anyone here tell me why the exceptions which can be seen > in storm ui page cant be seen inside worker log files :( . Does Storm UI > reads these exceptions from a different source than worker.*.log file . > > Thanks > Ankur > > On Sat, Oct 24, 2015 at 7:12 PM, Satish Mittal <satish.mit...@inmobi.com> > wrote: > >> You probably need to set up logviewer daemon. >> >> On Sat, Oct 24, 2015 at 5:28 PM, Ankur Garg <ankurga...@gmail.com> wrote: >> >>> Hi , >>> >>> I have set up a single node Storm Cluster to run my topologies . >>> Unfortunately , due to reason unknown I am not seeing logs inside >>> worker-*.log when I start a spring application inside the Storm Spout and >>> bolts . >>> >>> However , in the Storm UI I do see any exceptions occuring inside my >>> spouts and bolts and log messages present for the same in the UI (image >>> attached below) . Moreover, If i click on the error port below (6703) , I >>> get page not found error . >>> >>> Can someone tell me where does StormUI print or gets its log from . I >>> believe >>> >>> this should be the page where rest of my missing logs can be present . >>> >>> [image: Inline image 1] >>> >>> >>> Please help . >>> >>> Thanks >>> Ankur >>> >> >> >> _____________________________________________________________ >> The information contained in this communication is intended solely for >> the use of the individual or entity to whom it is addressed and others >> authorized to receive it. It may contain confidential or legally privileged >> information. If you are not the intended recipient you are hereby notified >> that any disclosure, copying, distribution or taking any action in reliance >> on the contents of this information is strictly prohibited and may be >> unlawful. If you have received this communication in error, please notify >> us immediately by responding to this email and then delete it from your >> system. The firm is neither liable for the proper and complete transmission >> of the information contained in this communication nor for any delay in its >> receipt. > > >
