[Bugs] [Bug 1436678] [Doc RFE] Document how to take Statedump for gfapi applications

bugzilla at redhat.com bugzilla at redhat.com
Thu May 11 08:05:09 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1436678

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(ndevos at redhat.com |
                   |)                           |



--- Comment #4 from Niels de Vos <ndevos at redhat.com> ---
Yes, this is an addition to the last part of that section.

> To retrieve the statedump information for client processes:
> 
>    kill -USR1 process_ID 

Applications using gfapi are client processes, but gfapi may not handle the
signals (like USR1) because the applications should handle them. This prevented
creating statedumps from gfapi-client (NFS-Ganesha, Samba, QEMU, ...) processes
before.

After executing the command, the statedump will be written to /var/run/gluster,
just like with other client processes. You should note that the user running
the application requires write permissions to /var/run/gluster. gfapi
applications do not require running as root, and for this a group "gluster" has
been created. The user running the application (in case of QEMU this is the
"qemu" user) needs to be added to the "gluster" group. A command like this
would do:

  # usermod -a -G gluster qemu

[Bug 1447694 has been filed to get this done in the QEMU packaging for RHV.]

Note that QEMU is just one example, admins can configure applications to run as
any user they like. Also users that run applications that use gfapi and need
the advanced debugging options with statedumps should be added to the "gluster"
group.

There is no need for users to understand the contents of the statedump itself.
This is purely a Gluster internal mechanism used for troubleshooting and
debugging. The note about statedumps in the documentation is more intended for
GSS/CEE and less for customers.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=QUOBP5jT91&a=cc_unsubscribe


More information about the Bugs mailing list