Nagios Support Forum

ericssonvietnam wrote:

lmiltchev wrote:Try doubling the value:

Code: Select all

upload_max_filesize = 4M

then restart apache:

Code: Select all

service httpd restart

Let us know if this helped.

Got the message apr_sockaddr_info_get() failed for nagiosxi which i do not usually get after restarting httpd service can you suggest.

[root@nagiosxi NEWMIBS]# service httpd restart
Stopping httpd: [ OK ]
Starting httpd: httpd: apr_sockaddr_info_get() failed for nagiosxi
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[ OK ]

But still status is running for httpd


I which configuration file should i check for the processed mibs.
I have the below configuration in the ini file /etc/snmp/snmptt.ini
[TrapFiles]
# A list of snmptt.conf files (this is NOT the snmptrapd.conf file). The COMPLETE path
# and filename. Ex: '/etc/snmp/snmptt.conf'
snmptt_conf_files = <<END
/etc/snmp/VNM_snmptt.conf
END

Do i require to restart the snmptt service

dwhitfield wrote:First step, are they showing up at http://YOURSERVER/nagiosxi/admin/mibs.php ?

The quickest thing to do, assuming you have a test device and test server, is just to test it and see if it works as anticipated. Please note that each XI install allows for both a test and a backup instance, so there's no reason why you shouldn't be able to test on the XI side.

tgriep wrote:It looks like the SNMPv2-SMI mib file is corrupted as the 'zeroDotZero' option is defined in that file.
Can you run the following as root and post the output so we can see the files in that folder are correct?

Code: Select all

ls -l /usr/share/snmp/mibs

tgriep wrote:There are a lot of files that have been uploaded to the server and I am guessing that some of them do not have the required SNMP definitions and that is causing the errors.
When you need to upload a MIB file, for the most part, you do not want to upload over an existing file or a file with a similar name but with different contents as that will generate the errors you are having.

In that folder, are many copies of this file (slightly different name) and the settings in one of them are bad causing the error.

Code: Select all

-rw-rw-r-- 1 root nagios    8932 Jun 30 01:09 SNMPv2-SMI
-rw-rw-r-- 1 root nagios     744 Jun 13  2016 snmpv2-smi.cfg
-rw-rw-r-- 1 root nagios    1398 May 15 21:17 SNMPv2-SMI.mib
-rw-rw-r-- 1 root nagios    8924 Jan 20  2016 SNMPv2-SMI.txt
-rw-rw-r-- 1 root nagios     666 Jun 13  2016 SNMPv2-SMI-v1.cfg
-rw-rw-r-- 1 root nagios    1414 May 15 21:17 SNMPv2-SMI-v1.mib

To fix this, delete all of the above files except this one

Code: Select all

-rw-rw-r-- 1 root nagios    8924 Jan 20  2016 SNMPv2-SMI.txt

There are also a lot of .cfg files in the folder, you should look at them to see if they are valid and it not, remove them as well.

tgriep wrote:1. There are a couple of ways you can create your custom files, run the addmib command which will add them to the default file and then you can rename it.
Or you can edit the /usr/local/bin/addmib script and change the name of the output file.

Code: Select all

cmd='/usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*"'
snmpttconvertmib --in="$1" --out=/etc/snmp/VNM_snmptt.conf \
        --exec "$cmd" >> /tmp/snmpttconvertmib.log

You will have to edit the /etc/snmp/snmptt.ini file and add the custom file to the list at the bottom so the snmptt daemon will load it.

2. Not all MIB files contain TRAP entries so if the files you added did not have any, then there is nothing to import.

3. The DISMAN-EVENT-MIB and the NOTIFICATION-LOG-MIB MIB files look like they were replaced on the system.
Delete this copy of the NOTIFICATION-LOG-MIB file. The without the .txt extension
Then delete the DISMAN-EVENT-MIB file and replace it with the one that is attached to the post.