[VERIFICATION BIONIC]
Installation works fine using the proposed package.
Both glusterd and glustereventsd are disabled by default and can easily be
enabled (permanently) and/or simply started manually (temporarily), exactly
like successor package starting with Cosmic and late.
# apt-get install glusterfs-server -y
...
Setting up python-chardet (3.0.4-1) ...
Setting up python-cryptography (2.1.4-1ubuntu1.3) ...
Setting up python-requests (2.18.4-2ubuntu0.1) ...
Setting up python-openssl (17.5.0-1ubuntu1) ...
Setting up glusterfs-common (3.13.2-1ubuntu1) ...
Adding group `gluster' (GID 116) ...
Done.
Setting up glusterfs-client (3.13.2-1ubuntu1) ...
Setting up glusterfs-server (3.13.2-1ubuntu1) ...
glusterd.service is a disabled or a static unit, not starting it.
glustereventsd.service is a disabled or a static unit, not starting it.
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for systemd (237-3ubuntu10.21) ...
# dpkg -l | grep -i gluster
ii glusterfs-client 3.13.2-1ubuntu1 amd64
clustered file-system (client package)
ii glusterfs-common 3.13.2-1ubuntu1 amd64
GlusterFS common libraries and translator modules
ii glusterfs-server 3.13.2-1ubuntu1 amd64
clustered file-system (server package)
# systemd unit "glustereventsd"
# systemctl status glustereventsd.service
● glustereventsd.service - Gluster Events Notifier
Loaded: loaded (/lib/systemd/system/glustereventsd.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
# systemctl start glustereventsd.service
# systemctl status glustereventsd.service
● glustereventsd.service - Gluster Events Notifier
Loaded: loaded (/lib/systemd/system/glustereventsd.service; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2019-06-03 20:01:01 UTC; 1s ago
Main PID: 5950 (glustereventsd)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/glustereventsd.service
├─5950 /usr/bin/python2 /usr/sbin/glustereventsd --pid-file
/var/run/glustereventsd.pid
└─5951 /usr/bin/python2 /usr/sbin/glustereventsd --pid-file
/var/run/glustereventsd.pid
Jun 03 20:01:01 glustersproposed systemd[1]: Started Gluster Events
Notifier.
# systemd unit "glusterd"
# 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)
# systemctl starts glusterd.service
# systemctl status glusterd.service
● glusterd.service - GlusterFS, a clustered file-system server
Loaded: loaded (/lib/systemd/system/glusterd.service; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2019-06-03 20:00:31 UTC; 6s ago
Process: 5858 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid
--log-level $LOG_LEVEL $GLUSTERD_OPTIONS (code=e
Main PID: 5859 (glusterd)
Tasks: 8 (limit: 4915)
CGroup: /system.slice/glusterd.service
└─5859 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO
Jun 03 20:00:29 glustersproposed systemd[1]: Starting GlusterFS, a clustered
file-system server...
Jun 03 20:00:31 glustersproposed systemd[1]: Started GlusterFS, a clustered
file-system server.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830615
Title:
glusterfs-server 3.13.2-1build1 installation fails in Bionic
because starting up the glustereventsd.service times out
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1830615/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
