[
https://issues.apache.org/jira/browse/CLOUDSTACK-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273824#comment-15273824
]
ASF GitHub Bot commented on CLOUDSTACK-6975:
--------------------------------------------
Github user dsclose commented on the pull request:
https://github.com/apache/cloudstack/pull/1514#issuecomment-217392996
@DaanHoogland yes, the line `CsHelper.service("dnsmasq", "restart")` in
`set_master` is in
systemvm/patches/debian/config/opt/cloud/bin/cs/CsRedundant.py. When a backup
router transitions to master, it successfully launches the dnsmasq service.
I should point out that I have only verified that the service is running. I
have not confirmed that it is successfully configured.
> Service monitoring starts dnsmasq on backup router when using redundant VRs
> ---------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6975
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6975
> 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: KVM
> Reporter: Magnus Bengtsson
>
> When using a network offering with redundant routers the default setting of
> EnableServiceMonitoring enables monit on the routers.
> "network.router.EnableServiceMonitoring service monitoring in router
> enable/disable option, default true false"
> This causes monit to run dnsmasq on both the Master and Backup router. When
> the backup router assigns dhcp to clients, password and userdata retrieval
> from that node fails since the services are not running on the backup router.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
