[ 
https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238251#comment-17238251
 ] 

akiyamaneko edited comment on AMBARI-25591 at 11/24/20, 4:49 PM:
-----------------------------------------------------------------

[~dhire...@gmail.com]
It is likely that some misconfigurations during installation caused the problem 
you mentioned。
It is recommended that you login into the server where the ambari-server is 
deployed, and use the command like below to check the username and password:
{code:bash}
[root@hadoop_personal~]# cat /etc/ambari-server/conf/ambari.properties | grep 
-n user
27:ambari-server.user=7zj3zuia
60:local.database.user=postgres
92:server.jdbc.rca.user.name=root
93:server.jdbc.rca.user.passwd=/etc/ambari-server/conf/password.dat
95:server.jdbc.user.name=root
96:server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat

{code}


was (Author: echohlne):
[~dhire...@gmail.com]

It is recommended that you login into the server where the ambari-server is 
deployed, and use the command like below to check the username and password:
{code:bash}
[root@hadoop_personal~]# cat /etc/ambari-server/conf/ambari.properties | grep 
-n user
27:ambari-server.user=7zj3zuia
60:local.database.user=postgres
92:server.jdbc.rca.user.name=root
93:server.jdbc.rca.user.passwd=/etc/ambari-server/conf/password.dat
95:server.jdbc.user.name=root
96:server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat

{code}

> 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
>
> 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}
>  
> [^ambari-server.log]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to