Bug #23070
closedhttpd fails for KDC proxy when port parameters are used
Description
The default installation with foreman-installer -v
works fine; I can access and log in to The Foreman via the web front-end just fine.
When I need different ports for HTTP and SSL to be used, however, and I specify the ports as follows then the installer fails:
foreman-installer -v --foreman-server-port=9080 --foreman-server-ssl-port=9443 --foreman-admin-password=foo-bar-baz
Error Message¶
After configuring KDC proxy for HTTPd (on CentOS) the installer aborts with:
Syntax error on line 18 of /etc/httpd/conf.d/ipa-kdc-proxy.conf
Invalid command ‘WSGIDaemonProcess’, perhaps misspelled or defined by a module not included in the server configuration
Expected Behavior¶
The foreman-installer should install normally even with various, valid command line arguments.
Analysis¶
The file /etc/httpd/conf.d/ipa-kdc-proxy.conf
looks like follows, and on line 18 there is the WSGIDaemonProcess
directive.
WSGIDaemonProcess kdcproxy processes=2 threads=15 maximum-requests=5000 \ user=kdcproxy group=kdcproxy display-name=%{GROUP} WSGIImportScript /usr/lib/python2.7/site-packages/kdcproxy/__init__.py \ process-group=kdcproxy application-group=kdcproxy WSGIScriptAlias /KdcProxy /usr/lib/python2.7/site-packages/kdcproxy/__init__.py WSGIScriptReloading Off <Location "/KdcProxy"> Satisfy Any Order Deny,Allow Allow from all WSGIProcessGroup kdcproxy WSGIApplicationGroup kdcproxy </Location>
The mod_wsgi
module seems to be installed, but still httpd
fails to (re)start. Note that it all installs just perfectly with the default command line parameters.
Foreman and Proxy versions¶
Foreman 1.17 (latest), installed from repos configured via https://yum.theforeman.org/releases/1.17/el7/x86_64/foreman-release.rpm
See Also¶
More information may be available from https://community.theforeman.org/t/installer-httpd-fails-for-kdc-proxy-centos-7/8656
Updated by Ewoud Kohl van Wijngaarden over 4 years ago
- Status changed from New to Rejected
This likely happened because the installer cleared out the mod_wsgi config. If you're making these modifications, you need to ensure that's loaded. The KDC proxy is not something the installer manages so I don't consider this a bug.