Unfortunately, without more information, there isn't anything we can do. This doesn't even give us enough to tell where the crash happened, let alone what was going on at the time. Is there really nothing like a backtrace in /var/log/messages? Usually, the kernel prints something useful there. Or maybe your system separates that out into another log? /var/log/abrt, maybe? Daniel On 1/13/20 3:53 AM, sundelor@gmail.com wrote:
Here is log from /var/log/messages Jan 13 11:31:11 sk kernel: ganesha.nfsd[28358]: segfault at 104 ip 00007f88d8472bd9 sp 00007f88c01c68d0 error 6 in libganesha_nfsd.so.2.8[7f88d83f1000+1c0000] Jan 13 11:31:11 sk systemd: nfs-ganesha.service: main process exited, code=killed, status=11/SEGV Jan 13 11:31:11 sk systemd: Unit nfs-ganesha.service entered failed state. Jan 13 11:31:11 sk systemd: nfs-ganesha.service failed.
in /var/log/ganesha.log nothing was logged.
Sys info: Linux sk 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 15 17:36:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.7 (Maipo)
Name : nfs-ganesha Arch : x86_64 Version : 2.8.1.2 Release : 0.1.el7
Name : rpcbind Arch : x86_64 Version : 0.2.0 Release : 48.el7
Name : nfs-ganesha-ceph Arch : x86_64 Version : 2.8.1.2 Release : 0.1.el7 _______________________________________________ Support mailing list -- support@lists.nfs-ganesha.org To unsubscribe send an email to support-leave@lists.nfs-ganesha.org