Blog
- Home
- Blog
Host Still Visible After Deletion in Nagios - How to resolve ?
This article covers steps to resolve Host Still Visible After Deletion (Ghost Hosts). Basically, by following this guide, you can easily resolve the error, Host Still Visible After Deletion in Nagios.
It is possible that you have multiple instances of nagios running or you have so called "ghost" hosts or services.
In order to check for multiple instances of nagios, run the following command from the command line:
$ ps -ef | head -1 && ps -ef | grep bin/nagios
Problems Using Nagios With Proxies - Fix it Now ?
This article covers how to resolve Problems Using Nagios With Proxies which arises if we do not configure proxies correctly while using Nagios.
Note that the Nagios XI code makes several internal HTTP calls to the local Nagios XI server to import configuration data, apply configuration changes, process AJAX requests, etc.
These functions may not work properly when you deploy a proxy if it is not configured properly, which could result in a non-functional Nagios XI installation.
Migrate Performance Data in Nagios - Step by Step Process ?
This article covers how to perform Migrate Performance Data in Nagios.
Basically, to migrate, we have to convert the data to XML and import it into RRD’s on the new machine.
Historical performance data that is used to generate graphs are stored in Round Robin Database (RRD) files.
RRD performance data files are compiled binaries, so for a simple file transfer a user would have to have the architecture match on both machines.
Nagios mysql_error out of range value for column - Fix it now ?
This article covers Nagios error, mysql_error out of range value for column which is evident in the /var/log/messages file on the Nagios XI server.
To resolve this issue you will need to define the SQL Mode in the MySQL / MariaDB my.cnf configuration file:
1. Locate the [mysqld] section and check to see if there is an sql_mode already defined:
[mysqld]
# Recommended in standard MySQL setup
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
2. If the sql_mode= line already exists you will need to replace it with the following.
If the line does not exist you will need to add the following line:
[mysqld]
sql_mode=""
Prestashop error "an error occurred while sending the message" - Fix it Now ?
This article covers methods to fix Prestashop error "an error occurred while sending the message".
This error happens when the theme that we use does not adapt to the latest version of Prestashop.
To resolve this error, you can try modifying the contact form file.
Add this before the submit button :
<style>
input[name=url] {
display: none !important;
}
</style>
<input type="text" name="url" value=""/>
<input type="hidden" name="token" value="{$token}" />
Can't connect to mysql error 111 - Fix this error now ?
This article covers methods to fix mysql error, 'Can't connect to mysql error 111' on Linux machine for our customers.
This can happen when there was a host IP change.
This issue can prevent connection to the database.
As it turned out if you do come accross this look in /etc/my.cnf, there is a line:
bind-address = ip.add.ress
This may be the old address for the server and this will stop connections, change this to your new address and restart MySQL/MariaDB and you should be good again.
