We may want to use localhost to make it bind to both v4 and v6 sockets.
Created from redmine issue https://projects.theforeman.org/issues/28681
*** Bug 1789007 has been marked as a duplicate of this bug. ***
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28681 has been resolved.
Satellite version: 6.8 Snap8
1- foreman-installer version
# rpm -q foreman-installer
2. Smart_proxy_dynflow_core.pid listen on all ip4 and ipv6 addresses.
# ps -aef|grep foreman-proxy
foreman+ 10974 1 0 Jul13 ? 00:00:56 ruby /usr/bin/smart_proxy_dynflow_core -d -p /var/run/foreman-proxy/smart_proxy_dynflow_core.pid
foreman+ 36992 1 0 Jul13 ? 00:00:04 ruby /usr/share/foreman-proxy/bin/smart-proxy --no-daemonize
# sudo netstat -lnp|grep 36992
tcp 0 0 0.0.0.0:9090 0.0.0.0:* LISTEN 36992/ruby
tcp6 0 0 :::9090 :::* LISTEN 36992/ruby
# sudo netstat -lnp|grep 10974
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN 10974/ruby
tcp6 0 0 :::8008 :::* LISTEN 10974/ruby
There was a typo in Comment12 step2, Smart_proxy_dynflow_core.service listen on all ipv4 and ipv6 addresses instead of Smart_proxy_dynflow_core.pid.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.