Qpidd [Broker] critical Unexpected error: Couldn't find any network address to listen to

Support
#1

Problem: [Broker] critical Unexpected error: Couldn’t find any network address to listen to

Expected outcome: Upgrade to F3.2/K4.4

Foreman and Proxy versions: Foreman 3.2 / Foreman-proxy 3.2

Foreman and Proxy plugin versions: Foreman 3.2/ Katello 4.4

Distribution and version:

Other relevant data:
Hi All,
I am trying to upgrade my foreman from 2.3 to 3.2 version on RHEL7.
After solving various package dependency issues, i came across a solution to remove python3-pulp2to3-migration and completely erased the package.
Updated the system to install Foreman 3.2/ Katello 4.4 and now the qpidd service failed while running foreman-installer command.
I can see these error logs on katello.log:
2022-08-11 13:34:13 [DEBUG ] [configure] Running journalctl command to get logs for systemd start failure: journalctl -n 50 --since ‘5 minutes ago’ -u qpidd --no-pager
2022-08-11 13:34:13 [DEBUG ] [configure] Executing: ‘journalctl -n 50 --since ‘5 minutes ago’ -u qpidd --no-pager’
2022-08-11 13:34:13 [ERROR ] [configure] Systemd start for qpidd failed!
2022-08-11 13:34:13 [ERROR ] [configure] journalctl log for qpidd:
2022-08-11 13:34:13 [ERROR ] [configure] Aug 11 13:32:43 syprvlasmoq02 qpidd[34769]: 2022-08-11 13:32:43 [Broker] critical Broker (pid=34769) start-up failed: Couldn’t find any network address to listen to
2022-08-11 13:34:13 [ERROR ] [configure] Aug 11 13:32:43 syprvlasmoq02 qpidd[34769]: 2022-08-11 13:32:43 [Broker] critical Broker (pid=34769) start-up failed: Couldn’t find any network address to listen to
2022-08-11 13:34:13 [ERROR ] [configure] Aug 11 13:32:43 syprvlasmoq02 qpidd[34769]: 2022-08-11 13:32:43 [Broker] critical Unexpected error: Couldn’t find any network address to listen to
2022-08-11 13:34:13 [ERROR ] [configure] Aug 11 13:32:43 syprvlasmoq02 qpidd[34769]: 2022-08-11 13:32:43 [Broker] critical Unexpected error: Couldn’t find any network address to listen to
2022-08-11 13:34:13 [ERROR ] [configure] Aug 11 13:32:43 syprvlasmoq02 systemd[1]: qpidd.service: main process exited, code=exited, status=1/FAILURE
2022-08-11 13:34:13 [ERROR ] [configure] Aug 11 13:34:13 syprvlasmoq02 systemd[1]: qpidd.service start-post operation timed out. Stopping.
2022-08-11 13:34:13 [ERROR ] [configure] Aug 11 13:34:13 syprvlasmoq02 systemd[1]: Unit qpidd.service entered failed state.
2022-08-11 13:34:13 [ERROR ] [configure] Aug 11 13:34:13 syprvlasmoq02 systemd[1]: qpidd.service failed.
2022-08-11 13:34:13 [ERROR ] [configure] /Stage[main]/Qpid::Service/Service[qpidd]/ensure: change from ‘stopped’ to ‘running’ failed: Systemd start for qpidd failed!

Has anyone been through same issue?
Please advise.

#2

Did you upgrade through all the versions between 2.3/3.18 and 3.2/4.4?

#3

Yes I was successful in upgrading to F3.0/K4.2
But when I came across this error when upgrading to F3.2/K4.4.

#4

I think this might be an occurrence of Bug #34860: Resetting nssdb certificate does not update private key and breaks Qpid - Installer - Foreman, which is fixed in F3.3/K4.5
We’re not planning to do another 3.2 release, but I think the patch (Ensure nssdb private key changes when certificate changes by ehelms · Pull Request #397 · theforeman/puppet-certs · GitHub) should apply cleanly on 3.2 too and you could try that out. Or “just” upgrade to 3.3?

#5

Do you still use katello-agent? If not, you could have it removed with foreman-installer. That should remove qpidd completely…

#6

Hi All, I found a solution to this.
I learned that Qpidd is only uselful if you run the Katello Agent, so i wiped out qpidd completely and reran the installer.

I reran foreman-installer --foreman-proxy-content-enable-katello-agent=false and that helped me in upgrade to F3.2/K4.4.

Thanks everyone for your quick response, much appreciated!