Hi Eric,
Yeah it does help. I am actually about to submit a patch for some updates
to the current quick start documentation which will include this within the
commentary.
Thanks for quick feedback.
Lewis

On Tue, Sep 22, 2015 at 10:44 PM, Eric Yang <ey...@apache.org> wrote:

> Hi Lewis,
>
> The messages are showing up because log4j socket appender writes to stderr
> for those warn messages when it is unable to stream logs to log4j socket
> server.  If Chukwa agent is started with socket adaptors prior to Hadoop
> and HBase, those messages will not show up.
>
> Hope this helps
> regards,
> Eric
>
> On Tue, Sep 22, 2015 at 7:54 PM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
>> Hi Folks,
>> When I substitute the various Hadoop and HBase config files e.g.
>> log4j.properties, hadoop-metrics2.properties, etc. I am left with some
>> pretty unappealinh Log4j output as follows
>>
>> lmcgibbn@LMC-032857 /usr/local/hadoop-2.4.0/sbin(master) $ ./start-all.sh
>> This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh
>> log4j:ERROR Could not connect to remote log4j server at [localhost]. We
>> will try again later.
>> log4j:ERROR Could not connect to remote log4j server at [localhost]. We
>> will try again later.
>> log4j:ERROR Could not connect to remote log4j server at [localhost]. We
>> will try again later.
>> log4j:WARN Failed to set property [port] to value "".
>> log4j:ERROR Could not connect to remote log4j server at [localhost]. We
>> will try again later.
>> log4j:WARN Failed to set property [port] to value "".
>> log4j:ERROR Could not connect to remote log4j server at [localhost]. We
>> will try again later.
>> 15/09/22 19:51:28 WARN util.NativeCodeLoader: Unable to load
>> native-hadoop library for your platform... using builtin-java classes where
>> applicable
>> ...
>> loads more of same logging.
>>
>> Does anyone know which specific setting setting is causing this? If so I
>> think a good patch would be to clean this up.
>>
>> I see several entires within log4j.properties as follows
>>
>> log4j.appender.RFA.RemoteHost=localhost
>>
>> However I am not sure if these are causing the problems.
>> Thanks for any guidance.
>> lewis
>>
>> --
>> *Lewis*
>>
>
>


-- 
*Lewis*

Reply via email to