Actions
Bug #6820
closedBad commandline usage crashed my monitor
Status:
Resolved
Priority:
Normal
Assignee:
Joao Eduardo Luis
Category:
Monitor
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
dumpling, emperor
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
I was looking to dump my CRUSH map without JSON syntax and I used the -f command to specify a format.
ceph osd crush dump -f plain
Thereafter, my monitor crashed and I wasn't able to restart it. Error is:
2013-11-20 15:45:50.038162 7f6d7c10f700 0 -- :/1024054 >> 192.168.0.138:6789/0 pipe(0x7f6d78026400 sd=8 :0 s=1 pgs=0 cs=0 l=1 c=0x7f6d78026660).fault
Updated by Joao Eduardo Luis over 10 years ago
John, that's the client being unable to contact the monitor (most likely because the monitor indeed crashed). We'd need the crash dump/stack trace from your monitor log. Or the whole log, that'd be preferable even.
Updated by Joao Eduardo Luis over 10 years ago
- Category changed from ceph cli to Monitor
- Status changed from New to Pending Backport
Updated by Joao Eduardo Luis about 10 years ago
- Backport set to dumpling, emperor
Updated by Sage Weil about 10 years ago
- Status changed from Pending Backport to Resolved
Actions