httpd.service start failed on Nagios XI offline install

[Sundar]

We tried Nagios XI offline install on RHEL 7.X and we couldn't complete the installation with these errors. Any help to resolve this issue would be much appreciated!

# cat xi-install.log
Adding users and groups...
useradd: user 'nagios' already exists
groupadd: group 'nagios' already exists
groupadd: group 'nagcmd' already exists
Users and groups added OK
MySQL installed OK - continuing...
Starting MySQL...
Redirecting to /bin/systemctl start mariadb.service
Initializing MySQL...
MySQL root password is now set to: nagiosxi
MySQL initialized OK
Note: Forwarding request to 'systemctl disable postgresql.service'.
Database servers initialized OK
/etc/services updated
sudoers configured OK
ln -s '/dev/null' '/etc/systemd/system/firewalld.service'
ln -s '/usr/lib/systemd/system/iptables.service' '/etc/systemd/system/basic.target.wants/iptables.service'
Firewall rules updated OK
SELinux Disabled
Database backups configured OK
PHP limits configured OK
Archive: sourceguardian/ixed4.lin.x86-64.zip
inflating: /usr/lib64/php/modules/ixed.5.4.lin
Sourceguardian extension found for PHP version 5.4
Adding Sourceguardian extension to php.ini
Redirecting to /bin/systemctl restart httpd.service
Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
[root@pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6 tmp]# systemctl status httpd.service -l
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled)
Active: failed (Result: exit-code) since Tue 2016-01-19 03:08:14 EST; 4min 28s ago
Process: 19543 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 19541 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 19541 (code=exited, status=1/FAILURE)

Jan 19 03:08:14 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c httpd[19541]: AH00526: Syntax error on line 100 of /etc/httpd/conf.d/ssl.conf:Jan 19 03:08:14 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c httpd[19541]: SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or is emptyJan 19 03:08:14 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jan 19 03:08:14 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c kill[19543]: kill: cannot find process ""
Jan 19 03:08:14 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c systemd[1]: httpd.service: control process exited, code=exited status=1
Jan 19 03:08:14 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c systemd[1]: Failed to start The Apache HTTP Server.
Jan 19 03:08:14 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c systemd[1]: Unit httpd.service entered failed state.
[root@pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6 tmp]# journalctl -xn
-- Logs begin at Fri 2016-01-15 12:56:24 EST, end at Tue 2016-01-19 03:12:42 EST. --
Jan 19 03:12:12 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:12.336 1178 WARNING os_collect_config.local [
Jan 19 03:12:12 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:12.337 1178 WARNING os_collect_config.local [
Jan 19 03:12:12 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:12.337 1178 WARNING os_collect_config.zaqar [
Jan 19 03:12:42 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:42.367 1178 WARNING os-collect-config [-] Sou
Jan 19 03:12:42 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:42.486 1178 WARNING os_collect_config.ec2 [-]
Jan 19 03:12:42 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:42.486 1178 WARNING os-collect-config [-] Sou
Jan 19 03:12:42 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:42.487 1178 WARNING os-collect-config [-] Sou
Jan 19 03:12:42 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:42.487 1178 WARNING os_collect_config.local [
Jan 19 03:12:42 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:42.487 1178 WARNING os_collect_config.local [
Jan 19 03:12:42 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c os-collect-config[1178]: 2016-01-19 03:12:42.487 1178 WARNING os_collect_config.zaqar [


htttpd.service File

# cat /usr/lib/systemd/system/httpd.service
[Unit]
Description=The Apache HTTP Server
After=network.target remote-fs.target nss-lookup.target

[Service]
Type=notify
EnvironmentFile=/etc/sysconfig/httpd
ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
ExecReload=/usr/sbin/httpd $OPTIONS -k graceful
ExecStop=/bin/kill -WINCH ${MAINPID}
# We want systemd to give httpd some time to finish gracefully, but still want
# it to kill httpd after TimeoutStopSec if something went wrong during the
# graceful stop. Normally, Systemd sends SIGTERM signal right after the
# ExecStop, which would kill httpd. We are sending useless SIGCONT here to give
# httpd time to finish.
KillSignal=SIGCONT
PrivateTmp=true

[Install]
WantedBy=multi-user.target



Note:
We actually conned to this Nagios XI node via "SSH -i" from a different node as we didn't have the login credentials. Unsure if this has anything to do with this error

Regards,
Sundar

[Sundar]

We managed to create a self-signed SSL cert & key and we retried the offline installation, which resolved the error we were getting for SSL certificate. However, Apache HTTP server still doesn't get restarted with the below error

]# systemctl status httpd.service -l
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled)
Active: failed (Result: exit-code) since Tue 2016-01-19 05:37:52 EST; 2min 54s ago
Process: 8569 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 8565 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 8565 (code=exited, status=1/FAILURE)

Jan 19 05:37:52 pq-infra-001-711a62ae-xxxxxx-4d08-8242-f2d14cb648c6.ebiz.xxxxx.c httpd[8565]: AH00557: httpd: apr_sockaddr_info_get() failed for pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c
Jan 19 05:37:52 pq-infra-001-711a62ae-xxxxx-4d08-8242-f2d14cb648c6.ebiz.xxxx.c httpd[8565]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this messageJan 19 05:37:52 pq-infra-001-711a62ae-5765-4d08-8242-f2d14cb648c6.ebiz.verizon.c systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jan 19 05:37:52 pq-infra-001-711a62ae-xxxxx-4d08-8242-f2d14cb648c6.ebiz.xxxx.c kill[8569]: kill: cannot find process ""
Jan 19 05:37:52 pq-infra-001-711a62ae-xxxxx-4d08-8242-f2d14cb648c6.ebiz.xxxx.c systemd[1]: httpd.service: control process exited, code=exited status=1
Jan 19 05:37:52 pq-infra-001-711a62ae-xxxxx-4d08-8242-f2d14cb648c6.ebiz.xxxx.c systemd[1]: Failed to start The Apache HTTP Server.
Jan 19 05:37:52 pq-infra-001-711a62ae-xxxxx-4d08-8242-f2d14cb648c6.ebiz.xxxx.c systemd[1]: Unit httpd.service entered failed state.


If you notice, the hostname is really long and we don't know if that is because we use "SSH -i" option, using a key file to access the node. We also, would like to know if there is any possibility this may be more than just the "server domain name as in the error"

Also, how do we confirm if "Apache" components have been successfully installed?

As mentioned in my previous post, looks like the installation terminates at the point it tries to start Apache HTTP server. ie) installation doesn't proceed after "Adjusting PHP settings and installing the SourceGuardian PHP loaders for encrypted files" in the below sequence as we undertsood

• Modifying the yum configuration and installing prerequisite packages
• Creating required uses and groups
• Initializing PostgreSQL and MySQL databases, and set the MySQL root password to 'nagiosxi'
• Modifying sudoers and iptables to allow certain commands and traffic
• Installing backup scripts for the databases
• Adjusting PHP settings and installing the SourceGuardian PHP loaders for encrypted files
• Compiling and installing various components, including Nagios Core, the plugins, NDOUtils, PNP, webinject, etc.
• Installing the Nagios XI scripts and PHP files in /usr/local/nagiosxi
• Installing cron jobs for the root and nagios users
• Setting appropriate services to start in runlevels 3 and 5 and starting them now
• Importing base object definitions (templates, commands, etc.) into NagiosQL for use with Nagios Core
• Installing a welcome page in the root webserver directory /var/www/html

Please advise if there is any workaround for this. Thanks!

Rgds,

[hsmith]

Was your RHEL machine clean? What version of apache are you running?

Code: Select all

httpd -V

[Sundar]

When we started, it was a clean VM.

Apache Version is 2.4.6

[Sundar]

Somehow we managed to het the Apache HTTP Server started. However, we get the below error when we ran the install again "path too long"

.
.
Intsall complete.
Nagios XI based files installed OK
path too long

When we try to access Nagios XI portal, it throws 403 error.

[Sundar]

Just to add .....“path too long” error comes which it tries to initialize apache crontab.

It seems to be using the below command

crontab -u $apacheuser nagiosxi/crontab.apache

If anyone has encountered similar issue on RHEL 7.X offline install and have a workaround please let us know. Thanks

[hsmith]

Can you attach the upgrade.log to this post for us to take a look at?