Hi Doug, Dear Bruce, FYI, I filed a bug with nfs-common package in Debian Buster: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963746 Hope this helps to track down the problem further and shed some light on the mysterious segfaults of rpc.gssd. >> A quick google links to https://wiki.debian.org/HowToGetABacktrace. BTW: Thanks very much for the link. This helped to find the right dbgsym packages in order to produce a more readable and hopefully valuable backtrace. ;-) I also passed by a similar and still open issue in the CentOS bug tracker: https://bugs.centos.org/view.php?id=15895 Best and Thanks for your support up to now Sebastian ___________________ Sebastian Kraus Team IT am Institut für Chemie Gebäude C, Straße des 17. Juni 115, Raum C7 Technische Universität Berlin Fakultät II Institut für Chemie Sekretariat C3 Straße des 17. Juni 135 10623 Berlin Email: sebastian.kraus@xxxxxxxxxxxx ________________________________________ From: Doug Nazar <nazard@xxxxxxxx> Sent: Thursday, June 25, 2020 23:44 To: Kraus, Sebastian; J. Bruce Fields Cc: linux-nfs@xxxxxxxxxxxxxxx Subject: Re: Strange segmentation violations of rpc.gssd in Debian Buster On 2020-06-25 13:43, Kraus, Sebastian wrote: > [Current thread is 1 (Thread 0x7fb2eaeba700 (LWP 14174))] > (gdb) bt > #0 0x000056233fff038e in ?? () > #1 0x000056233fff09f8 in ?? () > #2 0x000056233fff0b92 in ?? () > #3 0x000056233fff13b3 in ?? () > #4 0x00007fb2eb8dbfa3 in start_thread (arg=<optimized out>) at pthread_create.c:486 > #5 0x00007fb2eb80c4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > (gdb) quit > > > I am not an expert in analyzing stack and backtraces. Is there anything meaningful, you are able to extract from the trace? > As far as I see, thread 14174 caused the segmentation violation just after its birth on clone. > Please correct me, if I am in error. > Seems Debian Buster does not ship any dedicated package with debug symbols for the rpc.gssd executable. > So far, I was not able to find such a package. > What's your opinon about the trace? You'll need to install the debug symbols for your distribution/package. A quick google links to https://wiki.debian.org/HowToGetABacktrace. Those ?? lines should then be replaced with function, file & line numbers. I've been following this with interest since it used to happen to me a lot. It hasn't recently, even though every so often I spend a few hours trying to re-create it to try debug it. Doug
