Hello, First of all, the problem at hand is not that the mechanism doesn't work, it is the fact that NFS file transfer takes too long. From what I see, the NFS mechanism has worked at least partly.
The NFS was correctly mounted and the coredump transfer was initiated. For some reason, the NFS service started to timeout, but kdump-tools doesn't have much to do with it. One thing did get my attention. The mount command that you issued returns the following (edited for clarity ): # mount /dev/sda2 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,nodev,noexec,nosuid) ... 9.3.189.84:/nfsshare on /nfsmount type nfs (rw,vers=4,addr=9.3.189.84,clientaddr=9.114.13.128) The NFS mount on /var/crash is not appearing which is definitively a problem as this is done at a very early stage of the process. And it was mounted at the beginning since there is a vmcore-incomplete file on the remote NFS server. I don't have any context on the size of the file to be transfered and maybe it did bring the kexec booted kernel to memory exhaustion but there is no sign of OOM which is to be expected in these situations. Right now, with the data at hand, I cannot put forward anything else than an lack of availability of the NFS server that caused the failure. ** Tags added: cts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423483 Title: Kdump over network(nfs) does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1423483/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
