Thanks for the reply.
I ran `nestat -tulpn` after restarting the rpcbind service and did not see anything listening on 749. Unfortunately, I didn't think to run it before I restarted the rpcbind service.
Is it possible kadmin think the port is in use even after rpcbind has moved off it?
On ke, 04 syys 2019, Mike Conner via FreeIPA-users wrote:
Thanks for the reply.
I ran `nestat -tulpn` after restarting the rpcbind service and did not see anything listening on 749. Unfortunately, I didn't think to run it before I restarted the rpcbind service.
Is it possible kadmin think the port is in use even after rpcbind has moved off it?
It is a known issue with rpcbind. This should be fixed in rpcbind 1.2.5, according to https://bugzilla.redhat.com/show_bug.cgi?id=1592883
https://git.linux-nfs.org/?p=steved/rpcbind.git;a=commitdiff;h=2e9c289246c64...
freeipa-users@lists.fedorahosted.org