Bug #11983
closed
Rudder server installation fails if apache cannot resolve server hostname
Added by Nicolas CHARLES almost 7 years ago.
Updated almost 7 years ago.
Category:
System techniques
Description
INFO: Restarting Rudder webapp and inventory-endpoint...dpkg: error processing package rudder-webapp (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of rudder-server-root:
rudder-server-root depends on rudder-webapp (= 4.3.0~alpha1~git201801170043-stretch0); however:
Package rudder-webapp is not configured yet.
dpkg: error processing package rudder-server-root (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for systemd (232-25+deb9u1) ...
Processing triggers for rsyslog (8.24.0-1) ...
Errors were encountered while processing:
rudder-webapp
rudder-server-root
E: Sub-process /usr/bin/dpkg returned an error code (1)
no more details in the output ...
When running postinst:
# ./rudder-webapp.postinst configure
+ echo root
+ echo -n INFO: Restarting syslog...
INFO: Restarting syslog...+ service rsyslog restart
+ echo Done
Done
+ MODULES_TO_ENABLE=rewrite proxy_http headers ssl filter deflate
+ a2enmod version
+ true
+ a2enmod rewrite
+ a2enmod proxy_http
+ a2enmod headers
+ a2enmod ssl
+ a2enmod filter
+ a2enmod deflate
+ chmod 751 /var/rudder/inventories
+ chmod 755 -R /opt/rudder/share/tools
+ echo -n INFO: Restarting Apache HTTPd...
INFO: Restarting Apache HTTPd...+ service apache2 restart
root@server:/var/lib/dpkg/info# service apache2 restart
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
root@server:/var/lib/dpkg/info#
Error is in apache service
root@server:/var/lib/dpkg/info# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-01-17 09:49:40 CET; 58s ago
Process: 12174 ExecStop=/usr/sbin/apachectl stop (code=exited, status=1/FAILURE)
Process: 10134 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=1/FAILURE)
Process: 12275 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Main PID: 7161 (code=exited, status=0/SUCCESS)
Jan 17 09:49:40 server systemd[1]: Starting The Apache HTTP Server...
Jan 17 09:49:40 server apachectl[12275]: AH00526: Syntax error on line 2 of /opt/rudder/etc/rudder-networks-policy-server-24.conf:
Jan 17 09:49:40 server apachectl[12275]: ip address 'rudder' appears to be invalid
Jan 17 09:49:40 server apachectl[12275]: Action 'start' failed.
Jan 17 09:49:40 server apachectl[12275]: The Apache error log may have more information.
Jan 17 09:49:40 server systemd[1]: apache2.service: Control process exited, code=exited status=1
Jan 17 09:49:40 server systemd[1]: Failed to start The Apache HTTP Server.
Jan 17 09:49:40 server systemd[1]: apache2.service: Unit entered failed state.
Jan 17 09:49:40 server systemd[1]: apache2.service: Failed with result 'exit-code'.
root@server:/var/lib/dpkg/info#
# cat /opt/rudder/etc/rudder-networks-policy-server-24.conf
Require local
Require ip rudder
- Category changed from Packaging to System techniques
- Target version changed from 4.3.0~beta1 to 4.1.10
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1240
- Status changed from Pending technical review to Pending release
- Subject changed from Broken install for Rudder server 4.3 on Debian 9 to Rudder server installation fails if apache cannot resolve server hostname
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.
Also available in: Atom
PDF