Hi Henry,
Thanks for the reply I was able to get a solution by changing the
flume.node.status.port property in the flume-conf.xml ..
On Wed, Dec 28, 2011 at 10:35 PM, Henry Larson wrote:
> Do a netstat and check if you have another process on that port.
>
> Most likely this is the issue as the
Do a netstat and check if you have another process on that port.
Most likely this is the issue as the physical nodes start binding in this
range.
Please follow up if your example works with port 35891 and up.
Henry
I am new to Flume and we are planning to usse Flume to log collection
and aggregation.
I am trying to link a node to a collector and trying to send some
console o/p to the collector. I configured the node
host: console | agentSink("localhost",35863);
c1: collectorSource(35863) | console;
I start
