[
https://issues.apache.org/jira/browse/AMBARI-24261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24261:
----------------------------------
Description:
Upgraded above cluster from Ambari 2.6.2 to Ambari 2.7.0 and logsearch also
from 2.6.2 to 2.7.0.0
In ambari 2.6.2 we had created file "kafka-output.json" under "/usr/lib
/ambari-logsearch-logfeeder/conf" so that logsearch data is pushed to kafka
topic.
Looks like Ambari upgrade renames the conf dir to "conf-old" as below and due
to which kafka-output.json file in missing from the new config dir. This is
causing logfeeder start failure.
[logfeeder.out](/secure/attachment/160204/160204_logfeeder.out
"logfeeder.out attached to BUG-106926")
[root@ctr-e138-1518143905142-369208-01-000002 ambari-logsearch-logfeeder]#
ll
total 24
drwxr-xr-x 2 root root 4096 Jul 5 16:59 bin
drwxr-xr-x 3 root root 4096 Jul 6 08:11 conf
drwxr-xr-x 3 root root 4096 Jul 5 16:59 conf-old
drwxr-xr-x 2 root root 12288 Jul 5 16:59 libs
was:
====================================
cluster details:
host: 172.27.83.128
ssh username: cloudbreak
ssh key
<https://github.com/hortonworks/HCube/blob/master/utils/ssh_key_pair/hcube/hcube.pem>
====================================
Upgraded above cluster from Ambari 2.6.2 to Ambari 2.7.0 and logsearch also
from 2.6.2 to 2.7.0.0
In ambari 2.6.2 we had created file "kafka-output.json" under "/usr/lib
/ambari-logsearch-logfeeder/conf" so that logsearch data is pushed to kafka
topic.
Looks like Ambari upgrade renames the conf dir to "conf-old" as below and due
to which kafka-output.json file in missing from the new config dir. This is
causing logfeeder start failure.
[logfeeder.out](/secure/attachment/160204/160204_logfeeder.out
"logfeeder.out attached to BUG-106926")
[root@ctr-e138-1518143905142-369208-01-000002 ambari-logsearch-logfeeder]#
ll
total 24
drwxr-xr-x 2 root root 4096 Jul 5 16:59 bin
drwxr-xr-x 3 root root 4096 Jul 6 08:11 conf
drwxr-xr-x 3 root root 4096 Jul 5 16:59 conf-old
drwxr-xr-x 2 root root 12288 Jul 5 16:59 libs
> logfeeder fail to start due to missing conf file post logsearch upgrade
> -----------------------------------------------------------------------
>
> Key: AMBARI-24261
> URL: https://issues.apache.org/jira/browse/AMBARI-24261
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-24261.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Upgraded above cluster from Ambari 2.6.2 to Ambari 2.7.0 and logsearch also
> from 2.6.2 to 2.7.0.0
> In ambari 2.6.2 we had created file "kafka-output.json" under "/usr/lib
> /ambari-logsearch-logfeeder/conf" so that logsearch data is pushed to kafka
> topic.
> Looks like Ambari upgrade renames the conf dir to "conf-old" as below and due
> to which kafka-output.json file in missing from the new config dir. This is
> causing logfeeder start failure.
> [logfeeder.out](/secure/attachment/160204/160204_logfeeder.out
> "logfeeder.out attached to BUG-106926")
>
>
> [root@ctr-e138-1518143905142-369208-01-000002
> ambari-logsearch-logfeeder]# ll
> total 24
> drwxr-xr-x 2 root root 4096 Jul 5 16:59 bin
> drwxr-xr-x 3 root root 4096 Jul 6 08:11 conf
> drwxr-xr-x 3 root root 4096 Jul 5 16:59 conf-old
> drwxr-xr-x 2 root root 12288 Jul 5 16:59 libs
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
