Nagios Support Forum

dwhitfield wrote:I think this will help out: https://assets.nagios.com/downloads/nag ... ios-XI.pdf

Also, can you PM me your Profile? You can download it by going to Admin > System Config > System Profile and click the ***Download Profile*** button towards the top. If for whatever reason you *cannot* download the profile, please put the output of View System Info (5.3.4+, Show Profile if older) in the thread (that will at least get us some info). This will give us access to many of the logs we would otherwise ask for individually. If security is a concern, you can unzip the profile take out what you like, and then zip it up again. We may end up needing something you remove, but we can ask for that specifically.

After you PM the profile, please update this thread. Updating this thread is the only way for it to show back up on our dashboard.

s.wiki wrote:, should i implement all of them for this issue?

May 24 14:24:49 localhost ndo2db: mysql_error: 'Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed'

dwhitfield wrote:

s.wiki wrote:, should i implement all of them for this issue?

It's hard to say. It really depends on if your disks are faster than your network. If you are on an SSD, then they probably are. If you offload your db to a VM cluster on the same physical disks, then the offloading is not likely to help.

It also depends on what is going on on the system at the time you log in.

If I were you, the first thing I would start with is the ramdisk and see if you see any improvement. After that, I'd go to any non-critical services that are being monitored and increase the check interval. Fewer checks, means better performance.

You also have some database issues which may be causing some problems. Probably, you should start a new thread for the database issues though. I'm seeing several of the following:

Code: Select all

May 24 14:24:49 localhost ndo2db: mysql_error: 'Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed'

tgriep wrote:Lets increase the memory and timeout values that PHP uses and see if that helps the performance while logging in as the nagiosadmin account.
Edit the /etc/php.ini file and change the following from

Code: Select all

max_execution_time = 30
max_input_time = 60
memory_limit = 128M

to

Code: Select all

max_execution_time = 60
max_input_time = 120
memory_limit = 512M

Then add this to the bottom of that file

Code: Select all

max_input_vars=5000

Save the file and restart Apache for the changes to take affect.

Code: Select all

service httpd restart

Try that and see if it decreases the login time to the GUI.

tgriep wrote:First thing, if the Vagios server's FQDN is not setup on your DNS server, add it to DNS or add an entry in the /etc/hosts file like the example below

Code: Select all

192.168.248.175 imsvm.abc.bank.my imsvm

To resolve this message

Code: Select all

Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.248.175 for ServerName

You can add the FQDN to the Apache main configuration file.
Edit the /etc/httpd/conf/httpd.conf file and find the following line and change it from

Code: Select all

#ServerName www.example.com:80

to

Code: Select all

ServerName imsvm.abc.bank.my

Save the file and restart apache by running

Code: Select all

service httpd restart

That way, the Apache Server will know the name at start up but I think the changes to the /etc/hosts file should fix this as well.