Received: from localhost (unknown [200.46.204.184])
	by developer.postgresql.org (Postfix) with ESMTP id 6C6192E0032
	for <pgsql-admin-postgresql.org@developer.postgresql.org>;
	Tue, 29 Apr 2008 05:31:10 -0300 (ADT)
Received: from developer.postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024)
	with ESMTP id 82009-07
	for <pgsql-admin-postgresql.org@developer.postgresql.org>;
	Tue, 29 Apr 2008 05:31:03 -0300 (ADT)
X-Greylist: delayed 00:08:41.96377 by SQLgrey-1.7.5
Received: from smtp-out3.libero.it (smtp-out3.libero.it [212.52.84.43])
	by developer.postgresql.org (Postfix) with ESMTP id 2D5642E002D
	for <pgsql-admin@postgresql.org>; Tue, 29 Apr 2008 05:31:07 -0300 (ADT)
Received: from MailRelay10.libero.it (192.168.32.119) by smtp-out3.libero.it
	(7.3.120) id 4628C87A0B550DD2 for pgsql-admin@postgresql.org;
	Tue, 29 Apr 2008 10:22:23 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkCAMR3FkiXSXys/2dsb2JhbAAIrCI
Received: from unknown (HELO [192.168.1.2]) ([151.73.124.172])
	by outrelay-b10.libero.it with ESMTP; 29 Apr 2008 10:22:23 +0200
From: Pietro <bpietro@simail.it>
To: pgsql-admin@postgresql.org
Subject: Re: Resolved - LAN connection to server only after restart server
Date: Tue, 29 Apr 2008 10:22:22 +0200
User-Agent: KMail/1.9.7
References: <200803131020.07510.bpietro@simail.it>
	<17513.1205422296@sss.pgh.pa.us>
In-Reply-To: <17513.1205422296@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200804291022.22605.bpietro@simail.it>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200804/278
X-Sequence-Number: 29042

At Thursday 13 March 2008 16:31:36 Tom Lane wrote:
> Pietro <bpietro@simail.it> writes:
> > It isn't so serious problem for me, only boring one, because each morning
> > I must start server box and then manually restart posgresql server.
>

Problem resolved:

Annoying part of this problem was its intermittent character. Two days all OK, 
another one not working until restart, and so on.
Then I discover this line of log: could not bind IPv4 socket.
IMHO it was timing problem. Some days posgresql server was too quick and
tryied binding while network part wasn't wake up yet.
So I added nice 'sleep 10' in postgresql startup script and now all work well.

Regards
Pietro