On 11/24/20 7:55 AM, Jonathan Billings wrote:
On Nov 23, 2020, at 22:08, Richard Kimberly Heck <rikiheck@xxxxxxx> wrote:
I believe it is v3 on the server.
If so, you need to make sure that the rpc.lockd can communicate on both sides. That is probably why locking fails, and any program that is hanging is because locks are hanging.
This looks like the issue:
Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 not
responding, still trying
This was working fine in Fedora 32, though, so I'm puzzled what's wrong
now. There's no firewall on the client, and nothing has changed on the
server, and I do not see any error messages there. Is lockd perhaps
using a different port, which is blocked on the server? If so, how do I
find out what that is?
Riki
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
