[Gluster-users] Gluster CLI - No output/no info displayed.

Sanju Rakonde srakonde at redhat.com
Thu Jun 27 04:13:52 UTC 2019


On Sun, Jun 23, 2019 at 4:54 AM Laurent Dumont <laurentfdumont at gmail.com>
wrote:

> Hi,
>
> I am facing a strange issue with the Gluster CLI. No matter what command
> is used, the CLI doesn't output anything. It's a gluster with a single
> node. The volumes themselves are working without any issues.
>
> coldadmin at gluster01:~$ sudo dpkg -l | grep -i gluster
>> ii  glusterfs-client               6.3-1                          amd64
>>      clustered file-system (client package)
>> ii  glusterfs-common               6.3-1                          amd64
>>      GlusterFS common libraries and translator modules
>> ii  glusterfs-server               6.0-1                          amd64
>>      clustered file-system (server package)
>
>
Looks like, you've missed installing glusterfs-cli package. This is why you
are unable to execute any commands using cli.

Thanks,
Sanju

>
>> coldadmin at gluster01:~$ sudo gluster --version
>> glusterfs 6.0
>> Repository revision: git://git.gluster.org/glusterfs.git
>> Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/>
>> GlusterFS comes with ABSOLUTELY NO WARRANTY.
>> It is licensed to you under your choice of the GNU Lesser
>> General Public License, version 3 or any later version (LGPLv3
>> or later), or the GNU General Public License, version 2 (GPLv2),
>> in all cases as published by the Free Software Foundation.
>
>
> coldadmin at gluster01:~$ sudo gluster volume info all
>> coldadmin at gluster01:~$
>
>
> The cli.log is filled with :
>
> root at gluster01:/var/log/glusterfs# tail cli.log
>> [2019-06-22 23:10:31.397945] I [cli.c:834:main] 0-cli: Started running
>> gluster with version 6.0
>> [2019-06-22 23:10:31.398325] E [mem-pool.c:868:mem_get]
>> (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x18705) [0x7fc937069705]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x1863c) [0x7fc93706963c]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(mem_get+0x98)
>> [0x7fc9370a12f8] ) 0-mem-pool: invalid argument [Invalid argument]
>> [2019-06-22 23:13:20.895606] I [cli.c:834:main] 0-cli: Started running
>> gluster with version 6.0
>> [2019-06-22 23:13:20.895887] E [mem-pool.c:868:mem_get]
>> (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x18705) [0x7f65fc2e0705]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x1863c) [0x7f65fc2e063c]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(mem_get+0x98)
>> [0x7f65fc3182f8] ) 0-mem-pool: invalid argument [Invalid argument]
>> [2019-06-22 23:13:22.603313] I [cli.c:834:main] 0-cli: Started running
>> gluster with version 6.0
>> [2019-06-22 23:13:22.603581] E [mem-pool.c:868:mem_get]
>> (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x18705) [0x7fe7cd672705]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x1863c) [0x7fe7cd67263c]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(mem_get+0x98)
>> [0x7fe7cd6aa2f8] ) 0-mem-pool: invalid argument [Invalid argument]
>> [2019-06-22 23:13:47.945239] I [cli.c:834:main] 0-cli: Started running
>> gluster with version 6.0
>> [2019-06-22 23:13:47.945481] E [mem-pool.c:868:mem_get]
>> (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x18705) [0x7fd31bb2c705]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x1863c) [0x7fd31bb2c63c]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(mem_get+0x98)
>> [0x7fd31bb642f8] ) 0-mem-pool: invalid argument [Invalid argument]
>> [2019-06-22 23:14:09.015151] I [cli.c:834:main] 0-cli: Started running
>> gluster with version 6.0
>> [2019-06-22 23:14:09.015461] E [mem-pool.c:868:mem_get]
>> (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x18705) [0x7f471963b705]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x1863c) [0x7f471963b63c]
>> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(mem_get+0x98)
>> [0x7f47196732f8] ) 0-mem-pool: invalid argument [Invalid argument]
>
>
> The strange part is that cmd_history.log is not logging my commands
> anymore :(
>
> root at gluster01:/var/log/glusterfs# tail cmd_history.log
>> [2019-05-19 21:45:27.814905]  : volume start media : FAILED : Volume
>> media already started
>> [2019-05-19 21:45:32.630507]  : volume status all : SUCCESS
>> [2019-05-19 21:45:32.632032]  : volume status all : SUCCESS
>> [2019-05-19 21:45:32.644639]  : volume status all : SUCCESS
>> [2019-05-19 21:46:21.691147]  : volume status all : SUCCESS
>> [2019-05-19 21:46:21.692664]  : volume status all : SUCCESS
>> [2019-05-19 21:46:21.706471]  : volume status all : SUCCESS
>> [2019-05-19 21:48:15.418905]  : volume status all : SUCCESS
>> [2019-05-19 21:48:15.420487]  : volume status all : SUCCESS
>> [2019-05-19 21:48:15.422784]  : volume status all : SUCCESS
>
>
> I have this old bug from 2015, but the issue seems to be purely cosmetic.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1243753
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users



-- 
Thanks,
Sanju
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190627/80521134/attachment.html>


More information about the Gluster-users mailing list