On Tue, Feb 28, 2017 at 01:01:41AM +0100, users-requ...@clusterlabs.org wrote:
> > The oddity is - these are the only two boxes with this issue, and we have a
> > couple dozen at the same OS and level. Only these two, with this role and
> > this particular package set have the issue.
reminds
use something like standby?
2017-03-03 16:02 GMT+01:00 Ulrich Windl :
emmanuel segura schrieb am 03.03.2017 um 15:35 in
> Nachricht
>
Sorry, but can you please tell me where introduce the mysql check?
Is it not possible to introduce a countdown in order to start a guest 120
seconds after the mysql guest?
Thanks a lot
El 3 mar. 2017 11:51 a. m., "Dejan Muhamedagic"
escribió:
Hi,
On Wed, Mar 01, 2017 at
On 03/03/17 12:59, Ulrich Windl wrote:
> Hello!
>
> After Update and reboot of 2nd of three nodes (SLES11 SP4) I see a
> "cluster-dlm[4494]: setup_cpg_daemon: daemon cpg_join error retrying" message
> when I expected the node to joint the cluster. What can be the reasons for
> this?
> In fact
>>> emmanuel segura schrieb am 03.03.2017 um 15:35 in
Nachricht
I think is a good idea to put your cluster in maintenance mode, when
you do an update.
2017-03-03 15:11 GMT+01:00 Ulrich Windl :
emmanuel segura schrieb am 03.03.2017 um 14:22 in
> Nachricht
>
>>> emmanuel segura schrieb am 03.03.2017 um 14:22 in
Nachricht
Appreciate the offer - not familiar with monit.
Going to try running atop through logratate for the day, keep 12, rotate hourly
(to control space utilization) and see if I can catch anything that way. My
biggest issue is we've not caught it as it starts, so we don't ever see
anything amiss.
your cluster was in maintenance state?
2017-03-03 13:59 GMT+01:00 Ulrich Windl :
> Hello!
>
> After Update and reboot of 2nd of three nodes (SLES11 SP4) I see a
> "cluster-dlm[4494]: setup_cpg_daemon: daemon cpg_join error retrying" message
> when I expected
Hello!
After Update and reboot of 2nd of three nodes (SLES11 SP4) I see a
"cluster-dlm[4494]: setup_cpg_daemon: daemon cpg_join error retrying" message
when I expected the node to joint the cluster. What can be the reasons for this?
In fact this seems to have killed cluster communication,
Hi,
On Wed, Mar 01, 2017 at 01:47:21PM +0100, Oscar Segarra wrote:
> Hi Dejan,
>
> In my environment, is it possible to launch the check from the hypervisor.
> A simple telnet against an specific port may be enough tp check if service
> is ready.
telnet is not so practical for scripts, better
11 matches
Mail list logo