Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2BC1FE05B for ; Tue, 19 Feb 2013 11:37:18 +0000 (UTC) Received: (qmail 24466 invoked by uid 500); 19 Feb 2013 11:37:17 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 24420 invoked by uid 500); 19 Feb 2013 11:37:16 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 24340 invoked by uid 99); 19 Feb 2013 11:37:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2013 11:37:12 +0000 Date: Tue, 19 Feb 2013 11:37:12 +0000 (UTC) From: "GURURAJA RAO (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-1324) Unable to start the cloud-managment service MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 GURURAJA RAO created CLOUDSTACK-1324: ---------------------------------------- Summary: Unable to start the cloud-managment service Key: CLOUDSTACK-1324 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1324 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.0.0 Environment: on Cent 0S 6.2 Reporter: GURURAJA RAO I had setup trial version of Cloud Platform on Cent OS successfully and accessed the GUI. After restart, managment server is throwing 'Connection refused' error in browser. I tried to restart the 'cloud-managment' service by removing the some references to old pid and lock. Service comes up and listens up on port 8080. AFter few secs, the listening on port 8080 gets lost. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira