Bug #17036
closedrgw: radosgw daemon core when reopen logs
0%
Description
in my environment, the radosgw daemon coredump several times within days. below is part of the radosgw daemon log :
2016-08-16 00:00:01.536750 7fc3b787a700 1 received signal: Hangup from PID: 7910 task name: killall -q -1 ceph-mon ceph-mds ceph-osd ceph-fuse radosgw UID: 0>read ofs=0 len=524288
2016-08-16 00:00:01.536773 7fc3b787a700 4 rgw realm reloader: Notification on realm, reconfiguration scheduled in 2s
2016-08-16 00:00:03.536858 7fc384814700 1 rgw realm reloader: Pausing frontends for realm update...
2016-08-16 00:00:03.536884 7fc384814700 4 rgw period pusher: paused for realm update
2016-08-16 00:00:03.536886 7fc384814700 1 rgw realm reloader: Frontends paused
.
.
.
2016-08-16 00:00:03.884577 7fc3b887c700 20 rados
2016-08-16 00:00:03.884907 7fc3b887c700 20 rados->read r=0 bl.length=352
2016-08-16 00:00:03.938092 7fc3b887c700 -1 ** Caught signal (Segmentation fault) *
in thread 7fc3b887c700 thread_name:rgw_user_st_syn
detail please see the attachment
Files
Updated by wei qiaomiao over 7 years ago
Updated by Kefu Chai over 7 years ago
- Status changed from New to Fix Under Review
Updated by Casey Bodley over 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Loïc Dachary over 7 years ago
- Copied to Backport #17064: jewel: rgw: radosgw daemon core when reopen logs added
Updated by Yehuda Sadeh over 7 years ago
- Status changed from Pending Backport to Resolved
Updated by Yehuda Sadeh over 7 years ago
- Status changed from Resolved to Pending Backport
Updated by Loïc Dachary over 7 years ago
- Status changed from Pending Backport to Resolved