[
https://issues.apache.org/jira/browse/AMBARI-18002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409765#comment-15409765
]
Olivér Szabó commented on AMBARI-18002:
---------------------------------------
hi [~masatana],
good point, I have already noticed this issue, actually that is our major
problem now (for 2.5.0 release) the problem is that can happen with any of the
HDP components too, but most of the cases these are all configurable, you I
recommend to use LANG=en_US.UTF-8, or if you cant you can still change the
log4j.configurations. (also it would be nice if we used ISO format for every
service log...but as I said it can be configurable, but at least it would work
by default)
The long term solution here will be to use a custom appender which can be
parsed more easily without grok patterns:
https://github.com/apache/ambari/tree/trunk/ambari-logsearch/ambari-logsearch-appender
(of course that is working for only java applications)
Also for 2.5.0 I plan to add custom filters which can be added through ambari
> Parse Error in ambari-server.log with LogSearch
> -----------------------------------------------
>
> Key: AMBARI-18002
> URL: https://issues.apache.org/jira/browse/AMBARI-18002
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Environment: CentOS7.2, Ambari2.4.0 (trunk), LANG=ja_JP.UTF-8
> Reporter: Masahiro Tanaka
> Assignee: Masahiro Tanaka
> Attachments: AMBARI-18002.patch
>
>
> In Ambari Server with LogSearch environment, we got a lot of errors like below
> {code}
> 2016-08-03 13:51:36,146 WARN file=ambari-server.log
> org.apache.ambari.logfeeder.filter.FilterGrok LogFeederUtil.java:350 - Error
> parsing string. length=182, input=input:source=file,
> path=/var/log/ambari-server/ambari-server.log. First upto 100 characters=03 8
> 2016 13:51:29,606 INFO [ambari-heartbeat-processor-0] HeartbeatProcessor:505
> - Updating applie. Messages suppressed before: 3
> {code}
> ambari-server.log is below
> {code}
> 28 7 2016 12:52:57,207 INFO [main] Configuration:1009 - Generation of file
> with password
> 28 7 2016 12:52:58,893 INFO [main] Configuration:1022 - Reading password
> from existing file
> 28 7 2016 12:53:00,389 INFO [main] Configuration:1022 - Reading password
> from existing file
> 28 7 2016 12:53:01,885 INFO [main] Configuration:1022 - Reading password
> from existing file
> 28 7 2016 12:53:03,423 INFO [main] Configuration:1022 - Reading password
> from existing file
> 28 7 2016 12:53:04,947 INFO [main] Configuration:1022 - Reading password
> from existing file
> 28 7 2016 12:53:06,503 INFO [main] Configuration:1022 - Reading password
> from existing file
> 28 7 2016 12:53:08,038 INFO [main] Configuration:1022 - Reading password
> from existing file
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
