Hi Mike
It's prolly too late but you could have tried this as root to identify which
process had port 749 open:
netstat -pan | grep LISTEN | grep 749
Regards
Angus
From: Mike Conner via FreeIPA-users
Sent: Wednesday, September 4, 2019 5:35:57 AM
To:
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
Hello,
I'm running freeipa 4.5.0-20 on CentOS Linux release 7.4.1708 (Core)
I've noticed that when rebooting my replica, things are not working anymore
on this replica, as I can't get a kinit work for example.
It seems that services are disabled by default and I wonder if this is
normal ? Should
I've had a FreeIPA installation running without issues until today directory
services went down and when I attempt to restart services using `ipactl
restart` the kadmin service fails to start. I've been digging through logs and
searching for answers but haven't found anything that makes sense
