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 847E3DC9A for ; Tue, 25 Sep 2012 07:19:08 +0000 (UTC) Received: (qmail 28982 invoked by uid 500); 25 Sep 2012 07:19:07 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 28926 invoked by uid 500); 25 Sep 2012 07:19:07 -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 28900 invoked by uid 99); 25 Sep 2012 07:19:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2012 07:19:07 +0000 Date: Tue, 25 Sep 2012 18:19:07 +1100 (NCT) From: "Rohit Yadav (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: <1182265481.120858.1348557547461.JavaMail.jiratomcat@arcas> In-Reply-To: <1726180368.68627.1347442147425.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CLOUDSTACK-81) fail to start cloud-usage service MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462513#comment-13462513 ] Rohit Yadav commented on CLOUDSTACK-81: --------------------------------------- Fixed typo patch in: >From eb26f7a3e4a9f42130fa519b646132e54650970d Mon Sep 17 00:00:00 2001 From: Rohit Yadav Date: Tue, 25 Sep 2012 11:59:34 +0530 Subject: [PATCH] CLOUDSTACK-81: Use non-lsb function > fail to start cloud-usage service > --------------------------------- > > Key: CLOUDSTACK-81 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-81 > Project: CloudStack > Issue Type: Bug > Components: Usage > Affects Versions: pre-4.0.0 > Environment: build :CloudStack-oss-4.0.59-rhel6.3.tar.gz > Reporter: sadhu suresh > Assignee: Wido den Hollander > Priority: Blocker > Fix For: pre-4.0.0 > > > steps: > 1.Install new build on rhel6.3 > 2.install the usage server > 3.start the cloud-usage service > actual result: > Installation of cloud-usage server was successful but fail to start > :cloud-usage service fail to start and it shows the following error when we try to start > root@rhel63 CloudStack-oss-4.0.59-rhel6.3]# service cloud-usage start > Starting CloudStack Usage Monitor: /bin/bash: /usr/bin/cloud-daemonize: No such file or directory > [FAILED] > cloud-usage server installation requires additional rpm and installed additional rpm nd installed > fter installing the jsvc package installation usage server was successful: > [root@rhel63 CloudStack-oss-4.0.59-rhel6.3]# rpm -Uvh http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm > Retrieving http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm > warning: /var/tmp/rpm-tmp.pGKPCJ: Header V3 RSA/SHA256 Signature, key ID c105b9de: NOKEY > Preparing... ########################################### [100%] > 1:jakarta-commons-daemon-########################################### [100%] > [root@rhel63 CloudStack-oss-4.0.59-rhel6.3]# ./install.sh > Setting up the temporary repository... > Cleaning Yum cache... > Loaded plugins: product-id, subscription-manager > Updating certificate-based repositories. > Unable to read consumer identity > Cleaning repos: cloud-temp rhel > 2 metadata files removed > Welcome to the Cloud.com CloudStack Installer. What would you like to do? > A) Install the Agent > B) Install BareMetal Agent > S) Install the Usage Monitor > D) Install the database server > U) Upgrade the CloudStack packages installed on this computer > R) Stop any running CloudStack services and remove the CloudStack packages from this computer > Q) Quit > > s > Installing the Usage Server... > Loaded plugins: product-id, subscription-manager > Updating certificate-based repositories. > Unable to read consumer identity > cloud-temp | 2.6 kB 00:00 ... > rhel | 4.0 kB 00:00 ... > Setting up Install Process > No package cloud-premium available. > Resolving Dependencies > --> Running transaction check > ---> Package cloud-usage.x86_64 0:4.0.59-0.59.el6.4.0 will be installed > --> Finished Dependency Resolution > Dependencies Resolved > ======================================================================================================================================================================== > Package Arch Version Repository Size > ======================================================================================================================================================================== > Installing: > cloud-usage x86_64 4.0.59-0.59.el6.4.0 cloud-temp 81 k > Transaction Summary > ======================================================================================================================================================================== > Install 1 Package(s) > Total download size: 81 k > Installed size: 87 k > Is this ok [y/N]: y > Downloading Packages: > Running rpm_check_debug > Running Transaction Test > Transaction Test Succeeded > Running Transaction > Warning: RPMDB altered outside of yum. > Installing : cloud-usage-4.0.59-0.59.el6.4.0.x86_64 1/1 > Installed products updated. > Verifying : cloud-usage-4.0.59-0.59.el6.4.0.x86_64 1/1 > Installed: > cloud-usage.x86_64 0:4.0.59-0.59.el6.4.0 > Complete! > CloudStack Management Server setup is Done! > [root@rhel63 CloudStack-oss-4.0.59-rhel6.3]# service cloud-management status > cloud-management (pid 2984) is running... > [root@rhel63 CloudStack-oss-4.0.59-rhel6.3]# service cloud-usage start > Starting CloudStack Usage Monitor: /bin/bash: /usr/bin/cloud-daemonize: No such file or directory > [FAILED] -- 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