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

[Alex <mys...@gm...>]

Hi,

On Sun, Jul 6, 2014 at 7:07 AM, Dan Faerch <da...@ha...> wrote:
>
> > It's only based on the fact that there is no stalling or any delays here
> > - it happens immediately when sqlgrey isn't running at all.
>
> You are now talking about how Postfix reacts to a missing policy-daemon
> (sqlgrey is a postfix policy-daemon).
> As this is not something I or sqlgrey can influence, this is not what im
> talking about at all.
>
> I am ONLY talking about the issue you specified in your original mail,
> which was (slightly summarized):
>  - You had "..configured using the DBCLUSTER.."
>  - and when "..one machine goes down, all three fail.."
>  - with error "..4.3.5 Server configuration problem.."
>
> And as such, i believe the issue was a mysql connection attempt that took
> too long. This is now solved by setting timeout to 1 second.

Okay, I didn't understand that the inability to reach mysql because the
server was down would be considered a timeout.

I was also thinking about the more general case and wasn't explaining
myself very well. While I'm concerned about sqlgrey itself dying (and now
understand it's a misplaced concern), I wanted to be sure a complete loss
of the server itself was also solved with the mysql timeout parameter
you've mentioned.

I now only wish there was a way for postfix to fail silently and pass the
mail on, instead of returning any error, temporary or not, to the user.

I have a lot to read an re-read (especially about mysql replication). Very
much appreciate your help.

Thanks again for everything.
Alex