Hi Yehuda,
I just pushed a fix to wip-6161, can you verify that it fixes the issue
for you?
The fix wip-6161 branch seem to fix the problem for me. I was able to
re-enable the cache and have radosgw start (and seemingly work
properly).
Cheers,
Sylvain
--
To unsubscribe from this list:
Hi,
I just pushed a fix to wip-6161, can you verify that it fixes the issue
for you?
Thanks, I'll give it a shot on monday, I'm out of the office at the moment.
Cheers,
Sylvain
--
To unsubscribe from this list: send the line unsubscribe ceph-devel in
the body of a message to
Hi,
I just updated our test cluster to 0.67.2+ (latest dumpling branch) (
from 0.61.x ) and radosgw refuses to start.
2013-08-29 11:46:34.915552 7ffccbc3d780 0 ceph version
0.67.2-19-gc81bc5b (c81bc5b59dda37f54c02039ca3d5aada64076624), process
lt-radosgw, pid 30404
2013-08-29 11:46:34.915598
I reverted commit a4cca31c82bf0e84272e01eb1b3188dfdb5b5615 and then I got :
2013-08-29 13:32:44.430574 7f55402a7780 0 ceph version
0.67.2-19-gc81bc5b (c81bc5b59dda37f54c02039ca3d5aada64076624), process
lt-radosgw, pid 30786
2013-08-29 13:32:44.430608 7f55402a7780 -1 WARNING: libcurl doesn't
I tried going back to a src/rgw/ directory as it is in the 0.67.2
release, but didn't start either.
(failed to init storage).
Finally I disabled the cache for now and it seem to have started properly.
On Thu, Aug 29, 2013 at 1:50 PM, Sylvain Munaut
s.mun...@whatever-company.com wrote:
I
What's commit c81bc5b59dda37f54c02039ca3d5aada64076624? I don't see it
on the ceph github repository.
On Thu, Aug 29, 2013 at 5:59 AM, Sylvain Munaut
s.mun...@whatever-company.com wrote:
I tried going back to a src/rgw/ directory as it is in the 0.67.2
release, but didn't start either.
It's a local commit. We have a few patches that implement features we
need but that weren't accepted upstream. (and yes, I checked they had
no influence on the issue at hand).
The latest commit from the ceph repo is 39adc0195e6016ce36828885515be1bffbc10ae1
Cheers,
Sylvain
On Thu, Aug 29,
Just pushed a f
On Thu, Aug 29, 2013 at 7:24 AM, Sylvain Munaut
s.mun...@whatever-company.com wrote:
It's a local commit. We have a few patches that implement features we
need but that weren't accepted upstream. (and yes, I checked they had
no influence on the issue at hand).
The latest
Sorry for the early send, my keyboard is a bit of a whack right now. I
just pushed a fix to wip-6161, can you verify that it fixes the issue
for you?
Thanks,
Yehuda
On Thu, Aug 29, 2013 at 1:06 PM, Yehuda Sadeh yeh...@inktank.com wrote:
Just pushed a f
On Thu, Aug 29, 2013 at 7:24 AM, Sylvain
