|
From: Lionel B. <lio...@bo...> - 2005-09-28 18:36:23
|
Who Knows wrote the following on 28.09.2005 03:18 : > Lionel Bouton wrote: > >> No it is automatic. It is designed to recover from both an >> unreachable database and simple query errors (no answer or clearly >> invalid answers). >> Do you rely on the database for anything else than SQLgrey? Was >> SQLgrey running on the same systems the MTAs were on (ie >> policy_service declared as localhost:<something> on each MTA)? >> > My old configuration was sqlgrey v1.6.6-1 > > serverX > local MTA - postfix > local sqlgrey localhost sqlgraydb > > serverY > local MTA - postfix > local sqlgrey remote DB serverX sqlgraydb > > serverZ > local MTA - postfix > local sqlgrey serverX sqlgraydb > > Here is an exerpt of what was happened for all messages arriving at > serverY after serverX swooned: > NOTE: the ****** are to protect the guilty(or innocent) > > Sep 21 07:51:00 serverY postfix/smtpd[3184]: connect from > ablist.about.com[207.241.145.4] > Sep 21 07:51:03 serverY sqlgrey: dbaccess: can't connect to DB: Can't > connect to MySQL server on 'serverX.*******'' (110) > Sep 21 07:51:03 serverY sqlgrey: dbaccess: warning: couldn't do query: > DELETE FROM from_awl WHERE last_seen < timestamp '2005-09-20 21:35:36' > - INTERVAL 60 DAY: Can't connect to MySQL server on 'serverX.*******'' > (110), reconnecting to DB > Sep 21 07:51:03 serverY sqlgrey: warning: Use of uninitialized value > in string eq at /usr/sbin/sqlgrey line 1191. This odd-looking warning, I can deal with. It may be why some messages were rejected but unless SQLgrey died I believe it shouldn't have rejected every message but only a few ones (I'll have to check the flow of SQL queries to be sure that there's no loophole introduced by a recent change, but last time I did it was OK). > > Sep 21 07:51:11 serverY postfix/smtpd[3240]: timeout after RSET from > unknown[80.232.117.10] > Sep 21 07:51:11 serverY postfix/smtpd[3240]: disconnect from > unknown[80.232.117.10] > Sep 21 07:51:11 serverY postfix/smtpd[3130]: timeout after RSET from > unknown[80.232.117.10] > Sep 21 07:51:11 serverY postfix/smtpd[3130]: disconnect from > unknown[80.232.117.10] > Sep 21 07:51:17 serverY postfix/smtpd[3265]: connect from > mail3.inbox360.com[207.106.213.11] > Sep 21 07:51:24 serverY postfix/smtpd[3270]: warning: timeout on > 127.0.0.1:2501 while reading input attribute name > Sep 21 07:51:24 serverY postfix/smtpd[3270]: warning: problem talking > to server 127.0.0.1:2501: Connection timed out > Sep 21 07:51:24 serverY postfix/smtpd[3270]: NOQUEUE: reject: RCPT > from smtp02.infoave.net[165.166.0.27]: 450 Server configuration > problem; from=<mdf...@lo...> to=<webmaster@**********> > proto=ESMTP helo=<SMTP02.INFOAVE.NET> > > So several messages like this were rejected. If I understand correctly SQLgrey recovered when the database came back. Did some messages get through while the database was down or each and every message were tempfailed ? Lionel |