Hi again. I sshd to the nfs server and rebooted the nfs service. It seems to have solved the problem, at least as far as journalctl is concerned. Still I would like to know if there is a way to stop whomever is trying to access the nfs server from the client machine and avoid the error flood on journalctl.
Thanks
JP
On Sun, Apr 26, 2020 at 3:56 AM Javier Perez pepebuho@gmail.com wrote:
Hi I had to unplug the ethernet cable from the nfs server. After I plugged it back, the client machine is filling my journal with the following message
nfs: server "ipaddress" not responding, time out
where ipaddress is the ip address of the nfs server.
I did a lazy unmount of all the shared directories, but I am still getting this message. If I try to use Thunar, it will not open up and even the panel will not accept a click. I can switch windows with ALT+TAB
How can I find out whatever process is still trying to reach the nfs subdirectories and kill it?
Last time this happened I had to reboot the system. I do not want to do it again
Thanks
JP
/_/\ |O O| pepebuho@gmail.com
~~~~ While the night runs ~~~~ toward the day... m m Pepebuho watches from his high perch.