cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8815) Issues with cloudstack-management init script
Date Mon, 21 Sep 2015 17:57:04 GMT


ASF GitHub Bot commented on CLOUDSTACK-8815:

Github user remibergsma commented on the pull request:
    @sudhansu7 I think in the mean while this problem fixed itself: @wido contributed systemd
profiles so it's not needed any more to fix the CentOS 7 sysv scripts.

> Issues with cloudstack-management init script
> ---------------------------------------------
>                 Key: CLOUDSTACK-8815
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>            Reporter: Sudhansu Sahu
>            Assignee: Sudhansu Sahu
>         Attachments: screenshot-1.png, screenshot-2.png
> When a management server is halted or rebooted, the cloudstack-management init script
does not successfully kill the associated java process. There will always be an error about
"Cannot find PID file". The script should be reworked so that there are no errors and java
is killed correctly.
> This appears to be due to the script using the basename of the script:
> NAME="$(basename $0)"
> To look for the pid file:
> if [ -f /var/run/$
> {NAME}
> .pid ]; then
> This does work correctly if the script is run directly (basename will be "cloudstack-management",
so "" file is found). However when a server is halted or rebooted,
the script is not run directly but via the symlinks in /etc/rc.d/rc0.d/ and /etc/rc.d/rc0.d/,
respectively. The symlinks are named "K20cloudstack-management" so the script looks for a
pid file named "" which does not exist.

This message was sent by Atlassian JIRA

View raw message