Neste ultimo teste, instalou via apt ? É Debian ? Em 19 de abril de 2012 16:40, Tulio Santos <[email protected]> escreveu: > Não cheguei a dar um kill no processo dele antes de enviar o log.. > mas depois fiz o teste.. e o problema persitiu.. > > dessa vez vi que quando solicito o Status após a parada do serviço, este me > retorna failed... > > # pgpool -m smart stop > 2012-04-19 16:31:27 ERROR: pid 6469: could not read pid file > # service pgpool2 start > Starting pgpool-II: pgpool. > # pgpool -m smart stop > stop request sent to pgpool. waiting for termination...done. > # service pgpool2 status > pgpool-II is not running. ... failed! > > este é o log quando solicito a parada do serviço.. > (limpei a parte que carrega configurações pra nao encher muito) > ... > 2012-04-19 16:24:21 LOG: pid 6313: pgpool-II successfully started. version > 3.1.2 (hatsuiboshi) > 2012-04-19 16:24:21 DEBUG: pid 6317: I am 6317 > 2012-04-19 16:24:21 DEBUG: pid 6317: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6316: I am 6316 > 2012-04-19 16:24:21 DEBUG: pid 6316: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6318: I am 6318 > 2012-04-19 16:24:21 DEBUG: pid 6318: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6319: I am 6319 > 2012-04-19 16:24:21 DEBUG: pid 6319: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6315: I am 6315 > 2012-04-19 16:24:21 DEBUG: pid 6315: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6320: I am 6320 > 2012-04-19 16:24:21 DEBUG: pid 6320: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6321: I am 6321 > 2012-04-19 16:24:21 DEBUG: pid 6321: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6322: I am 6322 > 2012-04-19 16:24:21 DEBUG: pid 6322: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6323: I am 6323 > 2012-04-19 16:24:21 DEBUG: pid 6323: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6324: I am 6324 > 2012-04-19 16:24:21 DEBUG: pid 6324: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6325: I am 6325 > 2012-04-19 16:24:21 DEBUG: pid 6325: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6326: I am 6326 > 2012-04-19 16:24:21 DEBUG: pid 6326: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6327: I am 6327 > 2012-04-19 16:24:21 DEBUG: pid 6327: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6328: I am 6328 > 2012-04-19 16:24:21 DEBUG: pid 6328: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6329: I am 6329 > 2012-04-19 16:24:21 DEBUG: pid 6329: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6330: I am 6330 > 2012-04-19 16:24:21 DEBUG: pid 6330: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6314: I am 6314 > 2012-04-19 16:24:21 DEBUG: pid 6314: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6331: I am 6331 > 2012-04-19 16:24:21 DEBUG: pid 6331: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6332: I am 6332 > 2012-04-19 16:24:21 DEBUG: pid 6332: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6333: I am 6333 > 2012-04-19 16:24:21 DEBUG: pid 6333: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6334: I am 6334 > 2012-04-19 16:24:21 DEBUG: pid 6334: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6335: I am 6335 > 2012-04-19 16:24:21 DEBUG: pid 6335: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6336: I am 6336 > 2012-04-19 16:24:21 DEBUG: pid 6336: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6337: I am 6337 > 2012-04-19 16:24:21 DEBUG: pid 6337: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6338: I am 6338 > 2012-04-19 16:24:21 DEBUG: pid 6338: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6339: I am 6339 > 2012-04-19 16:24:21 DEBUG: pid 6339: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6340: I am 6340 > 2012-04-19 16:24:21 DEBUG: pid 6340: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6341: I am 6341 > 2012-04-19 16:24:21 DEBUG: pid 6341: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6342: I am 6342 > 2012-04-19 16:24:21 DEBUG: pid 6342: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6343: I am 6343 > 2012-04-19 16:24:21 DEBUG: pid 6343: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6344: I am 6344 > 2012-04-19 16:24:21 DEBUG: pid 6344: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6345: I am 6345 > 2012-04-19 16:24:21 DEBUG: pid 6345: pool_initialize_private_backend_status: > initialize backend status > 2012-04-19 16:24:21 DEBUG: pid 6313: find_primary_node: not in streaming > replication mode > 2012-04-19 16:24:21 DEBUG: pid 6347: I am 6347 > 2012-04-19 16:24:21 DEBUG: pid 6347: pool_initialize_private_backend_status: > initialize backend status > ^C2012-04-19 16:24:22 DEBUG: pid 6345: child received shutdown request > signal 2 > 2012-04-19 16:24:22 DEBUG: pid 6344: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6343: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6342: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6341: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6340: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6339: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6338: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6337: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6336: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6335: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6334: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6333: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6332: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6331: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6330: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6329: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6328: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6327: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6326: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6325: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6324: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6323: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6322: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6321: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6320: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6319: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6318: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6317: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6316: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6315: child received shutdown request signal > 2 > 2012-04-19 16:24:22 DEBUG: pid 6314: child received shutdown request signal > 2 > 2012-04-19 16:24:22 LOG: pid 6313: received fast shutdown request > 2012-04-19 16:24:22 DEBUG: pid 6313: shmem_exit(0) > > a instalação foi feita via package.. > não havia a versão 3 no "apt-get".. > recomenda que faça de alguma outra forma? > > Att, > Tulio > > ________________________________ > De: Flavio Henrique Araque Gurgel <[email protected]> > Para: [email protected] > Enviadas: Quinta-feira, 19 de Abril de 2012 13:48 > > Assunto: Re: [pgbr-geral] Failover - Pgpool II + Hot Standby + Stream > Replication > > > Em 19-04-2012 11:57, Tulio Santos escreveu: >> Após alterar isto, quando tento conectar via pgpool não há retorno.. >> $ postgres@server1:~$ psql -p 5433 -h 192.168.1.82 >> $ psql: postgres@server1:~$ >> >> Segue o log do pgpool.. >> ... > >> 2012-04-19 11:44:19 DEBUG: pid 2622: key: debug_level >> 2012-04-19 11:44:19 DEBUG: pid 2622: value: 0 kind: 2 > > Parece que o pgpool só leu o arquivo de configurações e parou. > >> pid file found. is another pgpool(2554) is running? >> esta ultima linha o log.. perguntado se tenho outro pgpool rodando.. é >> comum? > > Você matou o processo pgpool com kill? > Remova o arquivo pid e veja se ele sobe corretamente. > > []s > > Flavio Henrique A. Gurgel > Consultor e Instrutor 4Linux > Tel: +55-11-2125-4747 > www.4linux.com.br > > _______________________________________________ > pgbr-geral mailing list > [email protected] > https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral > > > _______________________________________________ > pgbr-geral mailing list > [email protected] > https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral >
-- William Felipe Welter ------------------------------ Consultor em Tecnologias Livres [email protected] www.4linux.com.br _______________________________________________ pgbr-geral mailing list [email protected] https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
