CPU use for httpd peaks when setting scheduled downtime

[awilson]

Hi. I've noticed that 4 times out of 5, the http utilization for httpd pins around 90% for a few minutes when we attempt to select servers to add to the list. We are not able to complete the configuring task. The browser just times out. Other times, it just works properly. Are there guidelines for adjustments that may ease the performance pressure?

Code: Select all

Nagios XI - System Info
System:
Nagios XI Version : 5.4.4
lussvpnagxi00.fossil.com 2.6.32-754.2.1.el6.x86_64 x86_64
Red Hat Enterprise Linux Server release 6.10 (Santiago)
Gnome is not installed
Apache Information
PHP Version: 5.3.3
Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Server Name: 10.10.83.90
Server Address: 10.10.83.90
Server Port: 80
Date/Time
PHP Timezone: America/Chicago 
PHP Time: Thu, 09 Aug 2018 18:42:48 -0500
System Time: Thu, 09 Aug 2018 18:42:48 -0500
Nagios XI Data
License ends in: xxxx

nagios (pid 3662) is running...
NPCD running (pid 3990).
ndo2db (pid 3102) is running...
CPU Load 15: 1.79 
Total Hosts: 1135 
Total Services: 17421 
Function 'get_base_uri' returns: http://10.10.83.90/nagiosxi/
Function 'get_base_url' returns: http://10.10.83.90/nagiosxi/
Function 'get_backend_url(internal_call=false)' returns: http://10.10.83.90/nagiosxi/includes/components/profile/profile.php
Function 'get_backend_url(internal_call=true)' returns: http://localhost/nagiosxi/backend/
Ping Test localhost
Running:
/bin/ping -c 3 localhost 2>&1 
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.175 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.124 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.166 ms

--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.124/0.155/0.175/0.022 ms
Test wget To localhost
WGET From URL: http://localhost/nagiosxi/includes/components/ccm/ 
Running:
/usr/bin/wget http://localhost/nagiosxi/includes/components/ccm/ 
--2018-08-09 18:42:50-- http://localhost/nagiosxi/includes/components/ccm/
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://localhost/nagiosxi/login.php?redirect=/nagiosxi/includes/components/ccm/index.php%3f&noauth=1 [following]
--2018-08-09 18:42:50-- http://localhost/nagiosxi/login.php?redirect=/nagiosxi/includes/components/ccm/index.php%3f&noauth=1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: "/usr/local/nagiosxi/tmp/ccm_index.tmp"

0K .......... .......... ..... 1.38M=0.02s

2018-08-09 18:42:50 (1.38 MB/s) - "/usr/local/nagiosxi/tmp/ccm_index.tmp" saved [26501]

Network Settings
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host 

       valid_lft forever preferred_lft forever

2: eth0:  mtu 1500 qdisc mq state UP qlen 1000

    link/ether 00:50:56:b8:4b:43 brd ff:ff:ff:ff:ff:ff

    inet 10.10.83.90/24 brd 10.10.83.255 scope global eth0

    inet6 fe80::250:56ff:feb8:4b43/64 scope link 

       valid_lft forever preferred_lft forever


10.10.83.0/24 dev eth0  proto kernel  scope link  src 10.10.83.90 

169.254.0.0/16 dev eth0  scope link  metric 1002 

default via 10.10.83.1 dev eth0 

I can PM the profile if it would help.

Thanks.

[cdienger]

The number of checks and services on the machine is getting up there. I would recommend increasing the values for the settings mentioned in https://support.nagios.com/kb/article/n ... e-611.html(quadruple the defaults). A lot of time can be spent by the apache service just writing to disk when you apply the config, so anything that can be done to make that quicker will help. If you haven't already, check out https://assets.nagios.com/downloads/nag ... ios-XI.pdf and setting up a RAM disk.