Hi, 
 
  Foreman-installer overwrites my customized ports.conf every time, I'm 
wondering whether there are some options for this issue. Let's elaborate it:

 On a Foreman server, I have two network interfaces: outside interface NIC1 
and internal interface NIC2.

Ports 80/443 and 8140 are listened on both NICs, but by different 
applications and for different purposes: 

 Internal interface NIC2:  80/443/8140 are used by Foreman cluster, and be 
taken care of by foreman-installer (apache)
Outside interface NIC1:  80/443/8140 are used by haproxy and linked for 
other purposes.

so, when things runs normal, I have the following contents inside  
/etc/httpd/conf/ports.conf
Listen NIC1:80
NameVirtualHost *:80
Listen NIC1:443
NameVirtualHost *:443
Listen NIC1:8140
NameVirtualHost *:8140

But after every Foreman-installer runs, say, upgrade, or tuning a few 
parameters, the file is reset back to the following:

Listen 80
NameVirtualHost *:80
Listen 443
NameVirtualHost *:443
Listen 8140
NameVirtualHost *:8140

Then surely the 'foreman-run' will fail in the middle, due to httpd/apache 
can not startup, because NIC2:80|443|8140 are already occupied (by haproxy).

is there an option like '--foreman-bind-host', similar to 
'--foreman-proxy-bind-host' that is available? I'm running Foreman 1.11.3. 
Thanks.



-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to