On 2013-07-25 15:55, Joao Eduardo Luis wrote:
On 07/25/2013 02:39 PM, pe...@2force.nl wrote:
On 2013-07-25 15:21, Joao Eduardo Luis wrote:
On 07/25/2013 11:20 AM, pe...@2force.nl wrote:
On 2013-07-25 12:08, Wido den Hollander wrote:
On 07/25/2013 12:01 PM, pe...@2force.nl wrote:
On 2013-07-2
On 07/25/2013 02:39 PM, pe...@2force.nl wrote:
On 2013-07-25 15:21, Joao Eduardo Luis wrote:
On 07/25/2013 11:20 AM, pe...@2force.nl wrote:
On 2013-07-25 12:08, Wido den Hollander wrote:
On 07/25/2013 12:01 PM, pe...@2force.nl wrote:
On 2013-07-25 11:52, Wido den Hollander wrote:
On 07/25/20
On 2013-07-25 15:21, Joao Eduardo Luis wrote:
On 07/25/2013 11:20 AM, pe...@2force.nl wrote:
On 2013-07-25 12:08, Wido den Hollander wrote:
On 07/25/2013 12:01 PM, pe...@2force.nl wrote:
On 2013-07-25 11:52, Wido den Hollander wrote:
On 07/25/2013 11:46 AM, pe...@2force.nl wrote:
Any news on
On 07/25/2013 11:20 AM, pe...@2force.nl wrote:
On 2013-07-25 12:08, Wido den Hollander wrote:
On 07/25/2013 12:01 PM, pe...@2force.nl wrote:
On 2013-07-25 11:52, Wido den Hollander wrote:
On 07/25/2013 11:46 AM, pe...@2force.nl wrote:
Any news on this? I'm not sure if you guys received the li
On 2013-07-25 12:08, Wido den Hollander wrote:
On 07/25/2013 12:01 PM, pe...@2force.nl wrote:
On 2013-07-25 11:52, Wido den Hollander wrote:
On 07/25/2013 11:46 AM, pe...@2force.nl wrote:
Any news on this? I'm not sure if you guys received the link to the
log
and monitor files. One monitor and
On 07/25/2013 12:01 PM, pe...@2force.nl wrote:
On 2013-07-25 11:52, Wido den Hollander wrote:
On 07/25/2013 11:46 AM, pe...@2force.nl wrote:
Any news on this? I'm not sure if you guys received the link to the log
and monitor files. One monitor and osd is still crashing with the error
below.
I
On 2013-07-25 11:52, Wido den Hollander wrote:
On 07/25/2013 11:46 AM, pe...@2force.nl wrote:
Any news on this? I'm not sure if you guys received the link to the
log
and monitor files. One monitor and osd is still crashing with the
error
below.
I think you are seeing this issue: http://track
On 07/25/2013 11:46 AM, pe...@2force.nl wrote:
Any news on this? I'm not sure if you guys received the link to the log
and monitor files. One monitor and osd is still crashing with the error
below.
I think you are seeing this issue: http://tracker.ceph.com/issues/5737
You can try with new pack
Any news on this? I'm not sure if you guys received the link to the log
and monitor files. One monitor and osd is still crashing with the error
below.
On 2013-07-24 09:57, pe...@2force.nl wrote:
Hi Sage,
I just had a 0.61.6 monitor crash and one osd. The mon and all osds
restarted just fine a
On 24 Jul 2013, at 05:47, Sage Weil wrote:
> There was a problem with the monitor daemons in v0.61.5 that would prevent
> them from restarting after some period of time. This release fixes the
> bug and works around the issue to allow affected monitors to restart.
> All v0.61.5 users are str
Hi Sage,
I just had a 0.61.6 monitor crash and one osd. The mon and all osds
restarted just fine after the update but it decided to crash after 15
minutes orso. See a snippet of the logfile below. I have you sent a link
to the logfiles and monitor store. It seems the bug hasn't been fully
fix
There was a problem with the monitor daemons in v0.61.5 that would prevent
them from restarting after some period of time. This release fixes the
bug and works around the issue to allow affected monitors to restart.
All v0.61.5 users are strongly recommended to upgrade.
Thanks everyone who he
12 matches
Mail list logo
