Hi all,
I 've recently noticed that I get a lot warning in the ha-log concerning
gmain_timeout_dispatch on one of my drbd/heartbeat setups. The machines
are running virtually on two ESXi machines, which are connected via a
D-Line. When I take a look at the /var/log/ha-log I see one message
appear over and over again.
Aug 19 14:07:34 sl00003 heartbeat: [2926]: WARN: Gmain_timeout_dispatch:
Dispatch function for check for signals was delayed 4620 ms (> 510 ms)
before being called (GSource: 0x1268f90)
Aug 19 14:07:34 sl00003 heartbeat: [2926]: info: Gmain_timeout_dispatch:
started at 4361743288 should have started at 4361742826
Aug 19 14:07:34 sl00003 heartbeat: [2926]: WARN: Gmain_timeout_dispatch:
Dispatch function for client audit was delayed 5390 ms (> 5000 ms)
before being called (GSource: 0x1268ed0)
Aug 19 14:07:34 sl00003 heartbeat: [2926]: info: Gmain_timeout_dispatch:
started at 4361743288 should have started at 4361742749
I don't really know due to what I get such a big delay? Could someone
give me hint.
Here my crm configure
node $id="51b018f8-1c37-4a3e-a4bc-a29cc981c1a6" sl00004
node $id="94f068b2-bf97-4598-8864-aa24a3b6f916" sl00003
primitive drbd ocf:linbit:drbd \
params drbd_resource="r0"
primitive fs ocf:heartbeat:Filesystem \
params device="/dev/drbd0" directory="/data" fstype="none"
primitive ip ocf:heartbeat:IPaddr2 \
params ip="10.1.1.100" nic="eth0"
primitive mailto ocf:heartbeat:MailTo \
params email="xxxxx" subject="[Alert] xxxx db"
group cluster mailto fs ip \
meta target-role="Started"
ms ms-drbd drbd \
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true" target-role="Started"
colocation fs-with-drbdmaster inf: cluster ms-drbd:Master
order ms-drbd-before-fs inf: ms-drbd:promote cluster:start
property $id="cib-bootstrap-options" \
dc-version="1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd" \
cluster-infrastructure="Heartbeat" \
stonith-enabled="false" \
no-quorum-policy="ignore" \
last-lrm-refresh="1274177587"
Thanks
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
