cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinandan Prateek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3583) Management server stop is not removing the PID
Date Thu, 05 Sep 2013 10:46:52 GMT

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

Abhinandan Prateek updated CLOUDSTACK-3583:
-------------------------------------------

    Priority: Critical  (was: Major)
    
> 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 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

Mime
View raw message