Cinder api service outputs error messages when SIGHUP signal is sent
Bug #1337796 reported by
Abhishek Kekane
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Ankit Agrawal |
Bug Description
When SIGHUP signal is send to cinder-api service, it stops all the cinder-api processes and while restarting the cinder-api processes, it throws AttributeError: 'WSGIService' object has no attribute 'reset'.
Steps to reproduce:
1. Run cinder-api service as daemon.
2. Send SIGHUP signal to cinder-api service
kill -1 <parent_
Changed in cinder: | |
assignee: | nobody → Abhishek Kekane (abhishek-kekane) |
Changed in cinder: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
After adding reset method in WSGIService class.
When SIGHUP signal is sent to cinder-api service, it stops all the cinder-api processes and while restarting the cinder-api processes, it throws error: [Errno 9] Bad file descriptor.
Traceback (most recent call last): python2. 7/dist- packages/ eventlet/ hubs/hub. py", line 346, in fire_timers python2. 7/dist- packages/ eventlet/ hubs/timer. py", line 56, in __call__cb(*args, **kw) python2. 7/dist- packages/ eventlet/ greenthread. py", line 194, in main cinder/ cinder/ openstack/ common/ service. py", line 483, in run_service cinder/ cinder/ service. py", line 336, in start server. start() cinder/ cinder/ wsgi.py" , line 229, in start getsockname( )[0:2] python2. 7/socket. py", line 224, in meth self._sock, name)(* args) python2. 7/socket. py", line 170, in _dummy
File "/usr/lib/
timer()
File "/usr/lib/
File "/usr/lib/
result = function(*args, **kwargs)
File "/opt/stack/
service.start()
File "/opt/stack/
self.
File "/opt/stack/
(self._host, self._port) = self._socket.
File "/usr/lib/
return getattr(
File "/usr/lib/
raise error(EBADF, 'Bad file descriptor')
error: [Errno 9] Bad file descriptor