[ceph-users] Re: how to restart daemons on 15.2 on Debian 10

2020-05-18 Thread Ml Ml
Is there no official link/docs how to manage the services on Debian 10 and 15.2.1? I have seach and seeked: systemctl restart ceph-5436dd5d-83d4-4dc8-a93b-60ab5db145df@mon.ceph01.service journalctl -u ceph-5436dd5d-83d4-4dc8-a93b-60ab5db145df@mon.ceph01.service docker logs Back in the days we ha

[ceph-users] Re: how to restart daemons on 15.2 on Debian 10

2020-05-18 Thread Ml Ml
Thanks, The following seems to work for me on Debian 10 and 15.2.1: systemctl restart ceph-5436dd5d-83d4-4dc8-a93b-60ab5db145df@mon.ceph01.service How can i restart a single OSD? Cheers, Michael On Sun, May 17, 2020 at 5:10 PM Sean Johnson wrote: > > I have OSD’s on the brain … that line shou

[ceph-users] Re: how to restart daemons on 15.2 on Debian 10

2020-05-18 Thread Sean Johnson
Use the same pattern …. systemctl restart ceph-{fsid}@osd.{id}.service ~Sean > On May 18, 2020, at 7:16 AM, Ml Ml wrote: > > Thanks, > > The following seems to work for me on Debian 10 and 15.2.1: > > systemctl restart ceph-5436dd5d-83d4-4dc8-a93b-60ab5db145df@mon.ceph01.service > > How can

[ceph-users] Re: how to restart daemons on 15.2 on Debian 10

2020-05-17 Thread Sean Johnson
I have OSD’s on the brain … that line should have read: systemctl restart ceph-{fsid}@mon.{host}.service > On May 17, 2020, at 10:08 AM, Sean Johnson wrote: > > In case that doesn’t work, there’s also a systemd service that contains the > fsid of the cluster. > > So, in the case of a mon serv

[ceph-users] Re: how to restart daemons on 15.2 on Debian 10

2020-05-17 Thread Sean Johnson
In case that doesn’t work, there’s also a systemd service that contains the fsid of the cluster. So, in the case of a mon service you can also run: systemctl restart ceph-{fsid}@osd.{host}.service Logs are correspondingly available via journalctl: journalctl -u ceph-{fsid}@mon.{host}.service

[ceph-users] Re: how to restart daemons on 15.2 on Debian 10

2020-05-15 Thread Simon Sutter
Hello Michael, I had the same problems. It's very unfamiliar, if you never worked with the cephadm tool. The Way I'm doing it is to go into the cephadm container: # cephadm shell Here you can list all containers (for each service, one container) with the orchestration tool: # ceph orch ps a