You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flume.apache.org by sh...@accenture.com on 2012/12/18 14:12:36 UTC

Getting this annoying error

I am always getting this annoying error


Unable to map logical node 'test_agnt_nd1' to physical node 'ip-10-40-222-77.ec2.internal'


I have the following configuration in a script file. Please help!



connect ip-10-40-222-77.ec2.internal


exec config test_agnt_nd1 test_Flow  'tail("/var/log/flume/test1.log",startFromEnd="true")' 'value("LogType","Test1Log") agentBESink("ip-10-40-222-77.ec2.internal",35853)'

exec config test_data_collector_nd1 test_Flow  'collectorSource(35853)' 'EHCacheSink("Y","/var/log/flume") '

exec spawn ip-10-40-222-77.ec2.internal test_agnt_nd1
exec spawn ip-10-40-222-77.ec2.internal test_data_collector_nd1

quit



Thanks and Regards,
Shouvanik Haldar | Cloud SME Pool | Mobile:+91-9830017568


________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.

______________________________________________________________________________________

www.accenture.com

Re: Getting this annoying error

Posted by Jeong-shik Jang <js...@gruter.com>.
Hi,

regarding Unable to map logical node 'test_agnt_nd1' to physical node 
'ip-10-40-222-77.ec2.internal',
Why don't you try "exec unmapAll" first and then "exec spawn ..." or map 
again; I guess "test_agnt_nd1" was mapped to a node already; you can 
check it in Mapping info in master Web UI or "getmappings" command in 
flume shell


On 12/18/12 10:16 PM, Nitin Pawar wrote:
>
> Try putting machines external IP or internal ip from aws console
>
> Name u r giving is invalid hostname and not routable
>
> On Dec 18, 2012 6:42 PM, <shouvanik.haldar@accenture.com 
> <ma...@accenture.com>> wrote:
>
>     I am always getting this annoying error
>
>     Unable to map logical node 'test_agnt_nd1' to physical node
>     'ip-10-40-222-77.ec2.internal'
>
>     I have the following configuration in a script file. Please help!
>
>     *connect ip-10-40-222-77.ec2.internal*
>
>     **
>
>     **
>
>     *exec config test_agnt_nd1 test_Flow
>     'tail("/var/log/flume/test1.log",startFromEnd="true")'
>     'value("LogType","Test1Log")
>     agentBESink("ip-10-40-222-77.ec2.internal",35853)'*
>
>     **
>
>     *exec config test_data_collector_nd1 test_Flow
>     'collectorSource(35853)' 'EHCacheSink("Y","/var/log/flume") '*
>
>     **
>
>     *exec spawn ip-10-40-222-77.ec2.internal test_agnt_nd1*
>
>     *exec spawn ip-10-40-222-77.ec2.internal test_data_collector_nd1*
>
>     **
>
>     *quit*
>
>     *Thanks and Regards,*
>
>     *Shouvanik Haldar | Cloud SME Pool | Mobile:+91-9830017568
>     <tel:%2B91-9830017568> *
>
>
>     ------------------------------------------------------------------------
>     This message is for the designated recipient only and may contain
>     privileged, proprietary, or otherwise private information. If you
>     have received it in error, please notify the sender immediately
>     and delete the original. Any other use of the e-mail by you is
>     prohibited.
>
>     Where allowed by local law, electronic communications with
>     Accenture and its affiliates, including e-mail and instant
>     messaging (including content), may be scanned by our systems for
>     the purposes of information security and assessment of internal
>     compliance with Accenture policy.
>
>     ______________________________________________________________________________________
>
>     www.accenture.com <http://www.accenture.com>
>


-- 
Jeong-shik Jang / jsjang@gruter.com
Gruter, Inc., R&D Team Leader
www.gruter.com
Enjoy Connecting


RE: Getting this annoying error

Posted by sh...@accenture.com.
This configuration was working previously!

What is meant by machine external IP or internal ip?

Thanks and Regards,
Shouvanik Haldar | Cloud SME Pool | Mobile:+91-9830017568

From: Nitin Pawar [mailto:nitinpawar432@gmail.com]
Sent: Tuesday, December 18, 2012 6:46 PM
To: Haldar, Shouvanik
Cc: user@flume.apache.org
Subject: Re: Getting this annoying error


Try putting machines external IP or internal ip from aws console

Name u r giving is invalid hostname and not routable
On Dec 18, 2012 6:42 PM, <sh...@accenture.com>> wrote:
I am always getting this annoying error


Unable to map logical node 'test_agnt_nd1' to physical node 'ip-10-40-222-77.ec2.internal'


I have the following configuration in a script file. Please help!



connect ip-10-40-222-77.ec2.internal


exec config test_agnt_nd1 test_Flow  'tail("/var/log/flume/test1.log",startFromEnd="true")' 'value("LogType","Test1Log") agentBESink("ip-10-40-222-77.ec2.internal",35853)'

exec config test_data_collector_nd1 test_Flow  'collectorSource(35853)' 'EHCacheSink("Y","/var/log/flume") '

exec spawn ip-10-40-222-77.ec2.internal test_agnt_nd1
exec spawn ip-10-40-222-77.ec2.internal test_data_collector_nd1

quit



Thanks and Regards,
Shouvanik Haldar | Cloud SME Pool | Mobile:+91-9830017568<tel:%2B91-9830017568>


________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.

______________________________________________________________________________________

www.accenture.com<http://www.accenture.com>

Re: Getting this annoying error

Posted by Nitin Pawar <ni...@gmail.com>.
Try putting machines external IP or internal ip from aws console

Name u r giving is invalid hostname and not routable
On Dec 18, 2012 6:42 PM, <sh...@accenture.com> wrote:

>  I am always getting this annoying error****
>
> ** **
>
> ** **
>
> Unable to map logical node 'test_agnt_nd1' to physical node
> 'ip-10-40-222-77.ec2.internal'****
>
> ** **
>
> ** **
>
> I have the following configuration in a script file. Please help!****
>
> ** **
>
> ** **
>
> ** **
>
> *connect ip-10-40-222-77.ec2.internal*
>
> * *
>
> * *
>
> *exec config test_agnt_nd1 test_Flow
> 'tail("/var/log/flume/test1.log",startFromEnd="true")'
> 'value("LogType","Test1Log")
> agentBESink("ip-10-40-222-77.ec2.internal",35853)'*
>
> * *
>
> *exec config test_data_collector_nd1 test_Flow  'collectorSource(35853)'
> 'EHCacheSink("Y","/var/log/flume") '*
>
> * *
>
> *exec spawn ip-10-40-222-77.ec2.internal test_agnt_nd1*
>
> *exec spawn ip-10-40-222-77.ec2.internal test_data_collector_nd1*
>
> * *
>
> *quit*
>
> ** **
>
> ** **
>
> ** **
>
> *Thanks and Regards,*
>
> *Shouvanik Haldar | Cloud SME Pool | Mobile:+91-9830017568 *
>
> ** **
>
> ------------------------------
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited.
>
> Where allowed by local law, electronic communications with Accenture and
> its affiliates, including e-mail and instant messaging (including content),
> may be scanned by our systems for the purposes of information security and
> assessment of internal compliance with Accenture policy.
>
>
> ______________________________________________________________________________________
>
> www.accenture.com
>