[pgpool-general: 195] Re: VM nodes marked down after snapshot

Guillaume DOUTE g.doute at linkbynet.com
Wed Jan 25 19:26:29 JST 2012


Sorry for the late reply.

You were right, I missed that option and it was set on 1. I put it to 0 and things went better. Needless to say that I felt silly.

For an odd reason, pgpool stopped logging at a certain point in time last Friday, and my problem happened again during the Weekend. So unfortunately, I still have no logs.
I will post again when I'll have something.

Thanks again for your help.

Guillaume Douté
Administrateur Activités Transversales
32 boulevard Vincent Gâche - 44000 Nantes
Tel direct : +33 (0)2 40 71 61 64
Tel : +33 (0)1 48 13 00 00 - Fax : +33 (0)1 48 13 31 21
Email : g.doute at linkbynet.com - Web : www.linkbynet.com
Astreinte : http://www.linkbynet.com/astreinte/

Avant d'imprimer cet e-mail, pensez à l'environnement.

-----Message d'origine-----
De : Guillaume Lelarge [mailto:guillaume at lelarge.info] 
Envoyé : dimanche 22 janvier 2012 15:21
À : Guillaume DOUTE
Cc : pgpool-general at pgpool.net
Objet : Re: [pgpool-general: 174] Re: VM nodes marked down after snapshot

On Tue, 2012-01-17 at 17:58 +0100, Guillaume DOUTE wrote:
> Thanks for your reply and your explanations,
> I can't understand why but I can't reproduce my problem. Things seems quite stable, fortunately. I will reply with logs when I'll encounter the problem again
> On a side question : I don't understand however why I keep getting "DEBUG" lines in my logs although I didn't launch pgpool with "-d". Logs are too verbose and get too big, so I can't enable logging all the time. Any particular reasons as to why pgpool behaves this way ?

You surely have debug_level set to a value higher than 0.

PostgreSQL Sessions #3: http://www.postgresql-sessions.org

More information about the pgpool-general mailing list