You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2018/10/16 11:08:00 UTC
[jira] [Updated] (AMBARI-24560) Better debugging for agent start
failure due to stuck fuser call
[ https://issues.apache.org/jira/browse/AMBARI-24560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk updated AMBARI-24560:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> 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)