Re: Generation of systemd units after nuking /etc/systemd/system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/10/22 08:33, Flemming Frandsen wrote:
Hi, this is somewhat embarrassing, but one of my colleagues fat fingered an
ansible rule and managed to wipe out /etc/systemd/system on all of our ceph
hosts.

The cluster is running nautilus on ubuntu 18.04, deployed with
ceph-ansible, one of our near-future tasks is to upgrade to the latest ceph
and cephadm, so I'm not looking forward to redoing the entire cluster using
ceph-ansible.

Normally I'd put on the workboots and start re-installing a broken host
from scratch, but I hope there's a faster way.

Is there any way to generate the ceph-owned contents of /etc/systemd/system
?
Depending on how your colleague did the job, that is if systemctl daemon-reload was executed or not, most information might be in systemctl list-units or systemctl show <unit>.

This might be too late, but do stash the output of systemctl list-units for later.

Unless --no-reload is used as arg, systemctl enable <service> actually does daemon-reload.

Regards
Josef
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux