Hi Edward,
You can disable the health checks as advised by Nicolas.
Additionally worth checking, this could be because of stale VR status on
Management Server's database. You can also try to rerun a health check on
that router from the UI or the API to update the results. (
https://cloudstack.apa
Thanks a lot for your help Nicolas.
Kind regards,
D.Fragkakis
On 2021/01/19 15:44:18, Nicolas Vazquez wrote:
> I would recommend to checkout the code from the repository and start a local
> instance of Primate which points to your CloudStack management server (you
> can specify the mgmt serve
Hi,
Thanks for that Nicolas.
Is that option available on a per VR basis as I have only seen it as a
global option?
Ed
On Fri, 22 Jan 2021 at 14:31, Nicolas Vazquez
wrote:
> Hi Edward,
>
> You can disable the health checks by setting
> 'router.health.checks.enabled' to false.
>
>
> Regards,
>
>
Hi Edward,
You can disable the health checks by setting 'router.health.checks.enabled' to
false.
Regards,
Nicolas Vazquez
From: Edward St Pierre
Sent: Friday, January 22, 2021 11:25 AM
To: users@cloudstack.apache.org
Subject: Health Checks for redundant VR o
Hi,
I have recently updated to version 4.15 from 4.13 and it looks great,
however I seem to have hit a problem with all the alerts filling up with
the following error:
Health checks failed: 1 failing checks on router
342ebf56-4128-4350-967f-cea40c26b080
For pretty most of my redundant VR or VPC
Hi Nicolas,
2021-01-22 08:21:46,824 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-099e13e3) (logid:2e38dea5) Zone 1 is not ready to
launch secondary storage VM yet
2021-01-22 08:21:47,218 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-a788e578) (logid:a5141c91) Zone
Sounds great, keep us posted.
A good solution for using iSCSI/SAN/etc would be great, as it is one of
the bigger let-downs of Cloudstack (or should I say, ACS+KVM/libvirt
combo).
PS: NVMeOF sounds like a game changer, wasn't even aware of it, thanks
for mentioning.
I would need to test t
On 21/01/2021 21:31, n...@li.nux.ro wrote:
Well, there you go..
On 2021-01-21 18:50, Simon Weller wrote:
We used to use CLVM a while ago before we shifted to Ceph. Cluster
suite/corosync was a bit of a nightmare, and fencing events caused all
sorts of locking (DLM) problems.
I helped a Cloud
Hey,
OK, we found the reason, the problem was disabling the default service
offering for console proxy. Normally it doesn't matter, but when a new
certificate is raised, the procedure skips the indicated service offering
and refers directly to the default one. I guess it qualifies for PR?
B
