Re: Graceful handling of DB connectivity failures

From: Naresh V <nareshov_at_gmail.com>
Date: Wed, 15 Jun 2011 14:09:51 +0530

Hi,

How can we prevent this from happening:



Jun 15 04:59:13 cf-us1 opendkim[17730]: A090869061A: no signing table
match for 'dash_at_domain.com'
Jun 15 04:59:14 cf-us1 opendkim[17730]: 428066905DB: no signing table
match for 'sharmila_at_domain.in'
Jun 15 04:59:14 cf-us1 opendkim[17730]: 428066905DB: no signature data
Jun 15 04:59:14 cf-us1 opendkim[17730]: A090869061A: no signature data
Jun 15 04:59:15 cf-us1 opendkim[17730]: error looking up ""Mejoramiso
-CorreoAutom<E1>ticoEvaluaci<F3>nProveedores"_at_outbound-us1.domain.com"
in database: ERROR: invalid byte sequence for encoding "UTF8":
0xe17469 HINT: This error can also happen if the byte sequence does
not match the encoding expected by the server, which is controlled by
"client_encoding".
Jun 15 04:59:15 cf-us1 opendkim[17730]: 36DB4690592: error reading signing table
Jun 15 04:59:15 cf-us1 opendkim[17730]: 54B2F6905DC: no signature data
Jun 15 04:59:15 cf-us1 opendkim[17730]: error looking up
"ambarish_at_domain.com" in database: another command is already in
progress
Jun 15 04:59:15 cf-us1 opendkim[17730]: 69ED4690609: error reading signing table
Jun 15 04:59:15 cf-us1 opendkim[17730]: error looking up
"delhi_at_domain.com" in database: another command is already in progress
Jun 15 04:59:15 cf-us1 opendkim[17730]: A61636905A0: error reading signing table
Jun 15 04:59:15 cf-us1 opendkim[17730]: error looking up
"liasesforas_at_domain.com" in database: another command is already in
progress

<opendkim-milter has to be restarted now>

-Naresh V.



On 18 March 2011 22:58, Naresh V <nareshov_at_gmail.com> wrote:
> On 18 March 2011 21:55, Murray S. Kucherawy <msk_at_blackops.org> wrote:
>> Can you send me your haproxy.cfg file?  It'll help me to reproduce your
>> problem if I have your exact configuration.
>
> Yes, here it is: http://dpaste.com/hold/514570/
> We use puppet to manage our configuration files and a puppet run
> occurred which updated this file in the MySQL-Maia section when this
> happened.
>
>
> Unrelated:
> I had to patch the redhat init script this way: http://dpaste.com/514585/
> for the milter to a. look at standard paths (not /local/) b.
> stop/restart properly because start() wasn't creating the pidfile
> causing to log this way:
>
>> Mar 10 07:24:11 outbound-us1 opendkim[30923]: OpenDKIM Filter: Unable to create listening socket on conn inet:8891_at_localhost
>> Mar 10 07:24:11 outbound-us1 opendkim[30923]: smfi_opensocket() failed
>> Mar 10 07:24:11 outbound-us1 opendkim[25390]: exited with status 69, restarting
>> Mar 10 07:24:11 outbound-us1 opendkim[30924]: OpenDKIM Filter: Opening listen socket on conn inet:8891_at_localhost
>> Mar 10 07:24:11 outbound-us1 opendkim[30924]: OpenDKIM Filter: Unable to bind to port inet:8891_at_localhost: Address already in use
>> Mar 10 07:24:11 outbound-us1 opendkim[30924]: OpenDKIM Filter: Unable to create listening socket on conn inet:8891_at_localhost
>> Mar 10 07:24:11 outbound-us1 opendkim[30924]: smfi_opensocket() failed
>
>
> -Naresh V.
>
Received on Wed Jun 15 2011 - 08:40:07 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:20:18 PST