Nagios Support Forum

Hi There,

Am trying to upgrade the HTTPD version of the Server where Nagios has been Installed & running and Below is my Server Configuration:

CentOS version: CentOS Linux release 7.8.2003 (Core)
Nagios Version: NagiosXI - 5.6.13
PHP version: 7.3.29
Httpd Version: Apache/2.4.6 (CentOS)

I've tried upgrading HTTPD to recent version (2.4.48) from current version (2.4.6), but after upgrading Nagios is Not up and running and systemctl status nagios shows Unit Nagios.service not found!

My Nagios Installation was done via Offline Tarball and recently I've updated the PHP from 5.4.16 to 7.3.29 version .

Kindly let me know the Processes/Steps that I need to follow to upgrade my HTTPD and inform if any HTTPD Version restrictions apply for the Nagios version that am using.

Also advice if upgrading method differs for Offline Nagios Installation from direct source (web) Installation, as am also looking forward to update HTTPD on a server that has Nagios Installed directly from online source.

Hi,

Sorry your system is down due to the upgrade.

First, look in: /etc/systemd/system/multi-user.target.wants - is there a nagios.service file there?

Secondly - what steps did you take to update your httpd ? I will use them to try
and replicate your problem.

Thanks

Hi,
I've been following the instructions mentioned on official APACHE Website to Install the HTTPD (https://httpd.apache.org/docs/current/install.html).

As Mentioned on it, I've Downloaded the latest httpd release (2.4.48) from http://httpd.apache.org/download.cgi and executed the following commands:

$ gzip -d httpd-2.4.48.tar.gz
$ tar xvf httpd-2.4.48.tar
$ cd httpd-2.4.48
$ ./configure --prefix=PREFIX
$ make
$ make install
$ vi PREFIX/conf/httpd.conf
$ PREFIX/bin/apachectl -k start

and my Prefix was set to: /etc/httpd

I got errors for Missing dependencies with apr & apr-util and I've downloaded installed latest version (apr-1.7.0.tar.gz & apr-util-1.6.1.tar.gz) of those from (http://apr.apache.org/download.cgi#apr1). The Make and Make Install commands executed fine.

But After the Upgrade, when I restart the httpd, it shows It couldn't restart the service and systemctl status httpd.service returns "httpd is not active & running" & Got the below error messages
(Failed to start the Apache httpd server. Unit httpd.service entered the failed state)

The /etc/systemd/system/multi-user.target.wants command has a nagios.service file (content in nagios.service.PNG attachment) with the location /usr/lib/systemd/system/nagios.service.

Kindly assist if there's any correction needed in the process that I've tried.

Hi,

Take a look at the log files in /var/log/httpd and see if they shed any light
on why Apache won't start.

Thanks

Hi gsmith,

Herewith I've enclosed the HTTPD Error & Access logs from /var/log/httpd and I'm not able to assess exactly whats the background of this issue.

httpd -t command returned the below error:

httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Syntax error on line 6 of /etc/httpd/conf.modules.d/00-base.conf: Cannot load modules/mod_access_compat.so into server: /etc/httpd/modules/mod_access_compat.so: undefined symbol: ap_get_useragent_host

Enclosed httpd.conf, 00-base.conf &nagios.conf for your reference

It'll be much helpful if you could replicate the HTTPD Upgrade on your end and let me know the correct process/Instruction Commands to follow.

FYI, My Current Configuration is:

CentOS version: CentOS Linux release 7.8.2003 (Core)
Nagios Version: NagiosXI - 5.6.13
PHP version: 7.3.29
Httpd Version: Apache/2.4.6 (CentOS)

HTTPD 2.4.48 version I'm trying to get on my machine!

Kindly assist!

Hi,

Here is what I found:

UPDATE I compiled my findings and submitted a bug report to the Apache devs. They suggested the server needed a full stop and start because some components were still in memory after the upgrade. I tested again and the graceful reload worked fine -- without replacing the module -- on the production servers. So, apparently this is a one-time bite you bug within the actual upgrade process because it should stop/start instead of restart the server. For anyone else who may experience this; just stop the server and start it again.

Here's the bug report I filed (I expect it to be marked as a non-bug really): https://bz.apache.org/bugzilla/show_bug.cgi?id=59842

- it came from https://serverfault.com/questions/78079 ... ul-restart

So please try: Thanks