Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 1F86F651785 for ; Mon, 23 Jun 2008 15:31:02 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 93347-01-3 for ; Mon, 23 Jun 2008 15:30:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id EF2EE6517D8 for ; Mon, 23 Jun 2008 15:19:54 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 8C672DCC3FB; Mon, 23 Jun 2008 20:19:52 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mha-laptop.hagander.net (Postfix) with ESMTP id 1ABF71240A8; Mon, 23 Jun 2008 20:19:52 +0200 (CEST) Message-ID: <485FE947.80805@hagander.net> Date: Mon, 23 Jun 2008 20:19:51 +0200 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: "Marc G. Fournier" CC: Alvaro Herrera , PostgreSQL WWW Subject: Re: Archives broken by new mail VM? References: <485F8754.3090106@hagander.net> <24392011FB03B576F6AAFFF8@ganymede.hub.org> In-Reply-To: <24392011FB03B576F6AAFFF8@ganymede.hub.org> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/180 X-Sequence-Number: 15407 Seems to be up and working again now. Thanks! //Magnus Marc G. Fournier wrote: > > Should be fixed ... missed starting rsync --daemon and switchihg mail to point > to the new VPS ... > > I can't find where the sync process is kicked off though, so either someone > else will have to do that, or just wait fo rit to kick off on its own ... > > --On Monday, June 23, 2008 13:21:56 +0200 Magnus Hagander > > wrote: > >> Seems we don't get anything into the archives anymore, and the search >> system is sending out alarms because it's not finding anything My first >> guess is that it's somehow related to the move of the VM. Can somebody >> who knows anything about this new VM (hello Marc) please look into that >> ASAP? Thanks! > >> //Magnus > > >