[jira] [Commented] (AMBARI-24560) Better debugging for agent start failure due to stuck fuser call

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on AMBARI-24560:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9900 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9900/])
AMBARI-24560. Better debugging for agent start failure due to stuck (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a4af8ed297a00b367f5948941b6cd92943d00b13])
* (edit) ambari-agent/src/main/python/ambari_agent/PingPortListener.py


> Better debugging for agent start failure due to stuck fuser call
> ----------------------------------------------------------------
>
>                 Key: AMBARI-24560
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24560
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-24560.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> While debugging with we encountered an issue where call to `fuser 8670/tcp` it got blocked for minutes
> - in fact we did not ever see the agent start and had to comment the call. Two
> improvements:
>   * Need timeout for such calls (lets also research and see why the call may get stuck). We checked that the port was free.
>   * Need more debug logging in the initial start up path to help debug what command is getting stuck - in main.py, and PingPortListener.py lets see if more debug logging can be added



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)