I’ve seen that once or twice. If a restart of the app didn’t fix it, then a reboot of the OS did. I recall seeing that for sure after I disabled iptables and tried to start the app. Rather than try to figure it out, I rebooted and everything was fine when it came back up.
It’d be helpful if it would spit out which port was already allocated. 