Hopefully not going too far of topic, the code (in perl) that is doing this is:<br><br># Check whether a postmaster server is running at the specified port.<br># Arguments: <version> <cluster> <port><br>sub cluster_port_running {<br>
die "port_running: invalid port $_[2]" if $_[2] !~ /\d+/;<br> my $socketdir = get_cluster_socketdir $_[0], $_[1];<br> my $socketpath = "$socketdir/.s.PGSQL.$_[2]";<br> return 0 unless -S $socketpath;<br>
<br> socket(SRV, PF_UNIX, SOCK_STREAM, 0) or die "socket: $!";<br> my $running = connect(SRV, sockaddr_un($socketpath));<br> close SRV;<br> return $running ? 1 : 0;<br>}<br><br>I think it raises a couple of questions about using this init.d script for pacemaker. The debian maintainers of postgresql have done a wonderful job of pulling together a system for running multiple versions of postgresql together on the one host. This means the init.d script may not do exactly what you want in this case.<br>
<br>I don't know exactly, but you should check what the return code of /etc/init.d/postgresql status is in various scenarios (including more than one version installed at once). Possibly your maintenance procedures will prevent this case occuring in production though.<br>
<br>It may also be the case that for proper pacemaker status checking, you want a more thorough check of the db being up than just the socket being open.<br><br>Hope that helps.<br><br>Joe<br><br><br><br><div class="gmail_quote">
On Fri, Feb 19, 2010 at 9:28 PM, Andrew Beekhof <span dir="ltr"><<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, Feb 19, 2010 at 9:22 AM, Jayakrishnan <<a href="mailto:jayakrishnanlll@gmail.com">jayakrishnanlll@gmail.com</a>> wrote:<br>
> But the issues is that my postgresql log file is getting filled<br>
> with<br>
><br>
> 2010-02-19 13:19:30 IST LOG: incomplete startup packet<br>
> 2010-02-19 13:19:45 IST LOG: incomplete startup packet<br>
> 2010-02-19 13:20:00 IST LOG: incomplete startup packet<br>
> ......<br>
><br>
> messages like this. I googled and I fount that my pgsql monitor is is the<br>
> cause for this. You can see that the message is given at the same instant as<br>
> the monitor interval.<br>
><br>
> Is there any way to get rid of this??<br>
<br>
</div>Perhaps asking on the postgres list might get you a more informed response<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
Pacemaker mailing list<br>
<a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
</div></div></blockquote></div><br>