Package: glusterfs-client
Version: 3.8.8-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I had a problem mounting a glusterfs on a gluster-server at boot.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Wanted to try and check if glusterfind could be used to check if the glusterd
is up and running properly.
So I typed "glusterfind" to check how that would work.
* What was the outcome of this action?
root@storage-b-01:~# glusterfind
Traceback (most recent call last):
File "/usr/bin/glusterfind", line 14, in <module>
from glusterfind.main import main
ImportError: No module named glusterfind.main
* What outcome did you expect instead?
That glusterfind would show me some info why it wouldn't help me with my
problem.
Thanks!
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-7-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages glusterfs-client depends on:
ii fuse 2.9.7-1
ii glusterfs-common 3.8.8-1
ii libc6 2.24-11+deb9u3
ii libssl1.1 1.1.0f-3+deb9u2
ii python 2.7.13-2
glusterfs-client recommends no packages.
glusterfs-client suggests no packages.
-- no debconf information
