You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2015/12/03 23:16:11 UTC

[jira] [Updated] (AMBARI-13233) Error message for ambari agent install failure when the ping port is taken by old agent process should state port and old process

     [ https://issues.apache.org/jira/browse/AMBARI-13233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yusaku Sako updated AMBARI-13233:
---------------------------------
    Fix Version/s:     (was: trunk)
                   2.3.0

> Error message for ambari agent install failure when the ping port is taken by old agent process should state port and old process
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13233
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13233
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.1.0
>            Reporter: Di Li
>            Assignee: Di Li
>            Priority: Minor
>             Fix For: 2.3.0
>
>         Attachments: AMBARI-13233.patch
>
>
> When the Ambari Agent's ping port is taken by old/left over ambari agent process. the Ambari agent install fails during the cluster installation time. The error message simply says Address already in use. As shown below.
> "ERROR 2015-08-14 17:11:26,557 main.py:272 - Failed to start ping port listener of: [Errno 98] Address already in use"
> The error message could have been more specific on which port was used by which process. 
> In fact, the err msg is there in the ambari-agent/src/main/python/ambari_agent/PingPortListener.py already. It's just that it was never used due to the way the awk parses the pid.
> This JIRA is to attempt to fix the awk parse cmd so that the Ambari agent python script would throw the exception with a detailed error message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)