[
https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238270#comment-17238270
]
Dhirendra Khanka commented on AMBARI-25591:
-------------------------------------------
[~echohlne] The above issue is on the production cluster.
Based on my testing on a dummy server, the properties related to
_server.jdbc.rca_ appear in properties only when "ambari-server setup" is run
with option Existing Postgresql Server. When the ambari-server setup is run
with option Embedded Postgresql then only _server.jdbc.user_ properties appear.
So it looks like our production cluster is using Embedded Postgresql option, as
I can see only server.jdbc.user.* properties. You can confirm this from
hdp-sandbox as well, where you wont find server.jdbc.rca.user unless you run
setup again and select Existing Postgresql option.
We also have a dev server where both rca.user and user.name point to 'ambari'
and its password file and it is using the Existing Postgresql setup. There I
can find mapred user, but I think the mapred user used to be part of older
Ambari Versions which used ambarirca schema. The newer ambari versions does not
create any mapred user in ambari database anymore.
Question is how does the new Ambari server continue to refer the mapred user
which is no longer created by ambari newer versions.
> org.postgresql.util.PSQLException: FATAL: password authentication failed for
> user "mapred"
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-25591
> URL: https://issues.apache.org/jira/browse/AMBARI-25591
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.1
> Reporter: Dhirendra Khanka
> Priority: Minor
> Labels: ambari-server
> Attachments: ambari-server.log
>
>
> Ambari server is continuously logging password authentication failed for user
> mapred error and ward messages. However there is no user mapred in ambari.
> The ambari database used is embedded postgresql. Will running the
> ambari-server setup again fix the issue?
>
> {code:java}
> 2020-11-24 06:37:46,933 ERROR [ambari-client-thread-1425637] Driver:263 -
> Connection error:
> org.postgresql.util.PSQLException: FATAL: password authentication failed for
> user "mapred"{code}
>
> Ambari database check gives below Warning in log
> {code:java}
> 2020-11-18 13:51:01,416 WARN - You have config(s):
> falcon-startup.properties-TOPOLOGY_RESOLVED,spark-defaults-version1524543611951,spark-metrics-properties-version1485951378211,falcon-atlas-application.properties-version1524574152922,spark-env-version1485951378211,falcon-startup.properties-INITIAL,spark-defaults-version1501747039754,falcon-log4j-INITIAL,hcat-env-version1570571662097,mahout-env-TOPOLOGY_RESOLVED,flume-env-INITIAL,hive-exec-log4j-version1570571662921,slider-log4j-TOPOLOGY_RESOLVED,slider-client-INITIAL,falcon-client.properties-INITIAL,falcon-startup.properties-version1524543610919,falcon-atlas-application.properties-version1524543611402,falcon-runtime.properties-TOPOLOGY_RESOLVED,mahout-log4j-TOPOLOGY_RESOLVED,spark-defaults-version1524574152551,falcon-env-INITIAL,ranger-site-version1570571657763,falcon-runtime.properties-INITIAL,spark-defaults-version1485951378211,livy-conf-version1485951378211,webhcat-site-version1570571662592,falcon-atlas-application.properties-version1492596818127,mahout-log4j-INITIAL,falcon-startup.properties-version1496929735878,falcon-log4j-TOPOLOGY_RESOLVED,spark-env-version1493710636755,spark-thrift-sparkconf-version1492596818303,livy-log4j-properties-version1485951378211,livy-conf-version1524543611603,falcon-env-version1524574151887,falcon-atlas-application.properties-INITIAL,flume-conf-TOPOLOGY_RESOLVED,spark-thrift-sparkconf-version1524574152356,mahout-env-INITIAL,spark-defaults-version1492596818576,flume-conf-INITIAL,livy-env-version1493710636755,falcon-startup.properties-version1524574151504,webhcat-env-version1570571663253,flume-env-TOPOLOGY_RESOLVED,falcon-env-TOPOLOGY_RESOLVED,slider-client-TOPOLOGY_RESOLVED,livy-env-version1485951378211,usersync-properties-version1570571659178,hive-log4j-version1570571663758,webhcat-log4j-version1570571661148,spark-thrift-fairscheduler-version1485951378211,falcon-atlas-application.properties-TOPOLOGY_RESOLVED,spark-thrift-sparkconf-version1524543611628,slider-log4j-INITIAL,spark-hive-site-override-version1485951378211,spark-log4j-properties-version1485951378211,slider-env-TOPOLOGY_RESOLVED,livy-spark-blacklist-version1485951378211,spark-javaopts-properties-version1485951378211,livy-conf-version1524574153115,livy-conf-version1492596818283,falcon-startup.properties-version1492596817779,slider-env-INITIAL,falcon-client.properties-TOPOLOGY_RESOLVED,spark-thrift-sparkconf-version1485951378211
> that is(are) not mapped (in serviceconfigmapping table) to any service!{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
