Re: [Sqlgrey-users] sqlgrey fails when configured with multiple machines

[Dan F. <da...@ha...>]

On 2014-07-18T00:30:38 CEST, Alex wrote:
> Then, about seven minutes into my testing, sqlgrey quit and died on
> all three systems:
>
> Jul 17 18:02:22 mail02 sqlgrey: fatal: setconfig error at
> /usr/sbin/sqlgrey line 195.
> Jul 17 18:02:36 mail03 sqlgrey: fatal: setconfig error at
> /usr/sbin/sqlgrey line 195.
> Jul 17 18:03:03 mail01 sqlgrey: fatal: setconfig error at
> /usr/sbin/sqlgrey line 195.
>

So this is very interesting and useful log information. Thats a bug, 
right there.. I think i know what this is. Ill make a patch and get 
back to you.

> > In this case 100s.
>
> I still have mine set for 1s, but I'd like an "indefinite" option for
No you have your "sqlgrey -> mysql" timeout at 1s. This value is for 
"postfix -> sqlgrey".

> I don't know if my 7m test hit some magic limit or something else
I think its the db-cleanup that tries to run. It saves a timestamp to 
the db and apparently that action isn't fault tolerant.

> So how do we explain it continuing beyond 100s when you've explicitly
> defined the timeout period to be 100s?

Because the defined timeout period is for Postfix. It tells postfix how 
long it will wait for a policy-daemon (like sqlgrey). "tester.pl" isnt 
using Postfix, it is connecting to sqlgrey directly and postfix timeout 
value is not in play at all.
This just means, that if it was Postfix that had made the connection to 
sqlgrey (and not tester.pl), it would have given up after 100 seconds 
and displayed "Server configuration problem".