Project

General

Profile

Bug #287

cmon crash when "osd tell" is given with no arguments

Added by Wido den Hollander over 13 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Monitor
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

root@node13:~# ceph osd tell
10.07.17_21:50:52.262074 mon <- [osd,tell]
10.07.17_21:50:52.295568 7fc5aaa5b710 monclient: hunting for new mon
10.07.17_21:50:52.298998 mon <- [osd,tell]
10.07.17_21:50:52.370110 7fc5aaa5b710 monclient: hunting for new mon
10.07.17_21:50:52.370631 7fc5a9756710 -- [2001:16f8:10:2::c3c3:3f9b]:0/7183 >> [2001:16f8:10:2::c3c3:2e5c]:6789/0 pipe(0x23836a0 sd=-1 pgs=0 cs=0 l=0).fault first fault
^C
root@node13:~#

Both monitors crashed when issueing this command.

When a argument is given, it goes fine:

root@node13:~# ceph osd tell 0 bench
10.07.17_21:54:29.856618 mon <- [osd,tell,0,bench]
10.07.17_21:54:29.857136 mon0 -> 'ok' (0)
root@node13:~#

Coredump, binary and log (debug mon = 20) are located on logger.ceph.widodh.nl in /srv/ceph/issues/cmon_crash_osd_tell

History

#1 Updated by Sage Weil over 13 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF