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
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?
-users@lists.fedorahosted.org
Cc: Mike Conner
Subject: [Freeipa-users] Re: kadmin service fails to start
I decided to reboot the master and the services came back up without a problem.
Is it likely I was experiencing the bug that I linked earlier, and that just
restarting the rpcbind service
I decided to reboot the master and the services came back up without a problem.
Is it likely I was experiencing the bug that I linked earlier, and that just
restarting the rpcbind service isn't enough to free the port for kadmin to use?
___
The most useful bit of information I've found so far is this from the kadmind
log:
kadmind[14297](Error): Failed setting up a RPC socket (for 0.0.0.0.749)
kadmind: Address already in use - Error setting up network
I read that this can be caused by the rpcbind service taking over the port
