Re: [Sqlgrey-users] Periodic crashes of sqlgrey

[HaJo S. <ha...@ha...>]

Lionel,

Pls don't dig deep into the long sender name issue, it seems I have
screwed up while going through my maillogs. The "sender too long" is in
fact from the old version of sqlgrey. I have now identified that 1.3.0
crashed differently:

Nov 16 19:16:55 sun sqlgrey[18895]: Error: couldn't access domain_awl
table: FATAL:  This connection has been terminated by the administrator.
Nov 16 19:16:57 sun sqlgrey[18895]: fatal: Can't connect to DB: could
not connect to server: Connection refused at /usr/bin/sqlgrey line 336.
Nov 16 19:16:58 sun sqlgrey[18895]: warning: Database handle destroyed
without explicit disconnect at /usr/bin/sqlgrey line 336.

I'm not sure why the "administrator terminated the connection", but I'm
trying to trace this back. Is it unavoidable that sqlgrey terminates if
there's an error with the DB connection? Maybe a setting in the config
file could determine if in such a case the mail is considered either
pass or fail and a warning being issued to syslog or postmaster. The
connection could then be re-tried on the next mail-RX, no?

Sorry for the trouble,
HaJo

On Wed, 2004-11-17 at 23:12, HaJo Schatz wrote:
> On Wed, 2004-11-17 at 21:09, Lionel Bouton wrote:
> 
> > I must confess I didn't test this case after coding the protection, but 
> > I just did and it worked :
> > 
> > c:doc...@ma...
> > is put in the connect table as :
> > 'c:documentsandsettingsadministratordesktopgevaliagevaliafroms.tx' | 'mail.eppele.co.kr'
> > (notice the missing 't')
> 
> I suspect the sender contains "illegal" characters such as the
> backslash. Did you consider this? I'm wondering what an <INSERT ...
> ("C:\DocumentsAndSettings...")..> would do.
> 
> > 
> > My best guess is that you have an old (1.1.3 wasn't protected against this) sqlgrey release in your $PATH.
> Nack. I only have one version here which is (well, says through "sqlgrey
> --version") 1.3.0. I had the crash a few times with 1.1.3 upon which I
> upgraded to 1.3.0. There's a remote possibility that I didn't restart
> sqlgrey after upgrading, but I strongly doubt it, as I have a log entry
> (sqlgrey starting) which is younger than the mtime of the (new)
> /etc/sqlgrey/ directory.
> 
> Anyway, I'm sure that now the correct version is running. I'll observe
> it and report back if it crashes again.
> 
> HaJo
-- 
HaJo Schatz <ha...@ha...>
http://www.HaJo.Net

PGP-Key:  http://www.hajo.net/hajonet/keys/pgpkey_hajo.txt