Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 6 Nov 2014 12:40:33 +0000 (UTC)
From: "Bharat Kumar (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12735413.1408544020000.433680.1415277633803@Atlassian.JIRA>
In-Reply-To: <JIRA.12735413.1408544020000@Atlassian.JIRA>
References: <JIRA.12735413.1408544020000@Atlassian.JIRA>
 <JIRA.12735413.1408544020059@arcas>
Subject: [jira] [Resolved] (CLOUDSTACK-7376) passwd_server attempts to start
 but terminates with the exit code 137
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bharat Kumar resolved CLOUDSTACK-7376.
--------------------------------------
    Resolution: Fixed

> passwd_server attempts to start but terminates with the exit code 137
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7376
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7376
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.5.0
>            Reporter: Bharat Kumar
>            Assignee: Bharat Kumar
>             Fix For: 4.5.0
>
>
> "Trying to add a non-contiguous IP range to an existing guest network, upon creation of an instance in the new range, the virtual router is updated with a new sub-interface but the passwd_server service (for serving passwords) is not running.
> If the script /opt/cloud/bin/passwd_server is run manually, then the service starts successfully and passwords can be served.
> If we reboot the virtual router via the CloudPlatform GUI, then it powers back up with the subinterface, but the passwd_server service is not running.
> Checking /var/log/cloud.log, the passwd_server attempts to start but terminates with the exit code 137, which from a quick google appears to be a SIGKILL termination.
> Steps to reproduce the issue
> i) Create a Shared Network in CCP and deploy a VM in the network.
> ii) Now add additional IP range to the same shared network.
> iii) Deploy a new VM in the additional IP range ( you can exhaust the first IP range to achieve this).
> iv) Once the new VM is deployed. Stop/start or restart the Router.
> The password server will fail to come up and following the entries in the logs
> In /var/log/cloud.log from VR
> /opt/cloud/bin/passwd_server_ip: line 32:  3161 Killed                  socat -lf /var/log/cloud.log TCP4-LISTEN:8080,reuseaddr,fork,crnl,bind=$addr SYSTEM:"/opt/cloud/bin/serve_password.sh \"\$SOCAT_PEERADDR\""
> Also, There is no issue in starting the service manually after ssh into the Router.


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