2:53 a.m.
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
7:58 a.m.
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(a)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(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
8:25 a.m.
Unfortunately no.
Here is what we have in
` dmesg -T` :
[Fri Jan 10 00:03:20 2020] type=1305 audit(1578603800.729:930): audit_pid=17526 old=0
auid=4294967295 ses=4294967295 res=1
[Fri Jan 10 00:28:39 2020] ganesha.nfsd[8252]: segfault at 7f9b771209c0 ip
00007f9b771209c0 sp 00007f9b2bffcb38 error 14 in nsswitch.so[7f9b77856000+3000]
[Fri Jan 10 00:29:16 2020] ganesha.nfsd[9535]: segfault at 7febe72e89c0 ip
00007febe72e89c0 sp 00007febbbffcb38 error 14 in nsswitch.so[7febe7806000+3000]
[Mon Jan 13 11:31:04 2020] ganesha.nfsd[28358]: segfault at 104 ip 00007f88d8472bd9 sp
00007f88c01c68d0 error 6 in libganesha_nfsd.so.2.8[7f88d83f1000+1c0000]
nothing more... I'll try to catch same error in Ubuntu...
one more q about logs in Ganesha:
I have this one in ganesha.conf:
LOG {
Default_Log_Level = INFO;
Components {
#FSAL = INFO;
#NFS4 = EVENT;
}
Facility {
name = FILE;
destination = "/var/log/ganesha.log";
enable = active;
}
}
and the main strange thing is:
/var/log/ganesha.log is a log where I see nfs_health and other logs
And also I have this:
[root@sk ~]# cat /var/log/ganesha/ganesha.log
13/01/2020 11:43:33 : epoch 5e1c2db5 : sk : ganesha.nfsd-7911[main] main :MAIN :EVENT
:ganesha.nfsd Starting: Ganesha Version 2.8.1.2
8:47 a.m.
Ganesha doesn't log much at the INFO level, and can't log it's own crash
anyway, so I wouldn't expect much in the ganesha.log about this. If the
crash is reproducible, you can turn up the logging on Ganesha, and maybe
get something useful out of that log, but the best solution is to get
Ubuntu to log the full backtrace. I'm not an Ubuntu user, so I don't
know how to do that.
Daniel
On 1/15/20 9:25 AM, sundelor(a)gmail.com wrote:
Unfortunately no.
Here is what we have in
` dmesg -T` :
[Fri Jan 10 00:03:20 2020] type=1305 audit(1578603800.729:930): audit_pid=17526 old=0
auid=4294967295 ses=4294967295 res=1
[Fri Jan 10 00:28:39 2020] ganesha.nfsd[8252]: segfault at 7f9b771209c0 ip
00007f9b771209c0 sp 00007f9b2bffcb38 error 14 in nsswitch.so[7f9b77856000+3000]
[Fri Jan 10 00:29:16 2020] ganesha.nfsd[9535]: segfault at 7febe72e89c0 ip
00007febe72e89c0 sp 00007febbbffcb38 error 14 in nsswitch.so[7febe7806000+3000]
[Mon Jan 13 11:31:04 2020] ganesha.nfsd[28358]: segfault at 104 ip 00007f88d8472bd9 sp
00007f88c01c68d0 error 6 in libganesha_nfsd.so.2.8[7f88d83f1000+1c0000]
nothing more... I'll try to catch same error in Ubuntu...
one more q about logs in Ganesha:
I have this one in ganesha.conf:
LOG {
Default_Log_Level = INFO;
Components {
#FSAL = INFO;
#NFS4 = EVENT;
}
Facility {
name = FILE;
destination = "/var/log/ganesha.log";
enable = active;
}
}
and the main strange thing is:
/var/log/ganesha.log is a log where I see nfs_health and other logs
And also I have this:
[root@sk ~]# cat /var/log/ganesha/ganesha.log
13/01/2020 11:43:33 : epoch 5e1c2db5 : sk : ganesha.nfsd-7911[main] main :MAIN :EVENT
:ganesha.nfsd Starting: Ganesha Version 2.8.1.2
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
4:53 a.m.
It is on RHEL7
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)
8:26 a.m.
Oh, RHEL. Sorry, I'm not sure where I got Ubuntu from. RHEL should
have abrt installed. Check in /var/lib/abrt/ to see if there's more info.
Daniel
On 1/16/20 5:53 AM, sundelor(a)gmail.com wrote:
It is on RHEL7
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)
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
2097
days inactive
2100
days old
6 comments
3 participants
participants (3)
-
Daniel Gryniewicz -
Daniel Gryniewicz -
sundelor＠gmail.com