[jira] [Assigned] (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:all-tabpanel
]
Dmytro Grinenko reassigned AMBARI-25591:
Assignee: Dmytro Grinenko
> 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=17238504#comment-17238504
]
Dmytro Grinenko commented on AMBARI-25591:
--
[~dhire...@gmail.com] while RCA is not used anymore, it still marked as
"[deprecated|https://github.com/apache/ambari/blob/branch-2.7/ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java#L1354]";
and should be set properly. The default value is "mapred" through.
In current state settings for default connection and RCA should match and with
embedded mode, setup script will configure both properties properly.
> 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)
[jira] [Resolved] (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:all-tabpanel
]
Dmytro Grinenko resolved AMBARI-25591.
--
Resolution: Invalid
> 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)
[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=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 ser
[jira] [Updated] (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:all-tabpanel
]
Dhirendra Khanka updated AMBARI-25591:
--
Description:
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}
was:
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-
[jira] [Updated] (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:all-tabpanel
]
Dhirendra Khanka updated AMBARI-25591:
--
Attachment: ambari-server.log
> 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}
>
> [^ambari-server.log]
--
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=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-spar
[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=17238251#comment-17238251
]
akiyamaneko commented on AMBARI-25591:
--
[~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)
[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=17238242#comment-17238242
]
Dmytro Grinenko commented on AMBARI-25591:
--
not a lot information available, basically nothing to tell without full stack
trace.
As for the recommendation, verify configured user and password in the
ambari.properties; The warning log might be a result of previous error.
> 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)
[jira] [Updated] (AMBARI-25587) Metrics cannot be stored and the exception message is null when metric value is NaN
[
https://issues.apache.org/jira/browse/AMBARI-25587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-25587:
-
Status: Patch Available (was: Open)
> Metrics cannot be stored and the exception message is null when metric value
> is NaN
>
>
> Key: AMBARI-25587
> URL: https://issues.apache.org/jira/browse/AMBARI-25587
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Environment: Ambari:2.7.4
>Reporter: akiyamaneko
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The exception information frequently appeared in ambari-metrics-collector.log
> as follows：
> {code:java}
> 2020-11-12 12:28:11,200 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : null
> 2020-11-12 12:28:11,200 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [default.General.hs2_avg_active_session_time,hiveserver2]{1605155168235=NaN,
> 1605155198236=NaN, 1605155228235=NaN, 1605155258235=NaN}
> {code}
> The exception message of metrics written to HBase is directly displayed as
> null.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25587) Metrics cannot be stored and the exception message is null when metric value is NaN
[
https://issues.apache.org/jira/browse/AMBARI-25587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-25587:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Metrics cannot be stored and the exception message is null when metric value
> is NaN
>
>
> Key: AMBARI-25587
> URL: https://issues.apache.org/jira/browse/AMBARI-25587
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Environment: Ambari:2.7.4
>Reporter: akiyamaneko
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The exception information frequently appeared in ambari-metrics-collector.log
> as follows：
> {code:java}
> 2020-11-12 12:28:11,200 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : null
> 2020-11-12 12:28:11,200 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [default.General.hs2_avg_active_session_time,hiveserver2]{1605155168235=NaN,
> 1605155198236=NaN, 1605155228235=NaN, 1605155258235=NaN}
> {code}
> The exception message of metrics written to HBase is directly displayed as
> null.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (AMBARI-25591) org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mapred"
Dhirendra Khanka created AMBARI-25591:
-
Summary: 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
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)
[jira] [Updated] (AMBARI-25586) The page will not refresh automatically after the permission was modified in the Files View page
[ https://issues.apache.org/jira/browse/AMBARI-25586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25586: - Resolution: Fixed Status: Resolved (was: Patch Available) > The page will not refresh automatically after the permission was modified in > the Files View page > - > > Key: AMBARI-25586 > URL: https://issues.apache.org/jira/browse/AMBARI-25586 > Project: Ambari > Issue Type: Improvement > Components: contrib >Affects Versions: 2.7.5 >Reporter: akiyamaneko >Priority: Minor > Fix For: 2.7.6 > > Attachments: permission_cannot_auto_refresh.mp4.gif > > Time Spent: 50m > Remaining Estimate: 0h > > In the Files View page in Ambari, select a directory or file to modify its > permission. After the operation was finished, the permission didn't > automatically refresh, which often makes users confused and mistakenly > believed that the operation was not successful. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25586) The page will not refresh automatically after the permission was modified in the Files View page
[ https://issues.apache.org/jira/browse/AMBARI-25586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25586: - Status: Patch Available (was: Open) > The page will not refresh automatically after the permission was modified in > the Files View page > - > > Key: AMBARI-25586 > URL: https://issues.apache.org/jira/browse/AMBARI-25586 > Project: Ambari > Issue Type: Improvement > Components: contrib >Affects Versions: 2.7.5 >Reporter: akiyamaneko >Priority: Minor > Fix For: 2.7.6 > > Attachments: permission_cannot_auto_refresh.mp4.gif > > Time Spent: 50m > Remaining Estimate: 0h > > In the Files View page in Ambari, select a directory or file to modify its > permission. After the operation was finished, the permission didn't > automatically refresh, which often makes users confused and mistakenly > believed that the operation was not successful. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25586) The page will not refresh automatically after the permission was modified in the Files View page
[ https://issues.apache.org/jira/browse/AMBARI-25586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25586: - Fix Version/s: 2.7.6 > The page will not refresh automatically after the permission was modified in > the Files View page > - > > Key: AMBARI-25586 > URL: https://issues.apache.org/jira/browse/AMBARI-25586 > Project: Ambari > Issue Type: Improvement > Components: contrib >Affects Versions: 2.7.5 >Reporter: akiyamaneko >Priority: Minor > Fix For: 2.7.6 > > Attachments: permission_cannot_auto_refresh.mp4.gif > > Time Spent: 50m > Remaining Estimate: 0h > > In the Files View page in Ambari, select a directory or file to modify its > permission. After the operation was finished, the permission didn't > automatically refresh, which often makes users confused and mistakenly > believed that the operation was not successful. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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: - Description: When transition between IN_PROGRESS and COMPLETED happens in agent while server is connected, but in not responsive state. The report may get lost. (was: ) > 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: 10m > 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: - Description: *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. was: 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. 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. > 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 > > > *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)
[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: - 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. 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. > 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 > > > 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. > 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)
[jira] [Created] (AMBARI-25590) Ambari Get Hosts API returning empty json
Andrew Onischuk created AMBARI-25590: Summary: 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 Fix For: 2.7.6 Attachments: AMBARI-25590.patch -- 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: - Attachment: AMBARI-25590.patch > 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 > > -- 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: - Status: Patch Available (was: Open) > 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 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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: - Description: was: Spawned of: https://jira.cloudera.com/browse/ENGESC-5309 > 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: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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: - Attachment: AMBARI-25589.patch > 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 > > > Spawned of: https://jira.cloudera.com/browse/ENGESC-5309 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25589) When hearbeat is lost sometimes start/stop tasks can hang for a long time.
Andrew Onischuk created AMBARI-25589: Summary: 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 Fix For: 2.7.6 Attachments: AMBARI-25589.patch Spawned of: https://jira.cloudera.com/browse/ENGESC-5309 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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: - Status: Patch Available (was: Open) > 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 > > > Spawned of: https://jira.cloudera.com/browse/ENGESC-5309 -- This message was sent by Atlassian Jira (v8.3.4#803005)
