Hi, so no one has seen the problem of disabled systemd units before? Regards, Hubert Am Mo., 6. Apr. 2020 um 12:30 Uhr schrieb Hu Bert <revirii@xxxxxxxxxxxxxx>: > > Hello, > > after a server reboot (with a fresh gluster 6.8 install) i noticed > that the gluster services weren't running. > > systemctl status glusterd.service > ● glusterd.service - GlusterFS, a clustered file-system server > Loaded: loaded (/lib/systemd/system/glusterd.service; disabled; > vendor preset: enabled) > Active: inactive (dead) > Docs: man:glusterd(8) > > Apr 06 11:34:18 glfsserver1 systemd[1]: > /lib/systemd/system/glusterd.service:9: PIDFile= references path below > legacy directory /var/run/, updating /var/run/glusterd.pid → > /run/glusterd.pid; please update the unit file accordingly. > > systemctl status glustereventsd.service > ● glustereventsd.service - Gluster Events Notifier > Loaded: loaded (/lib/systemd/system/glustereventsd.service; > disabled; vendor preset: enabled) > Active: inactive (dead) > Docs: man:glustereventsd(8) > > Apr 06 11:34:27 glfsserver1 systemd[1]: > /lib/systemd/system/glustereventsd.service:11: PIDFile= references > path below legacy directory /var/run/, updating > /var/run/glustereventsd.pid → /run/glustereventsd.pid; please update > the unit file accordingly. > > You have to enable them manually: > > systemctl enable glusterd.service > Created symlink > /etc/systemd/system/multi-user.target.wants/glusterd.service → > /lib/systemd/system/glusterd.service. > systemctl enable glustereventsd.service > Created symlink > /etc/systemd/system/multi-user.target.wants/glustereventsd.service → > /lib/systemd/system/glustereventsd.service. > > Is this a bug? If so: already known? > > > Regards, > Hubert ________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
