Re: what is up with the PG mailing lists? - Mailing list pgsql-www
From | Marc G. Fournier |
---|---|
Subject | Re: what is up with the PG mailing lists? |
Date | |
Msg-id | B7245D11FCB5AF5EEEAAA436@ganymede.hub.org Whole thread Raw |
In response to | what is up with the PG mailing lists? (Tom Lane <tgl@sss.pgh.pa.us>) |
Responses |
Re: what is up with the PG mailing lists?
|
List | pgsql-www |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is where I hate debugging email issues ... Bruce IMd me about this, I looked around and the only problem that I could see was that the caching DNS server within the VPS itself was still reporting one scanner, so I restarted named, and postfix after to clear out any caches it might have, and mail started flowing again ... The only thing I have in the log file is: Nov 1 14:22:41 postgresql postfix/smtpd[26360]: E4E039FC8E6: client=hub.org[200.46.204.220] Nov 1 14:22:41 postgresql postfix/cleanup[73513]: E4E039FC8E6: message-id=<A43323733D66A14A086CABF7@ganymede.hub.org> Nov 1 14:23:58 postgresql postfix/qmgr[7655]: E4E039FC8E6: from=<scrappy@hub.org>, size=3553, nrcpt=1 (queue active) Nov 1 16:12:19 postgresql postfix/smtp[51424]: E4E039FC8E6: to=<pgsql-www-postgresql.org@postgresql.org>, orig_to=<pgsql-www@postgresql.org>, relay=maia.hub.org[200.46.204.184]:10024, conn_use=7, delay=6578, delays=78/6496/0.01/3.9, dsn=2.6.0, status=sent (250 2.6.0 Ok, id=62395-04-7, from MTA: 250 2.0.0 Ok: queued as 9E4B49FC802) Nov 1 16:12:19 postgresql postfix/qmgr[7655]: E4E039FC8E6: removed Which shows the 'delay', but, there are no errors on the scanner server, nor did I touch either of htem to fix the problem ... so it looks like the scanner received it and hung trying to send it back, until I reset the receiving side, whereby it finished .. But there is nothing on either side to indicate a problem ... but restarting postfix 'unstuck' it ... - --On Thursday, November 01, 2007 15:23:12 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote: > "Marc G. Fournier" <scrappy@hub.org> writes: >> But, again, it would be interesting to look at a specific one, with >> message-id, and see what the logs show for reasons of delays ... > > Well, the current problems seem to be entirely inside hub.org, and so > all this banter about DNS etc seems not relevant. A handy example is > this same message I'm replying to, which seems to have been hung up > for 2.5 hours: > > Received: from maia-2.hub.org (maia-2.hub.org [200.46.204.187] (may be > forged)) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lA1JCPC2010552 > for <tgl@sss.pgh.pa.us>; Thu, 1 Nov 2007 15:12:26 -0400 (EDT) > Received: from postgresql.org (postgresql.org [200.46.204.71]) > by maia-2.hub.org (Postfix) with ESMTP id 912252C9544 > for <tgl@sss.pgh.pa.us>; Thu, 1 Nov 2007 16:12:22 -0300 (ADT) > Received: from localhost (unknown [200.46.204.184]) > by postgresql.org (Postfix) with ESMTP id 9E4B49FC802 > for <pgsql-www-postgresql.org@postgresql.org>; Thu, 1 Nov 2007 16:12:18 > -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) > by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) > with ESMTP id 62395-04-7 for <pgsql-www-postgresql.org@postgresql.org>; > Thu, 1 Nov 2007 16:12:11 -0300 (ADT) > Received: from hub.org (hub.org [200.46.204.220]) > by postgresql.org (Postfix) with ESMTP id E4E039FC8E6 > for <pgsql-www@postgresql.org>; Thu, 1 Nov 2007 14:22:40 -0300 (ADT) > Received: from localhost (unknown [200.46.204.184]) > by hub.org (Postfix) with ESMTP id A428DB475C8 > for <pgsql-www@postgresql.org>; Thu, 1 Nov 2007 13:43:35 -0300 (ADT) > Received: from hub.org ([200.46.204.220]) > by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) > with ESMTP id 56221-03; Thu, 1 Nov 2007 13:43:01 -0300 (ADT) > Received: from fserv.hub.org (blk-137-93-67.eastlink.ca [24.137.93.67]) > by hub.org (Postfix) with ESMTP id BB0BCB47581; > Thu, 1 Nov 2007 13:43:02 -0300 (ADT) > Received: from [192.168.1.2] (unknown [192.168.1.2]) > by fserv.hub.org (Postfix) with ESMTP id AD2C34E165; > Thu, 1 Nov 2007 13:43:02 -0300 (ADT) > Date: Thu, 01 Nov 2007 13:42:31 -0300 > From: "Marc G. Fournier" <scrappy@hub.org> > To: "Joshua D. Drake" <jd@commandprompt.com> > cc: Magnus Hagander <magnus@hagander.net>, > Andrew Sullivan <ajs@crankycanuck.ca>, pgsql-www@postgresql.org > Subject: Re: [pgsql-www] what is up with the PG mailing lists? > Message-ID: <A43323733D66A14A086CABF7@ganymede.hub.org> > In-Reply-To: <20071101092806.3b1fa452@scratch> > References: <25716.1193887595@sss.pgh.pa.us> > <DADF296033D290EF9634F611@ganymede.hub.org> <26669.1193891360@sss.pgh.pa.us> > <47299585.7030402@hagander.net> <47299957.5020605@postgresql.org> > <2968.1193919208@sss.pgh.pa.us> <20071101080959.49f3087b@scratch> > <20071101152333.GM27676@crankycanuck.ca> <4729F105.30704@hagander.net> > <1127E6493CBA8A29F343C4D7@ganymede.hub.org> <4729F7D2.6050608@hagander.net> > <AD9BF3BA60F6634EA7FCDB76@ganymede.hub.org> > <20071101092806.3b1fa452@scratch> X-Mailer: Mulberry/4.0.8 (Linux/x86) > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > X-Virus-Scanned: Maia Mailguard 1.0.1 > X-Virus-Scanned: Maia Mailguard 1.0.1 > X-Mailing-List: pgsql-www > List-Archive: <http://archives.postgresql.org/pgsql-www> > List-Help: <mailto:majordomo@postgresql.org?body=help> > List-ID: <pgsql-www.postgresql.org> > List-Owner: <mailto:pgsql-www-owner@postgresql.org> > List-Post: <mailto:pgsql-www@postgresql.org> > List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-www> > List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-www> > Precedence: bulk > Sender: pgsql-www-owner@postgresql.org > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKk2T4QvfyHIvDvMRAsA/AKCFj3U3RNAIvehPULV8S8PfbgeLlwCcDZSp qCWZnSOOTTQydS1Tk+e1Vs8= =DFh4 -----END PGP SIGNATURE-----