You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Takashi Sugano (JIRA)" <ji...@apache.org> on 2014/04/25 04:28:16 UTC
[jira] [Created] (CLOUDSTACK-6503) Restarting services monitored in
VR fails while the monitoring script logs it succeeded
Takashi Sugano created CLOUDSTACK-6503:
------------------------------------------
Summary: Restarting services monitored in VR fails while the monitoring script logs it succeeded
Key: CLOUDSTACK-6503
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6503
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Virtual Router
Affects Versions: 4.3.0
Environment: Tested on KVM hosts, but I anticipated that this would happen other hypervisors.
Reporter: Takashi Sugano
In VR the service command reports it succeeded to restart a service while it actually didn't in some cases where, for example, the service command binary is accidentary removed. This can be reproduced as follows:
root@r-3-VM# service dnsmasq stop; rm -f /usr/sbin/dnsmasq
Since the monitorServices.py script relies on the service command to know if restarting a service gets done successfully or not, the script keeps writing "The process dnsmasq is recovered successfully" in /var/log/messages forever.
--
This message was sent by Atlassian JIRA
(v6.2#6252)