<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Andrew Beekhof wrote:
<blockquote
cite="mid:26ef5e70810060629p202290cboef450d1ff862d52@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">In short - pingd in 0.7 is/was completely broken on linux (but worked
great on Darwin).
Sorry :(
The good news is that I have it basically functioning properly now - I
just need to clean up the patch before I commit (which I'll do over
the weekend).
</pre>
</blockquote>
<pre wrap=""><!---->
Would you be able to verify that pingd in the new packages (0.7.3-2.1)
behaves properly?
</pre>
</blockquote>
I installed the debian/etch packages from Oct 06 and no longer see "bad
echo" messages:<br>
<br>
Oct 7 00:32:33 xen20b attrd_updater: [29206]: info: Invoked:
/usr/sbin/attrd_updater -S status -n cpu_speed -v 4002.38<br>
Oct 7 00:32:33 xen20b attrd_updater: [29209]: info: Invoked:
/usr/sbin/attrd_updater -S status -n cpu_cores -v 2<br>
Oct 7 00:32:33 xen20b attrd_updater: [29214]: info: Invoked:
/usr/sbin/attrd_updater -S status -n cpu_load -v 2.05<br>
Oct 7 00:32:33 xen20b attrd_updater: [29226]: info: Invoked:
/usr/sbin/attrd_updater -S status -n ram_total -v 550<br>
Oct 7 00:32:33 xen20b attrd_updater: [29236]: info: Invoked:
/usr/sbin/attrd_updater -S status -n ram_free -v 100<br>
Oct 7 00:32:33 xen20b attrd_updater: [29246]: info: Invoked:
/usr/sbin/attrd_updater -S status -n root_free -v 40%<br>
Oct 7 00:32:36 xen20b pingd: [12186]: info: stand_alone_ping: Node
195.244.97.241 is alive<br>
Oct 7 00:32:36 xen20b pingd: [12186]: info: send_update: 1 active ping
nodes<br>
Oct 7 00:32:42 xen20b pingd: [12197]: info: stand_alone_ping: Node
172.17.32.23 is alive<br>
Oct 7 00:32:42 xen20b pingd: [12197]: info: stand_alone_ping: Node
192.168.132.23 is alive<br>
Oct 7 00:32:42 xen20b pingd: [12197]: info: send_update: 2 active ping
nodes<br>
Oct 7 00:32:46 xen20b pingd: [12186]: info: stand_alone_ping: Node
195.244.97.241 is alive<br>
Oct 7 00:32:46 xen20b pingd: [12186]: info: send_update: 1 active ping
nodes<br>
Oct 7 00:32:52 xen20b pingd: [12197]: info: stand_alone_ping: Node
172.17.32.23 is alive<br>
Oct 7 00:32:52 xen20b pingd: [12197]: info: stand_alone_ping: Node
192.168.132.23 is alive<br>
Oct 7 00:32:52 xen20b pingd: [12197]: info: send_update: 2 active ping
nodes<br>
Oct 7 00:32:53 xen20b attrd: [3562]: info: attrd_ha_callback: (null)
message from (null)<br>
Oct 7 00:32:53 xen20b attrd: [3562]: info: find_hash_entry: Ignoring
message with no attribute name<br>
Oct 7 00:32:53 xen20b attrd_updater: [29337]: info: Invoked:
/usr/sbin/attrd_updater -S status -n arch -v x86_64<br>
Oct 7 00:32:53 xen20b attrd_updater: [29340]: info: Invoked:
/usr/sbin/attrd_updater -S status -n os -v Linux-2.6.18-6-xen-amd64<br>
Oct 7 00:32:53 xen20b attrd_updater: [29363]: info: Invoked:
/usr/sbin/attrd_updater -S status -n free_swap -v 2050<br>
Oct 7 00:32:53 xen20b attrd_updater: [29370]: info: Invoked:
/usr/sbin/attrd_updater -S status -n cpu_info -v Intel(R) Xeon(R)
CPU 5110 @ 1.60GHz<br>
Oct 7 00:32:53 xen20b attrd_updater: [29371]: info: Invoked:
/usr/sbin/attrd_updater -S status -n cpu_speed -v 4002.38<br>
Oct 7 00:32:53 xen20b attrd_updater: [29372]: info: Invoked:
/usr/sbin/attrd_updater -S status -n cpu_cores -v 2<br>
Oct 7 00:32:53 xen20b attrd_updater: [29377]: info: Invoked:
/usr/sbin/attrd_updater -S status -n cpu_load -v 2.05<br>
Oct 7 00:32:53 xen20b attrd_updater: [29387]: info: Invoked:
/usr/sbin/attrd_updater -S status -n ram_total -v 550<br>
Oct 7 00:32:53 xen20b attrd_updater: [29397]: info: Invoked:
/usr/sbin/attrd_updater -S status -n ram_free -v 100<br>
Oct 7 00:32:53 xen20b attrd_updater: [29407]: info: Invoked:
/usr/sbin/attrd_updater -S status -n root_free -v 40%<br>
Oct 7 00:32:56 xen20b pingd: [12186]: info: stand_alone_ping: Node
195.244.97.241 is alive<br>
Oct 7 00:32:56 xen20b pingd: [12186]: info: send_update: 1 active ping
nodes<br>
<br>
But I can't detect in the cibadmin -Q output any trace of the set
attributes!<br>
Where should they be located ?<br>
Do I have to initialize them manually so that pingd can update them?
How?<br>
BTW: the output of the SysInfo clone-resource is there:<br>
<br>
<node_state uname="xen20b.fqdn" ha="active" in_ccm="true"
crmd="online" join="member" shutdown="0" expected="member"
id="278bebc6-2a59-4fa9-be2f-f6e262ce8936"
crm-debug-origin="do_update_resource"><br>
<transient_attributes
id="278bebc6-2a59-4fa9-be2f-f6e262ce8936"><br>
<instance_attributes
id="status-278bebc6-2a59-4fa9-be2f-f6e262ce8936"><br>
<nvpair name="root_free"
id="status-278bebc6-2a59-4fa9-be2f-f6e262ce8936-root_free"
value="40%"/><br>
<nvpair
id="status-278bebc6-2a59-4fa9-be2f-f6e262ce8936-os" name="os"
value="Linux-2.6.18-6-xen-amd64"/><br>
<nvpair
id="status-278bebc6-2a59-4fa9-be2f-f6e262ce8936-arch" name="arch"
value="x86_64"/><br>
<br>
# ps -ef | grep pingd<br>
root 6440 1 0 Oct06 ? 00:00:00
/usr/lib/heartbeat/pingd -D -p
/var/run/heartbeat/rsctmp/pingd-pingd-internal:0 -a pingd-internal -d
5s -m 1000 -h 172.17.32.23 -h 192.168.132.23<br>
root 6502 1 0 Oct06 ? 00:00:00
/usr/lib/heartbeat/pingd -D -p
/var/run/heartbeat/rsctmp/pingd-pingd-external:0 -a pingd-external -d
5s -m 1000 -h 195.244.97.241<br>
<br>
<blockquote
cite="mid:26ef5e70810060629p202290cboef450d1ff862d52@mail.gmail.com"
type="cite">
<pre wrap="">Btw. You can also run it from the command line (with no cluster
present) by supplying the -U option.
Instead of trying to update attrd, it will instead output the message
it would have sent.
</pre>
</blockquote>
/usr/lib/heartbeat/pingd -U -a pingd-internal -d 5s -m 1000 -h
172.17.32.23<br>
does not generate any output on the console.<br>
The -U switch does not appear in pingd --help.<br>
<br>
WR,<br>
Bruno<br>
<br>
</body>
</html>