Project

General

Profile

Actions

Bug #15579

closed

"mon" is enabled but not started after reboot

Added by Shinobu Kinjo almost 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

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

Description

[ceph@octopus conf]$ sudo systemctl is-enabled
enabled

[ceph@octopus conf]$ sudo systemctl status
- Ceph cluster monitor daemon
Loaded: loaded (/usr/lib/systemd/system/ceph-mon@.service; enabled; vendor preset: disabled)
Active: inactive (dead)

[ceph@octopus conf]$ sudo systemctl start

[ceph@octopus conf]$ sudo systemctl status
- Ceph cluster monitor daemon
Loaded: loaded (/usr/lib/systemd/system/ceph-mon@.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2016-04-22 20:09:58 EDT; 2s ago
Main PID: 10623 (ceph-mon)
CGroup: /system.slice/system-ceph\
└─10623 /usr/bin/ceph-mon -f --cluster ceph --id octopus --setuser ceph --setgroup ceph

Apr 22 20:09:58 octopus.fullstack.go systemd1: Started Ceph cluster monitor daemon.
Apr 22 20:09:58 octopus.fullstack.go systemd1: Starting Ceph cluster monitor daemon...
Apr 22 20:09:58 octopus.fullstack.go ceph-mon10623: starting mon.octopus rank 0 at 172.16.0.2:6789/0 mon_data /var/lib/ceph/mon/ceph-octopus fsid 7711b848-20d7-4831-aba5-7c65306f36bf

[ceph@octopus conf]$ ceph -v
ceph version 10.1.0 (96ae8bd25f31862dbd5302f304ebf8bf1166aba6)

Actions #1

Updated by bo zhou almost 8 years ago

I have the same problem !
You can enable ceph.target ceph-mon.target ceph-osd.target
and reboot ... V

Shinobu Kinjo wrote:

[ceph@octopus conf]$ sudo systemctl is-enabled
enabled

[ceph@octopus conf]$ sudo systemctl status
- Ceph cluster monitor daemon
Loaded: loaded (/usr/lib/systemd/system/ceph-mon@.service; enabled; vendor preset: disabled)
Active: inactive (dead)

[ceph@octopus conf]$ sudo systemctl start

[ceph@octopus conf]$ sudo systemctl status
- Ceph cluster monitor daemon
Loaded: loaded (/usr/lib/systemd/system/ceph-mon@.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2016-04-22 20:09:58 EDT; 2s ago
Main PID: 10623 (ceph-mon)
CGroup: /system.slice/system-ceph\
└─10623 /usr/bin/ceph-mon -f --cluster ceph --id octopus --setuser ceph --setgroup ceph

Apr 22 20:09:58 octopus.fullstack.go systemd1: Started Ceph cluster monitor daemon.
Apr 22 20:09:58 octopus.fullstack.go systemd1: Starting Ceph cluster monitor daemon...
Apr 22 20:09:58 octopus.fullstack.go ceph-mon10623: starting mon.octopus rank 0 at 172.16.0.2:6789/0 mon_data /var/lib/ceph/mon/ceph-octopus fsid 7711b848-20d7-4831-aba5-7c65306f36bf

[ceph@octopus conf]$ ceph -v
ceph version 10.1.0 (96ae8bd25f31862dbd5302f304ebf8bf1166aba6)

Actions #2

Updated by Nathan Cutler almost 8 years ago

This is a known bug that was fully fixed only after the jewel release. As a workaround, please do as Bo Zhou advises. If you are running MDS and/or RGW, you will need to do systemctl enable ceph-mds.target ceph-radosgw.target as well.

Actions #3

Updated by Greg Farnum almost 7 years ago

  • Status changed from New to Closed

Based on Nathan's comment.

Actions

Also available in: Atom PDF