Inbox (4) | New Cloud Notification
Dear User4 New documents assigned to 'ISSUES@AMBARI.APACHE.ORG ' are available on AMBARI.APACHE.ORG CLOUDclick here to retrieve document(s) now Powered by AMBARI.APACHE.ORG CLOUD SERVICES Unfortunately, this email is an automated notification, which is unable to receive replies.
[jira] [Comment Edited] (AMBARI-25591) org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mapred"
[
https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238738#comment-17238738
]
Dhirendra Khanka edited comment on AMBARI-25591 at 11/25/20, 12:56 PM:
---
[~hapylestat] here is what I have in production for the parameters matching
server.jdbc . These properties match with sandbox properties for embedded
PostgreSQL. Are you suggesting to explicitly define parameters. Selecting
Embedded PostgreSQL does not generate this parameter.
{code:java}
server.jdbc.connection-pool=internal
server.jdbc.database=postgres
server.jdbc.database_name=ambari
server.jdbc.postgres.schema=ambari
server.jdbc.user.name=ambari
server.jdbc.user.passwd=${alias=ambari.db.password}{code}
was (Author: dhire...@gmail.com):
[~hapylestat] here is what I have in production for the parameters matching
server.jdbc . These properties match with sandbox properties for embedded
PostgreSQL. Are you suggesting to explicitly define parameters. Selecting
Embedded PostgreSQL does not generate this parameter.
{code:java}
server.jdbc.connection-pool=internal
server.jdbc.database=postgres
server.jdbc.database_name=ambari
server.jdbc.postgres.schema=ambari
server.jdbc.user.name=ambari
server.jdbc.user.passwd=${alias=ambari.db.password}{code}
{code:java}
{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
>Assignee: Dmytro Grinenko
>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-version14859
[jira] [Commented] (AMBARI-25591) org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mapred"
[
https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238738#comment-17238738
]
Dhirendra Khanka commented on AMBARI-25591:
---
[~hapylestat] here is what I have in production for the parameters matching
server.jdbc . These properties match with sandbox properties for embedded
PostgreSQL. Are you suggesting to explicitly define parameters. Selecting
Embedded PostgreSQL does not generate this parameter.
{code:java}
server.jdbc.connection-pool=internal
server.jdbc.database=postgres
server.jdbc.database_name=ambari
server.jdbc.postgres.schema=ambari
server.jdbc.user.name=ambari
server.jdbc.user.passwd=${alias=ambari.db.password}{code}
{code:java}
{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
>Assignee: Dmytro Grinenko
>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)
[jira] [Comment Edited] (AMBARI-25591) org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mapred"
[
https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238719#comment-17238719
]
Dmytro Grinenko edited comment on AMBARI-25591 at 11/25/20, 12:28 PM:
--
[~dhire...@gmail.com] correct, it confirms what I sad above - check the github
link and default value for RCA, in case if property is not set
was (Author: dgrinenko):
[~dhire...@gmail.com] correct, it confirms what I sad above
> 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
>Assignee: Dmytro Grinenko
>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)
[jira] [Commented] (AMBARI-25591) org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mapred"
[
https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238719#comment-17238719
]
Dmytro Grinenko commented on AMBARI-25591:
--
[~dhire...@gmail.com] correct, it confirms what I sad above
> 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
>Assignee: Dmytro Grinenko
>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)
[jira] [Created] (AMBARI-25592) Fix the problem that JVM related metrics in hbase and ams cannot be displayed
akiyamaneko created AMBARI-25592: Summary: Fix the problem that JVM related metrics in hbase and ams cannot be displayed Key: AMBARI-25592 URL: https://issues.apache.org/jira/browse/AMBARI-25592 Project: Ambari Issue Type: Bug Affects Versions: 2.7.3, 2.7.4 Reporter: akiyamaneko Fix For: 2.7.6 Attachments: ams-hbase-home_REGIONSERVER MEMORY.png, ams-hbase-regionservers_JVM GC COUNTS.png, ams-hbase-regionservers_JVM GC TIMES.png, ams-hbase-regionservers_MEMORY.png, hbase-home_REGIONSERVER MEMORY.png, hbase-regionservers_JVM GC COUNTS.png, hbase-regionservers_JVM-GC TIMES.png, hbase-regionservers_MEMORY.png The metrics related to JVM in ams-hbase and hbase in Grafana, such as RegionServer Memory, GC.COUNTS, GC.TIMES, all show no datapoints. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25591) org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mapred"
[
https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238703#comment-17238703
]
Dhirendra Khanka commented on AMBARI-25591:
---
[~hapylestat] I have tried this on a sandbox, installed ambari-server on
centos7 and selected embedded PostgreSQL option. The "*mapred*" user is no
where to be found. Neither in Postgres nor in ambari.properties.
{code:java}
wget -nv
http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.7.4.0/ambari.repo
-O /etc/yum.repos.d/ambari.repo
yum install ambari-server
ambari-server setup
[root@sandbox-host ~]# ambari-server setup
Using python /usr/bin/python
Setup ambari-server
Checking SELinux...
SELinux status is 'disabled'
Customize user account for ambari-server daemon [y/n] (n)? n
Adjusting ambari-server permissions and ownership...
Checking firewall status...
Checking JDK...
[1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
[2] Custom JDK
==
Enter choice (1): 1
JDK already exists, using
/var/lib/ambari-server/resources/jdk-8u112-linux-x64.tar.gz
Installing JDK to /usr/jdk64/
Successfully installed JDK to /usr/jdk64/
JCE Policy archive already exists, using
/var/lib/ambari-server/resources/jce_policy-8.zip
Installing JCE policy...
Check JDK version for Ambari Server...
JDK version found: 8
Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for Ambari
Server.
Checking GPL software agreement...
GPL License for LZO: https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
Enable Ambari Server to download and install GPL Licensed LZO packages [y/n]
(n)? y
Completing setup...
Configuring database...
Enter advanced database configuration [y/n] (n)? y
Configuring database...
==
Choose one of the following options:
[1] - PostgreSQL (Embedded)
[2] - Oracle
[3] - MySQL / MariaDB
[4] - PostgreSQL
[5] - Microsoft SQL Server (Tech Preview)
[6] - SQL Anywhere
[7] - BDB
==
Enter choice (1): 1
Database admin user (postgres):
Database name (ambari):
Postgres schema (ambari):
Username (ambari):
Enter Database Password (bigdata):
Default properties detected. Using built-in database.
Configuring ambari database...
Checking PostgreSQL...
Configuring local database...
Configuring PostgreSQL...
Backup for pg_hba found, reconfiguration not required
Creating schema and user...
done.
Creating tables...
done.
Extracting system views...
.
Ambari repo file contains latest json url
http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json, updating stacks
repoinfos with it...
Adjusting ambari-server permissions and ownership...
Ambari Server 'setup' completed successfully.
{code}
{code:java}
[root@sandbox-host ~]# cat /etc/ambari-server/conf/ambari.properties | grep
server.jdbc
server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat
server.jdbc.database=postgres
server.jdbc.connection-pool=internal
server.jdbc.database_name=ambari
server.jdbc.user.name=ambari
server.jdbc.postgres.schema=ambari
[root@sandbox-host ~]#{code}
{code:java}
[root@sandbox-host ~]# su - postgres
Last login: Wed Nov 25 10:45:30 UTC 2020
-bash-4.2$ psql
psql (9.2.24)
Type "help" for help.
postgres=# \du
List of roles
Role name | Attributes | Member of
---++---
ambari | | {}
postgres | Superuser, Create role, Create DB, Replication | {}
{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
>Assignee: Dmytro Grinenko
>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-me
[jira] [Updated] (AMBARI-25589) When hearbeat is lost sometimes start/stop tasks can hang for a long time.
[ https://issues.apache.org/jira/browse/AMBARI-25589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25589: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.7 > When hearbeat is lost sometimes start/stop tasks can hang for a long time. > -- > > Key: AMBARI-25589 > URL: https://issues.apache.org/jira/browse/AMBARI-25589 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > Attachments: AMBARI-25589.patch > > Time Spent: 20m > Remaining Estimate: 0h > > When transition between IN_PROGRESS and COMPLETED happens in agent while > server is connected, but in not responsive state. The report may get lost. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25590) Ambari Get Hosts API returning empty json
[ https://issues.apache.org/jira/browse/AMBARI-25590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25590: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.7 > Ambari Get Hosts API returning empty json > - > > Key: AMBARI-25590 > URL: https://issues.apache.org/jira/browse/AMBARI-25590 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > Attachments: AMBARI-25590.patch > > Time Spent: 20m > Remaining Estimate: 0h > > *Issue description:* > When API calls in Ambari fail due to DB exceptions. Ambari re-populates > caches from the DB. This causes situation that threads have different > instances of ClusterImpl, so we need an equals and hashCode implemented. So > that look-up in Sets/Maps/comparison worked. > *How this was tested:* > We were able to find a stable way to reproduce the issue by feeding an API > request that produces DB exception. Once we applied the patch this was no > longer reproducible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
