Project

General

Profile

Bug #11140

/etc/init.d/radosgw restart does not work correctly

Added by Dmitry Yatsushkevich over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
03/17/2015
Due date:
% Done:

0%

Source:
other
Tags:
Backport:
firefly,hammer
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:

Description

`/etc/init.d/radosgw restart` does not guarantee proper restarting of the service.
radosgw has two configuration options:
- rgw_init_timeout (default value 300)
- rgw_exit_timeout_secs (default value 120)
First option - how long waiting for full initialization of the service, second one - how long waiting for correct shutdown.
If timeout is reached, service exits with exit code 1
Shutdown can take time because it is waiting until all RGWFrontends stop.
As a result `/etc/init.d/radosgw restart` will be a cause that for time will be two instances of radosgw:
first - waiting for stop
- second - waiting for start or started incorrectly (e.g. without admin socket)

logs linked to this situation:
2015-02-26 23:51:32.363877 7f2f62ffd700 1 handle_sigterm set alarm for 120
2015-02-26 23:51:32.363921 7f2fe827d780 -1 shutting down
2015-02-26 23:51:32.364260 7f2f62ffd700 1 handle_sigterm
2015-02-26 23:51:32.364359 7f2f627fc700 0 ERROR: FCGX_Accept_r returned -4
2015-02-26 23:51:32.446801 7f0937b93780 0 ceph version 0.80.7 (6c0127fcb58008793d3c8b62d925bc91963672a3), process radosgw, pid 12221
2015-02-26 23:51:32.446833 7f0937b93780 -1 WARNING: libcurl doesn't support curl_multi_wait()
2015-02-26 23:51:32.446840 7f0937b93780 -1 WARNING: cross zone / region transfer performance may be affected
2015-02-26 23:51:32.488104 7f0937b93780 -1 asok(0x209d060) AdminSocketConfigObs::init: failed: AdminSocket::bind_and_listen: failed to bind the UNIX domain socket to '/var/run/ceph/ceph-client.radosgw.gateway.asok': (17) File exists
2015-02-26 23:53:18.119360 7f2fe827d780 1 final shutdown
2015-02-26 23:56:32.448035 7f092f79d700 -1 Initialization timeout, failed to initialize


Related issues

Copied to rgw - Backport #12982: /etc/init.d/radosgw restart does not work correctly Resolved 03/17/2015
Copied to rgw - Backport #13343: /etc/init.d/radosgw restart does not work correctly Resolved 03/17/2015

Associated revisions

Revision 1cca0c1e (diff)
Added by Dmitry Yatsushkevich over 3 years ago

rgw: init script waits until the radosgw stops

Fixes: #11140
Init script waits in stop action until the radowgw daemons stop.

Signed-off-by: Dmitry Yatsushkevich <>

Revision 3be204f6 (diff)
Added by Dmitry Yatsushkevich about 3 years ago

rgw: init script waits until the radosgw stops

Fixes: #11140
Init script waits in stop action until the radowgw daemons stop.

Signed-off-by: Dmitry Yatsushkevich <>
(cherry picked from commit 1cca0c1e91a1e18f82f4d22855e96b2fc947f5ea)

Revision eb001d3a (diff)
Added by Dmitry Yatsushkevich about 3 years ago

rgw: init script waits until the radosgw stops

Fixes: #11140
Init script waits in stop action until the radowgw daemons stop.

Signed-off-by: Dmitry Yatsushkevich <>
(cherry picked from commit 1cca0c1e91a1e18f82f4d22855e96b2fc947f5ea)

History

#2 Updated by Loic Dachary over 3 years ago

  • Status changed from New to In Progress

#3 Updated by Loic Dachary about 3 years ago

  • Status changed from In Progress to Pending Backport
  • Regression set to No

#4 Updated by Loic Dachary about 3 years ago

  • Backport set to firefly

#5 Updated by Loic Dachary about 3 years ago

  • Backport changed from firefly to firefly,hammer

#6 Updated by Loic Dachary about 3 years ago

  • Status changed from Pending Backport to Resolved

#7 Updated by Loic Dachary about 3 years ago

  • Status changed from Resolved to Pending Backport

#8 Updated by Loic Dachary about 3 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF