Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 4C0822E0060 for ; Sun, 4 May 2008 21:29:30 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 08578-03 for ; Sun, 4 May 2008 21:29:21 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by developer.postgresql.org (Postfix) with ESMTP id 8EF762E002C for ; Sun, 4 May 2008 21:29:26 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.1/8.14.1) with ESMTP id m450TKIf009079 for ; Sun, 4 May 2008 21:29:20 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.1/8.14.1/Submit) id m4502SEF098118 for pgsql-admin@postgresql.org; Sun, 4 May 2008 21:02:28 -0300 (ADT) (envelope-from news) Date: Sun, 04 May 2008 20:02:31 -0400 From: Lew User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 X-Newsgroups: pgsql.admin Subject: Re: Resolved - LAN connection to server only after restart server References: <200803131020.07510.bpietro@simail.it> <17513.1205422296@sss.pgh.pa.us> <200804291022.22605.bpietro@simail.it> In-Reply-To: <200804291022.22605.bpietro@simail.it> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Lines: 19 X-Usenet-Provider: http://www.giganews.com X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.39 To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/31 X-Sequence-Number: 29115 Pietro wrote: > At Thursday 13 March 2008 16:31:36 Tom Lane wrote: >> Pietro 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. Thank you so very much, molto grazie, for sharing the solution with us. -- Lew