You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2014/06/26 19:59:24 UTC

[jira] [Updated] (AMBARI-6288) ambari-server may kill INIT and SSHD process (in some specific scenarios)

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

Dmitry Lysnichenko updated AMBARI-6288:
---------------------------------------

    Attachment: AMBARI-6288-1.6.1.patch

> ambari-server may kill INIT and SSHD process (in some specific scenarios)
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-6288
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6288
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.6.1
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 1.6.1
>
>         Attachments: AMBARI-6288-1.6.1.patch
>
>
> h2. STR:
> # create directory 
> # change current dir to this directory
> # remove directory
> # run ambari-server restart. It will complain that could not perform getcwd and fail.
> # Check ambari-server PID file:
> {code}
> # cat /var/run/ambari-server/ambari-server.pid 
> 1
> {code}
> # The 1 is a PID of an */sbin/init process*
> {code}
> cat /proc/1/cmdline 
> /sbin/init
> {code}
> # Try to restart ambari-server. It notices that old process (INIT) is running and tries to kills it. As a result, INIT process does not die, but SSHD and probably other services are killed, active login sessions are terminated.
> # Now host is not available over SSH and requires physical access



--
This message was sent by Atlassian JIRA
(v6.2#6252)