From: Alex <mys...@gm...> - 2014-07-22 22:22:59
|
Hi, On Tue, Jul 22, 2014 at 6:16 PM, Alex <mys...@gm...> wrote: > Hi, > > On Mon, Jul 21, 2014 at 8:41 PM, Alex <mys...@gm...> wrote: > >> Hi, >> >> >> On Fri, Jul 18, 2014 at 3:12 AM, Dan Faerch <da...@ha...> wrote: >> > >> > 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. >> >> Thanks very much. I've applied the patch. I'll be watching it over the >> next few days, and hope to be doing some more testing with the changes soon. >> > > Found out today when the link between mail02 (the db server) and mail03 > was broken that the patch is not fixing the problem. Did you test this > locally before? > I may have made a mistake. Would you confirm for me that this change is made in the setconfig() function? The version I have has a few patches from fedora, and this may have affected my patch. Thanks, Alex |