You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/03/11 20:58:41 UTC
[jira] [Commented] (AMBARI-10021) Python Does Not Close Alert TCP
Connections Reliably
[ https://issues.apache.org/jira/browse/AMBARI-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357481#comment-14357481 ]
Hudson commented on AMBARI-10021:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2007 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2007/])
AMBARI-10021 - Python Does Not Close Alert TCP Connections Reliably (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=516d718fc96625a146a9e276c65a8fd9990a5976)
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_thrift_port.py
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/files/alert_hive_thrift_port.py
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/alerts/alert_nodemanager_health.py
* ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/alerts.json
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/alerts.json
* ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/alerts.json
* ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py
* ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/alerts.json
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/WEBHCAT/package/files/alert_webhcat_server.py
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/alerts/alert_nodemanagers_summary.py
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/alerts.json
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_ha_namenode_health.py
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/alerts.json
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/alerts.json
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/package/files/alert_nodemanager_health.py
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/files/alert_ha_namenode_health.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/alerts.json
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/files/alert_checkpoint_time.py
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_metastore.py
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_webhcat_server.py
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/alerts.json
* ambari-agent/src/main/python/ambari_agent/alerts/metric_alert.py
* ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/alerts.json
> Python Does Not Close Alert TCP Connections Reliably
> ----------------------------------------------------
>
> Key: AMBARI-10021
> URL: https://issues.apache.org/jira/browse/AMBARI-10021
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.0.0
>
>
> During installs, we've seen a process bound to port 50070. This causes the NN to abort startup.
> This is with build: 1129
> {noformat}
> root@hdp2-02-01 hdfs]# netstat -anp | grep 50070
> tcp 0 0 192.168.1.141:50070 192.168.1.141:50070 ESTABLISHED 1630/python2.6
> [root@hdp2-02-01 hdfs]# ps aux | grep 1630
> root 1630 2.7 1.0 837364 50508 ? Sl Mar07 114:13 /usr/bin/python2.6
> /usr/lib/python2.6/site-packages/ambari_agent/main.py start restart
> root 16057 0.0 0.0 103252 820 pts/0 S+ 08:54 0:00 grep 1630
> {noformat}
> The NN Log is:
> {noformat}
> 2015-03-10 08:50:13,046 FATAL namenode.NameNode (NameNode.java:main(1509))
> - Failed to start namenode.
> java.net.BindException: Port in use: 192.168.1.141:50070
> at org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:891)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:827)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeHttpServer.start(NameNodeHtt
> pServer.java:142)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.startHttpServer(NameNode.ja
> va:703)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:59
> 0)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:762)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:746)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.jav
> a:1438)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1504)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:444)
> at sun.nio.ch.Net.bind(Net.java:436)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at
> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.ja
> va:216)
> at org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:886)
> ... 8 more
> 2015-03-10 08:50:13,056 INFO util.ExitUtil (ExitUtil.java:terminate(124))
> - Exiting with status 1
> 2015-03-10 08:50:13,068 INFO namenode.NameNode (StringUtils.java:run(659))
> - SHUTDOWN_MSG:
> /************************************************************
> SHUTDOWN_MSG: Shutting down NameNode at
> 192.168.1.141/192.168.1.141
> ************************************************************/
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)