On 02/16/2014 09:22 PM, Sage Weil wrote:
Hi Wido,
On Sun, 16 Feb 2014, Wido den Hollander wrote:
On 02/16/2014 06:49 PM, Gregory Farnum wrote:
Did you maybe upgrade that box to v0.67.6? This sounds like one of the
bugs Sage mentioned in it.
No, I checked it again. Version is: ceph version 0.
Hi Wido,
On Sun, 16 Feb 2014, Wido den Hollander wrote:
> On 02/16/2014 06:49 PM, Gregory Farnum wrote:
> > Did you maybe upgrade that box to v0.67.6? This sounds like one of the
> > bugs Sage mentioned in it.
>
> No, I checked it again. Version is: ceph version 0.67.5
> (a60ac9194718083a4b6a225f
On 02/16/2014 06:49 PM, Gregory Farnum wrote:
Did you maybe upgrade that box to v0.67.6? This sounds like one of the
bugs Sage mentioned in it.
No, I checked it again. Version is: ceph version 0.67.5
(a60ac9194718083a4b6a225fc17cad6096c69bd1)
All machines in the cluster are on that version.
Did you maybe upgrade that box to v0.67.6? This sounds like one of the
bugs Sage mentioned in it.
-Greg
Software Engineer #42 @ http://inktank.com | http://ceph.com
On Sun, Feb 16, 2014 at 4:23 AM, Wido den Hollander wrote:
> Hi,
>
> Yesterday I got a notification that a RGW setup was having iss
Hi,
Yesterday I got a notification that a RGW setup was having issues with
objects suddenly giving errors (403 and 404) when trying to access them.
I started digging and after cranking up the logs with 'debug rados' and
'debug rgw' set to 20 I found what caused RGW to throw a error:
librado
