[Pacemaker] postgresql monitoring- "incomplete startup packet"- getting filled in log

[Jayakrishnan]

Sir,

I am using heartbeat-pacemaker for my two node postgresql cluster with slony
database replication. I am using the init script for the postgresql coz my
ocf script is not working. Somehow I manage with my init script.

My packages are:

heartbeat                            2.99.2+sles11r9-5ubuntu1
heartbeat-common                     2.99.2+sles11r9-5ubuntu1
heartbeat-common-dev                 2.99.2+sles11r9-5ubuntu1
heartbeat-dev                        2.99.2+sles11r9-5ubuntu1
libheartbeat2                        2.99.2+sles11r9-5ubuntu1
libheartbeat2-dev                    2.99.2+sles11r9-5ubuntu1
pacemaker-heartbeat                  1.0.5+hg20090813-0ubuntu4
pacemaker-heartbeat-dev              1.0.5+hg20090813-0ubuntu4

My ha.cf file and crm.xml file are attached with in.

My crm file :
_______________________________________________________________
node $id="3952b93e-786c-47d4-8c2f-a882e3d3d105" node2 \
    attributes standby="off"
node $id="ac87f697-5b44-4720-a8af-12a6f2295930" node1 \
    attributes standby="off"
primitive pgsql lsb:postgresql-8.4 \
    meta target-role="Started" resource-stickness="inherited" \
    op monitor interval="15s" timeout="25s" on-fail="standby"
primitive slony-fail lsb:slony_failover \
    meta target-role="Started"
primitive slony-fail2 lsb:slony_failover2 \
    meta target-role="Started"
primitive vir-ip ocf:heartbeat:IPaddr2 \
    params ip="192.168.10.10" nic="eth0" cidr_netmask="24"
broadcast="192.168.10.255" \
    op monitor interval="15s" timeout="25s" on-fail="standby" \
    meta target-role="Started"
clone pgclone pgsql \
    meta notify="true" globally-unique="false" interleave="true"
target-role="Started"
colocation ip-with-slony inf: slony-fail vir-ip
colocation ip-with-slony2 inf: slony-fail2 vir-ip
order ip-b4-slony2 inf: vir-ip slony-fail2
order slony-b4-ip inf: vir-ip slony-fail
property $id="cib-bootstrap-options" \
    dc-version="1.0.5-3840e6b5a305ccb803d29b468556739e75532d56" \
    cluster-infrastructure="Heartbeat" \
    no-quorum-policy="ignore" \
    stonith-enabled="false" \
    last-lrm-refresh="1266563445"
rsc_defaults $id="rsc-options" \
    resource-stickiness="INFINITY"

__________________________________________________________________________
-- 
My ha.cf file

-----------------------------------------------------------------------
autojoin none
keepalive 2
deadtime 15
warntime 5
initdead 64
udpport 694
bcast eth0
auto_failback off
node node1
node node2
crm respawn
use_logd yes
__________________________________________________

The configuration is working fine for me. When I stop the postgresql service
in active machine , it will go to standby and resource is moved to other
machine. But the issues is that my postgresql log file is getting filled
with

2010-02-19 13:19:30 IST LOG:  incomplete startup packet
2010-02-19 13:19:45 IST LOG:  incomplete startup packet
2010-02-19 13:20:00 IST LOG:  incomplete startup packet
......

messages like this. I googled and I fount that my pgsql monitor is is the
cause for this. You can see that the message is given at the same instant as
the monitor interval.

Is there any way to get rid of this??

Regards,

Jayakrishnan. L

Visit: www.jayakrishnan.bravehost.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100219/28801c21/attachment.html>
-------------- next part --------------
node $id="3952b93e-786c-47d4-8c2f-a882e3d3d105" node2 \
	attributes standby="off"
node $id="ac87f697-5b44-4720-a8af-12a6f2295930" node1 \
	attributes standby="off"
primitive pgsql lsb:postgresql-8.4 \
	meta target-role="Started" resource-stickness="inherited" \
	op monitor interval="15s" timeout="25s" on-fail="standby"
primitive slony-fail lsb:slony_failover \
	meta target-role="Started"
primitive slony-fail2 lsb:slony_failover2 \
	meta target-role="Started"
primitive vir-ip ocf:heartbeat:IPaddr2 \
	params ip="192.168.10.10" nic="eth0" cidr_netmask="24" broadcast="192.168.10.255" \
	op monitor interval="15s" timeout="25s" on-fail="standby" \
	meta target-role="Started"
clone pgclone pgsql \
	meta notify="true" globally-unique="false" interleave="true" target-role="Started"
colocation ip-with-slony inf: slony-fail vir-ip
colocation ip-with-slony2 inf: slony-fail2 vir-ip
order ip-b4-slony2 inf: vir-ip slony-fail2
order slony-b4-ip inf: vir-ip slony-fail
property $id="cib-bootstrap-options" \
	dc-version="1.0.5-3840e6b5a305ccb803d29b468556739e75532d56" \
	cluster-infrastructure="Heartbeat" \
	no-quorum-policy="ignore" \
	stonith-enabled="false" \
	last-lrm-refresh="1266563445"
rsc_defaults $id="rsc-options" \
	resource-stickiness="INFINITY"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ha.cf
Type: application/octet-stream
Size: 151 bytes
Desc: not available
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100219/28801c21/attachment.obj>