De: "Andy Mroczkowski" <address@hidden>
Para: address@hidden
Enviadas: Domingo, 1 de Abril de 2012 22:24:06
Assunto: [Fab-user] trouble with pgbouncer - SIGINT?
Greetings.
sudo("service pgbouncer restart")
The output looks ok:
address@hidden sudo: service pgbouncer restart
address@hidden out: * Restarting pgbouncer pgbouncer
address@hidden out: ...done.
However, after fabric disconnects, pgbouncer is not running. It's log file reports:
2012-04-02 00:53:56.205 22454 LOG File descriptor limit: 1024 (H:4096), max_client_conn: 100, max fds possible: 110
2012-04-02 00:53:56.207 22456 LOG listening on 127.0.0.1:6432
2012-04-02 00:53:56.208 22456 LOG listening on unix:/var/run/postgresql/.s.PGSQL.6432
2012-04-02 00:53:56.208 22456 LOG process up: pgbouncer 1.4.2, libevent 2.0.12-stable (epoll), adns: evdns2
2012-04-02 00:54:03.904 22456 LOG Got SIGINT, shutting down
2012-04-02 00:54:04.233 22456 LOG server connections dropped, exiting
It seems like the service is starting, and then exiting almost immediately due to receiving a SIGINT.
If I run the command manually from my local shell (without fabric) it works fine. No immediate shutdown due to SIGINT
ssh -i key.pem address@hidden 'sudo service pgbouncer restart'
I can only assume that somehow fabric is sending SIGINT (directly or indirectly), but I don't know a lot the fabric execution environment or UNIX signals/daemons in general.
Any ideas?
Thanks,
- Andy
_______________________________________________
Fab-user mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/fab-user