Well, i understand that there is a change and acted afterwards accordingly - enabled them manually. But why i do not see same daemons? was there a crucial change between 7.7-1 and 7.8-1?
on a server, which was updated from stretch to buster: # dpkg -l|grep gluster ii glusterfs-client 7.7-1 amd64 clustered file-system (client package) ii glusterfs-common 7.7-1 amd64 GlusterFS common libraries and translator modules ii glusterfs-server 7.7-1 amd64 clustered file-system (server package) # systemctl --all|grep gluster srv-gluster-xftpservices.mount loaded active mounted /srv/gluster/xftpservices var-log-glusterfs.mount loaded active mounted /var/log/glusterfs glusterd.service loaded active running GlusterFS, a clustered file-system server glustereventsd.service loaded active running Gluster Events Notifier glusterfssharedstorage.service loaded active running Mount glusterfs sharedstorage on a clear buster server installed from scratch: # dpkg -l|grep gluster ii glusterfs-client 7.8-1 amd64 clustered file-system (client package) ii glusterfs-common 7.8-1 amd64 GlusterFS common libraries and translator modules ii glusterfs-server 7.8-1 amd64 clustered file-system (server package) ii libglusterfs0:amd64 7.8-1 amd64 GlusterFS shared library # systemctl --all|grep gluster srv-gluster-xftpservices.mount loaded active mounted /srv/gluster/xftpservices var-log-glusterfs.mount loaded active mounted /var/log/glusterfs glusterd.service loaded active running GlusterFS, a clustered file-system server glustereventsd.service loaded active running Gluster Events Notifier Thanks for help in advance. Kind regards, peterk On Wed, 14 Oct 2020 at 14:55, Kaleb Keithley <kkeit...@redhat.com> wrote: > tl;dnr: some linux distribution package guidelines say it's bad to > automatically start services after installing. > > long answer: > The package layout of the gluster packages changed in the base packages of > newer Debian and Ubuntu releases. To be compatible — e.g. to update from > Buster's base glusterfs to the gluster community packages — the Gluster > community packages switched to the same layout. If they used to start > automatically before, and they don't now, that's almost certainly why. > > For the most part we just copied the base package debian files, so > whatever the base packages do, or don't do, that's what the community > packages also do, including starting, or not starting the daemons. > > > On Wed, Oct 14, 2020 at 8:39 AM peter knezel <peter.kne...@gmail.com> > wrote: > >> Hello Kaleb, >> thanks for your email. >> >> i think i found the problem. >> In previous releases, when gluster packages are installed, they are >> started. >> In the case of 7.8-1 version i needed to check and enable them: >> systemctl is-enabled xx >> systemctl enable xx >> systemctl start xx >> >> where xx={glusterd.service, glustereventsd.service} >> >> But i still miss the glusterfssharedstorage.service - i think it will be >> activated when a glusterfs client locally mounts a created volume. >> >> I will go on and recheck all my steps. i will update this thread later. >> Kind regards, >> peterk >> >> >> On Wed, 14 Oct 2020 at 14:16, Kaleb Keithley <kkeit...@redhat.com> wrote: >> >>> On Wed, Oct 14, 2020 at 7:56 AM peter knezel <peter.kne...@gmail.com> >>> wrote: >>> >>>> Hello All, >>>> >>>> i have installed 7.8-1 version of glusterfs packages on a VM with >>>> debian buster 10.5 and see no glusterfs daemons present. >>>> >>>> root@buster:~# dpkg -l|grep gluster >>>> ii glusterfs-client 7.8-1 >>>> amd64 clustered file-system (client package) >>>> ii glusterfs-common 7.8-1 >>>> amd64 GlusterFS common libraries and translator modules >>>> ii glusterfs-server 7.8-1 >>>> amd64 clustered file-system (server package) >>>> ii libglusterfs0:amd64 7.8-1 >>>> amd64 GlusterFS shared library >>>> root@buster:~# cat /etc/debian_version >>>> 10.5 >>>> root@buster:~# uname -a >>>> Linux buster 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) >>>> x86_64 GNU/Linux >>>> root@buster:~# systemctl --all|grep gluster >>>> root@buster:~# >>>> >>>> root@buster:/etc/systemd/system/multi-user.target.wants# pwd >>>> /etc/systemd/system/multi-user.target.wants >>>> root@buster:/etc/systemd/system/multi-user.target.wants# ls -ltr|grep >>>> gluster >>>> root@buster:/etc/systemd/system/multi-user.target.wants# >>>> >>>> >>>> root@buster:/lib/systemd/system# ls -ltr|grep gluster >>>> -rw-r--r-- 1 root root 400 Sep 29 04:01 glustereventsd.service >>>> -rw-r--r-- 1 root root 466 Sep 29 04:01 glusterd.service >>>> root@buster:/lib/systemd/system# >>>> >>>> on updated server from stretch to buster: >>>> root@stretchtobluster:/lib/systemd/system# ls -ltr|grep gluster >>>> -rw-r--r-- 1 root root 425 Jul 21 05:16 gluster-ta-volume.service >>>> -rw-r--r-- 1 root root 301 Jul 21 05:16 glusterfssharedstorage.service >>>> -rw-r--r-- 1 root root 400 Jul 21 05:16 glustereventsd.service >>>> -rw-r--r-- 1 root root 464 Jul 21 05:16 glusterd.service >>>> root@stretchtobluster:/lib/systemd/system# >>>> >>>> Is something missing here? >>>> >>> >>> The Gluster executables (including the daemons: glusterd, glusterfsd, >>> glusterfs, and glustereventsd) aren't installed in /lib/systemd/... and >>> never have been. >>> >>> They are installed in /usr/sbin/, and >>> /usr/lib/$arch-linux-gnu/glusterfs/ or on newer Debian in >>> /usr/libexec/glusterfs/ >>> >>> What do you think is missing? >>> >>> -- >>> >>> Kaleb >>> >>
________ 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@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users