Sadly we don't have a core dump when the crash happened, so that we are not
able to dump the registers..
The latest status - we changed the rgw thread number from 600 to 300, and we
haven't seen the same crash since, but still it is hard to tell if that is
related and how it is related..
- Original Message -
From: GuangYang yguan...@outlook.com
To: Yehuda Sadeh-Weinraub yeh...@redhat.com
Cc: ceph-de...@vger.kernel.org, ceph-users@lists.ceph.com
Sent: Wednesday, June 24, 2015 2:12:23 PM
Subject: RE: radosgw crash within libfcgi
Also, looking at the code, I see an extra call to FCGX_Finish_r():
diff --git a/src/rgw/rgw_main.cc b/src/rgw/rgw_main.cc
index 9a8aa5f..0aa7ded 100644
--- a/src/rgw/rgw_main.cc
+++ b/src/rgw/rgw_main.cc
@@ -669,8 +669,6 @@ void RGWFCGXProcess::handle_request(RGWRequest *r)
dout(20)
Thanks Yehuda for the response.
We already patched libfcgi to use poll instead of select to overcome the
limitation.
Thanks,
Guang
Date: Wed, 24 Jun 2015 14:40:25 -0400
From: yeh...@redhat.com
To: yguan...@outlook.com
CC:
- Original Message -
From: GuangYang yguan...@outlook.com
To: ceph-de...@vger.kernel.org, ceph-users@lists.ceph.com, yeh...@redhat.com
Sent: Wednesday, June 24, 2015 10:09:58 AM
Subject: radosgw crash within libfcgi
Hello Cephers,
Recently we have several radosgw daemon crashes
Hello Cephers,
Recently we have several radosgw daemon crashes with the same following kernel
log:
Jun 23 14:17:38 xxx kernel: radosgw[68180]: segfault at f0 ip 7ffa069996f2
sp 7ff55c432710 error 6 in libfcgi.so.0.0.0[7ffa06995000+a000] in
libfcgi.so.0.0.0[7ffa06995000+a000]
Looking
