You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Saksham Srivastava (JIRA)" <ji...@apache.org> on 2013/10/15 12:38:42 UTC
[jira] [Commented] (CLOUDSTACK-3583) Management server stop is not
removing the PID
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795052#comment-13795052 ]
Saksham Srivastava commented on CLOUDSTACK-3583:
------------------------------------------------
Fix is available for review at https://reviews.apache.org/r/14647/
> Management server stop is not removing the PID
> -----------------------------------------------
>
> Key: CLOUDSTACK-3583
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3583
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Sailaja Mada
> Assignee: Saksham Srivastava
> Priority: Critical
> Fix For: 4.2.1
>
>
> Steps:
> 1. Configure Adv Zone with VMWARE
> 2. Deploy VM's 3. Update expunge interval GC value
> 3. Stop the Management server
> [root@ec2 management]# service cloudstack-management stop
> Stopping cloudstack-management: [ OK ]
> 4. Check the status
> cloudstack-management dead but pid file exists
> The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management.
> Starting cloudstack-management will take care of them or you can manually clean up.
> [root@ec2 management]#
> 5. Start the management server
> [root@ec2 management]# service cloudstack-management start
> Starting cloudstack-management: [ OK ]
> 6. Check the status
> [root@ec2 management]# service cloudstack-management status
> cloudstack-management (pid 350) is running...
> [root@ec2 management]#
> But when Management server stopped , status shows as its not a clean stop
> [root@ec2 management]# service cloudstack-management stop
> Stopping cloudstack-management: [ OK ]
> [root@ec2 management]# service cloudstack-management status
> cloudstack-management dead but pid file exists
> The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management.
> Starting cloudstack-management will take care of them or you can manually clean up.
> [root@ec2 management]# service cloudstack-management status
> cloudstack-management dead but pid file exists
> The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management.
> Starting cloudstack-management will take care of them or you can manually clean up.
> [root@ec2 management]# service cloudstack-management start
> Starting cloudstack-management: [ OK ]
> [root@ec2 management]# service cloudstack-management status
> cloudstack-management (pid 350) is running...
> [root@ec2 management]#
> [root@ec2 management]# cat /var/run/cloudstack-management.pid
> 350
> [root@ec2 management]# cat /var/lock/subsys/cloudstack-management
--
This message was sent by Atlassian JIRA
(v6.1#6144)