[op5-users] Réf. : Re: merlind crash after loosing mysql connection

[nicolas.raspail at bnpparibas.com]

Bonjour


Cordialement

Nicolas Raspail

op5-users-bounces at lists.op5.com wrote on 31/08/2009 10:38:27:

> nicolas.raspail at bnpparibas.com wrote:
> > Hi
> > 
> > Merlind (version 0.6.2-beta5) crash if it loose the connection with 
the 
> > MySQL. My sql server is running inside a cluster, and for some 
reasons,  I 
> > have switched it to another node. To be sure that everything is okay, 
I 
> > have checked the log of merlin. As expected, I see the following 
message :
> > 
> > [1251471412] 6: dbi_conn_query_null(): Failed to run [SELECT 
host_name, 
> > current_state, state_type FROM merlindb.host ORDER BY host_name]: 
2006: 
> > MySQL server has gone away
> > 
> > But what is not expected is the fact that no more merlind process is 
> > running.
> 
> Do you mean that no merlind process is running, or that only one is?

No merlind process is running and I receive an alert from my cluster 
software

> 
> > I have see the same behaviour with the beta2 as reported in a 
> > previous email and Andreas answered :
> > "Hmm. It should try to reconnect at that point instead. Not sure if it 
did 
> > that in beta2."
> > 
> 
> It should, although it log that it does. What version of libdbi are you
> using? There has been some changes to the error handling in recent 
versions
> of libdbi, so perhaps your version no longer returns DBI_ERROR_NOCONN 
when
> it notices the database connection has died. I'll run some tests and add
> some logging and make sure it at least tries to reconnect.
> 

I'm running libdbi-0.8.1-2.1 on a RHEL 5.3 x86_64 system

> > It seems that even with the beta5, merlind is not trying to reconnect
> > 
> 
> Well, the code in sql.c hasn't changed between beta5 and beta10, so it
> wouldn't help to upgrade for this particular problem.
> 
> I'll get back to you in an hour when I've run those tests.

Ok, thanks you

Regards

Nicolas




This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 
Do not print this message unless it is necessary,
consider the environment.

                ---------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.
N'imprimez ce message que si necessaire,
pensez a l'environnement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.op5.com/pipermail/op5-users/attachments/20090831/d8e64929/attachment.html