Bug 1244103 - Gluster cli logs invalid argument error on every gluster command execution
Summary: Gluster cli logs invalid argument error on every gluster command execution
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1243753
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-17 06:53 UTC by Anoop C S
Modified: 2015-07-30 09:47 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.7.3
Clone Of: 1243753
Environment:
Last Closed: 2015-07-30 09:47:24 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Anoop C S 2015-07-17 06:53:54 UTC
+++ This bug was initially created as a clone of Bug #1243753 +++

Description of problem:
Each every time when a gluster command is executed directly, the following error is being logged in cli logs.

[2015-07-16 06:21:22.746577] E [mem-pool.c:417:mem_get0] (-->/usr/local/lib/libglusterfs.so.0(+0x7e262) [0x7fdbc0b1f262] -->/usr/local/lib/libglusterfs.so.0(_gf_msg+0x804) [0x7fdbc0ac7844] -->/usr/local/lib/libglusterfs.so.0(mem_get0+0x78) [0x7fdbc0af5b48] ) 0-mem-pool: invalid argument [Invalid argument]

Version-Release number of selected component (if applicable):
master

How reproducible:
Always

Steps to Reproduce:
1. Build glusterfs from master and start glusterd service
2. Execute any gluster command and check cli logs for the above mentioned error.

Actual results:
Error logs are seen.

Expected results:
No errors are seen.

Additional info:

--- Additional comment from Anand Avati on 2015-07-16 04:56:39 EDT ---

REVIEW: http://review.gluster.org/11691 (cli: Create missing logbuf_pool) posted (#1) for review on master by Anoop C S (achiraya)

--- Additional comment from Anand Avati on 2015-07-17 01:04:13 EDT ---

COMMIT: http://review.gluster.org/11691 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit 4cdeee511ef8bab977cbb31bc2e8f005fe340ef1
Author: Anoop C S <anoopcs>
Date:   Thu Jul 16 13:56:51 2015 +0530

    cli: Create missing logbuf_pool
    
    Since logbuf_pool was not created via glusterfs_ctx_defaults_init(),
    the following error was present in cli logs repeateadly for each
    and every execution of a gluster command.
    
    E [mem-pool.c:417:mem_get0] (-->/usr/local/lib/libglusterfs.so.0(+0x7e262)
    [0x7fdbc0b1f262] -->/usr/local/lib/libglusterfs.so.0(_gf_msg+0x804)
    [0x7fdbc0ac7844] -->/usr/local/lib/libglusterfs.so.0(mem_get0+0x78)
    [0x7fdbc0af5b48] ) 0-mem-pool: invalid argument [Invalid argument]
    
    This change creates ctx->logbuf_pool via glusterfs_ctx_defaults_init()
    in cli.c so that the above error is no longer logged in cli logs.
    
    Change-Id: I3fcd9cfefa06ddd52e1989b039ff5637372c3235
    BUG: 1243753
    Signed-off-by: Anoop C S <anoopcs>
    Reviewed-on: http://review.gluster.org/11691
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Krishnan Parthasarathi <kparthas>

Comment 1 Anand Avati 2015-07-17 06:59:08 UTC
REVIEW: http://review.gluster.org/11705 (cli: Create missing logbuf_pool) posted (#1) for review on release-3.7 by Anoop C S (achiraya)

Comment 2 Kaushal 2015-07-30 09:47:24 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.3, please open a new bug report.

glusterfs-3.7.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.