Comment 1 for bug 1607177

Revision history for this message
Rabi Mishra (rabi) wrote :

It seems the stale childs are removed after a minute or so.

SIGHUP Received at 2016-07-28 03:48:33.595[1]

2016-07-28 03:48:33.595 6673 ERROR heat.common.wsgi [-] SIGHUP received
2016-07-28 03:48:33.599 6673 INFO heat.common.wsgi [-] Starting 3 workers
2016-07-28 03:48:33.602 6673 INFO heat.common.wsgi [-] Started child 24039
2016-07-28 03:48:33.604 24039 INFO eventlet.wsgi.server [-] (24039) wsgi starting up on http://0.0.0.0:8004
2016-07-28 03:48:33.607 6673 INFO heat.common.wsgi [-] Started child 24040
2016-07-28 03:48:33.609 24040 INFO eventlet.wsgi.server [-] (24040) wsgi starting up on http://0.0.0.0:8004
2016-07-28 03:48:33.611 6673 INFO heat.common.wsgi [-] Started child 24041
2016-07-28 03:48:33.614 24041 INFO eventlet.wsgi.server [-] (24041) wsgi starting up on http://0.0.0.0:8004

Stale Childs removed: 03:49:07:325[1]

2016-07-28 03:49:07.304 6673 INFO heat.common.wsgi [-] Removed stale child 7100
2016-07-28 03:49:07.325 6673 INFO heat.common.wsgi [-] Removed stale child 7099

After almost 35 seconds. I would post a patch to increase the self.conf.sighup_timeout

[1] http://logs.openstack.org/11/347111/3/check/gate-heat-dsvm-functional-orig-mysql-lbaasv2/81f7fb6/logs/screen-h-api.txt.gz#_2016-07-28_03_49_07_304