[ic] mysql having problems reconnecting on catalog reconfig

Peter peter at pajamian.dhs.org
Thu Nov 10 19:05:21 UTC 2011

On 11/11/11 07:50, Mike Heins wrote:
> Quoting Peter (peter at pajamian.dhs.org):
>> On 11/11/11 03:15, Mike Heins wrote:
>>> It's a part of the alternate DSN stuff, where you can fall back to a
>>> different database server if one is down.
>> Well it does seem to make at least some sense to me that if the first db
>> server goes down to retry the connection to that before falling back to
>> an alternate DSN or giving up entirely.
> I believe our approach is that we delegate that level of connection 
> robustness to the DBI module.
>>> But the bigger question is -- why did your connect fail originally,
>>> so that you have a connection marked as bad?
>> Yes, I agree, unfortunately I'm at a loss for how to discover this.  It
>> took enough digging for me to find this bit of code.
>> That said, I highly suspect it has something to do with either (1) newer
>> version of perl, (2) newer version of DBI or (3) newer version of
>> DBD::mysql (I don't think it's this last one because I initially
>> suspected it and went back about 10 versions and the issue was still there).
> Did you see my suggestion about emptying %DBI_connect_bad on a
> reconfiguration?

Yes, see my other response.


More information about the interchange-users mailing list