Bug #14405
closedceph-mon process crash when wrong message type in ceph.conf
0%
Description
- I set a wrong message type in my ceph.conf
cat /etc/ceph/ceph.conf
[global]
fsid = b4c0f945-f80a-4092-b059-d7b7b8fbb4ca
mon_initial_members = cas-meta3, ubuntu, ubuntu-meta2
mon_host = 172.16.53.19,172.16.53.52,172.16.53.53
ms_type = caibo
- then I try to start my ceph monitor, but the program crash
root@ubuntu:/deb-test/test/DEBIAN# ceph-mon -i ubuntu
2016-01-06 12:22:08.464863 7f956b0ab8c0 -1 unrecognized ms_type 'caibo'- Caught signal (Segmentation fault)
in thread 7f956b0ab8c0
ceph version 0.94.5-V100R001B01D007 (6a8648811103835d57927149b419b0e037cc53c6)
1: ceph-mon() [0x9aec6a]
2: (()+0x10340) [0x7f956a1aa340]
3: (main()+0x1c28) [0x577008]
4: (__libc_start_main()+0xf5) [0x7f9568634ec5]
5: ceph-mon() [0x5993f7]
2016-01-06 12:22:08.466383 7f956b0ab8c0 -1 Caught signal (Segmentation fault) *
in thread 7f956b0ab8c0ceph version 0.94.5-V100R001B01D007 (6a8648811103835d57927149b419b0e037cc53c6)
1: ceph-mon() [0x9aec6a]
2: (()+0x10340) [0x7f956a1aa340]
3: (main()+0x1c28) [0x577008]
4: (__libc_start_main()+0xf5) [0x7f9568634ec5]
5: ceph-mon() [0x5993f7]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.-1> 2016-01-06 12:22:08.464863 7f956b0ab8c0 -1 unrecognized ms_type 'caibo'
0> 2016-01-06 12:22:08.466383 7f956b0ab8c0 -1 ** Caught signal (Segmentation fault) *
in thread 7f956b0ab8c0ceph version 0.94.5-V100R001B01D007 (6a8648811103835d57927149b419b0e037cc53c6)
1: ceph-mon() [0x9aec6a]
2: (()+0x10340) [0x7f956a1aa340]
3: (main()+0x1c28) [0x577008]
4: (__libc_start_main()+0xf5) [0x7f9568634ec5]
5: ceph-mon() [0x5993f7]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
- Caught signal (Segmentation fault)
[24581]: (33) Numerical argument out of domain
Updated by bo cai about 8 years ago
I have pull a git request for this:
Updated by bo cai about 8 years ago
Updated by Kefu Chai about 8 years ago
- Status changed from New to Fix Under Review
Updated by Sage Weil about 8 years ago
- Status changed from Fix Under Review to Resolved