Nagios upgrade from 3 to 4.3.1 -a lot of issues

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
dsnagi
Posts: 14
Joined: Mon Mar 13, 2017 8:53 pm

Re: Nagios upgrade from 3 to 4.3.1 -a lot of issues

Post by dsnagi »

Content of my commands.cfg file is here below:

Code: Select all

###############################################################################
# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS 3.4.4
#
# 
#
# NOTES: This config file provides you with some example command definitions
#        that you can reference in host, service, and contact definitions.
#       
#        You don't need to keep commands in a separate file from your other
#        object definitions.  This has been done just to make things easier to
#        understand.
#
###############################################################################


################################################################################
#
# SAMPLE NOTIFICATION COMMANDS
#
# These are some example notification commands.  They may or may not work on
# your system without modification.  As an example, some systems will require 
# you to use "/usr/bin/mailx" instead of "/usr/bin/mail" in the commands below.
#
################################################################################


# 'notify-host-by-email' command definition
#define command{
#	command_name	notify-host-by-email
#	command_line	/usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$ -- -r user-name@domain-name.top-level-domain
#	}

# 'notify-service-by-email' command definition
#define command{
#	command_name	notify-service-by-email
#	command_line	/usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time:$LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$ -- -r user-name@domain name.top-level-domain
#	}

define command{
      command_name    notify-host-by-email
      command_line    /usr/bin/php -q /usr/local/nagios/libexec/nagios_mail.php
      }

define command{
      command_name    notify-service-by-email
      command_line    /usr/bin/php -q /usr/local/nagios/libexec/nagios_mail.php
      }



################################################################################
#
# SAMPLE HOST CHECK COMMANDS
#
################################################################################


# This command checks to see if a host is "alive" by pinging it
# The check must result in a 100% packet loss or 5 second (5000ms) round trip 
# average time to produce a critical error.
# Note: Five ICMP echo packets are sent (determined by the '-p 5' argument)

# 'check-host-alive' command definition
define command{
        command_name    check-host-alive
        command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% -p 5
        }




################################################################################
#
# SAMPLE SERVICE CHECK COMMANDS
#
# These are some example service check commands.  They may or may not work on
# your system, as they must be modified for your plugins.  See the HTML 
# documentation on the plugins for examples of how to configure command definitions.
#
# NOTE:  The following 'check_local_...' functions are designed to monitor
#        various metrics on the host that Nagios is running on (i.e. this one).
################################################################################

# 'check_local_disk' command definition
define command{
        command_name    check_local_disk
        command_line    $USER1$/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
        }


# 'check_local_load' command definition
define command{
        command_name    check_local_load
        command_line    $USER1$/check_load -w $ARG1$ -c $ARG2$
        }


# 'check_local_procs' command definition
define command{
        command_name    check_local_procs
        command_line    $USER1$/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$
        }


# 'check_local_users' command definition
define command{
        command_name    check_local_users
        command_line    $USER1$/check_users -w $ARG1$ -c $ARG2$
        }


# 'check_local_swap' command definition
define command{
	command_name	check_local_swap
	command_line	$USER1$/check_swap -w $ARG1$ -c $ARG2$
	}


# 'check_local_mrtgtraf' command definition
define command{
	command_name	check_local_mrtgtraf
	command_line	$USER1$/check_mrtgtraf -F $ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -e $ARG5$
	}


################################################################################
# NOTE:  The following 'check_...' commands are used to monitor services on
#        both local and remote hosts.
################################################################################

# 'check_ftp' command definition
define command{
        command_name    check_ftp
        command_line    $USER1$/check_ftp -H $HOSTADDRESS$ $ARG1$
        }


# 'check_hpjd' command definition
define command{
        command_name    check_hpjd
        command_line    $USER1$/check_hpjd -H $HOSTADDRESS$ $ARG1$
        }


# 'check_snmp' command definition
define command{
        command_name    check_snmp
        command_line    $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
        }


# 'check_http' command definition
define command{
        command_name    check_http
        command_line    $USER1$/check_http -I $HOSTADDRESS$ $ARG1$
        }


# 'check_ssh' command definition
define command{
	command_name	check_ssh
	command_line	$USER1$/check_ssh $ARG1$ $HOSTADDRESS$
	}


# 'check_dhcp' command definition
define command{
	command_name	check_dhcp
	command_line	$USER1$/check_dhcp $ARG1$
	}


# 'check_ping' command definition
define command{
        command_name    check_ping
        command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5
        }


# 'check_pop' command definition
define command{
        command_name    check_pop
        command_line    $USER1$/check_pop -H $HOSTADDRESS$ $ARG1$
        }


# 'check_imap' command definition
define command{
        command_name    check_imap
        command_line    $USER1$/check_imap -H $HOSTADDRESS$ $ARG1$
        }


# 'check_smtp' command definition
define command{
        command_name    check_smtp
        command_line    $USER1$/check_smtp -H $HOSTADDRESS$ $ARG1$
        }


# 'check_tcp' command definition
define command{
	command_name	check_tcp
	command_line	$USER1$/check_tcp -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
	}


# 'check_udp' command definition
define command{
	command_name	check_udp
	command_line	$USER1$/check_udp -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
	}


# 'check_nt' command definition
define command{
	command_name	check_nt
	command_line	$USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -v $ARG1$ $ARG2$
	}



################################################################################
#
# SAMPLE PERFORMANCE DATA COMMANDS
#
# These are sample performance data commands that can be used to send performance
# data output to two text files (one for hosts, another for services).  If you
# plan on simply writing performance data out to a file, consider using the 
# host_perfdata_file and service_perfdata_file options in the main config file.
#
################################################################################


# 'process-host-perfdata' command definition
#define command{
#	command_name	process-host-perfdata
#	command_line	/usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /usr/local/nagios/var/host-perfdata.out
#	}


# 'process-service-perfdata' command definition
#define command{
#	command_name	process-service-perfdata
#	command_line	/usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /usr/local/nagios/var/service-perfdata.out
#	}

define command{
       command_name    process-service-perfdata-file
       command_line    /bin/mv /usr/local/pnp4nagios/var/service-perfdata /usr/local/pnp4nagios/var/spool/service-perfdata.$TIMET$
}

define command{
       command_name    process-host-perfdata-file
       command_line    /bin/mv /usr/local/pnp4nagios/var/host-perfdata /usr/local/pnp4nagios/var/spool/host-perfdata.$TIMET$
}


#1 

define command {
	command_name	check_interface_table
command_line	/usr/bin/perl /usr/local/nagios/libexec/check_interface_table_v3t.pl -h $HOSTNAME$ -C public -H $HOSTADDRESS$ -f --cp 1 --tp='ifOperStatus' --alias --ipinfo
}


define command {
	command_name	check_icmp
	command_line	$USER1$/check_icmp $ARG1
	}

define command {
        command_name    check_dns
        command_line    $USER1$/check_dns $HOSTNAME$
        }
It seems that "/usr/local/nagios/libexec/nagios_mail.php" is the place where I need to look for fixing broken link, but I cannot even find anything related to "details" in that file (nagios_mail.php).


For email body link problem please take a look at the picture in attachment. Clicking on "details" link nothing happen. All other hyperlinks in email body work ok.
Attachments
email_body_link.JPG
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Nagios upgrade from 3 to 4.3.1 -a lot of issues

Post by tgriep »

I found a copy of the nagios_mail.php online and there is nothing in there about the [details] link.
In your example, it does look like you are getting the correct output.
Maybe if the service or host output is larger, you would have to click on that link but since the data is displayed fully, you don't need to.
Be sure to check out our Knowledgebase for helpful articles and solutions!
dsnagi
Posts: 14
Joined: Mon Mar 13, 2017 8:53 pm

Re: Nagios upgrade from 3 to 4.3.1 -a lot of issues

Post by dsnagi »

Yes, there is nothing in nagios_mail.php about the [details] link.

So how can I find out the source of [details] link?
What is feeding my email body with [details] link?

I can see in my nagios_mail.php this section:

Code: Select all

  $output_html[] = '<div style="background-color:#CCC;padding:5px;clear:both;">';
  $output_html[] = '<div style="font-weight:bold;">';
  $output_html[] = $this->str_info;
  $output_html[] = '</div>';
It seems that "$this->str_info;" could be a source of [details] link.

Yes tgriep I agree with you that output in the email body already has plenty of information, but they want fixed details link.
They had that link functional before upgrade, so ... my only option is to fix that :) .
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Nagios upgrade from 3 to 4.3.1 -a lot of issues

Post by tgriep »

I don't know where the [details] link is coming from, it may be something that the email client is adding.
If you view the source details of the email, you may be able to find out where it is coming from and go from there.
If you still have access to an older email with a working link, where did it go to?
Be sure to check out our Knowledgebase for helpful articles and solutions!
dsnagi
Posts: 14
Joined: Mon Mar 13, 2017 8:53 pm

Re: Nagios upgrade from 3 to 4.3.1 -a lot of issues

Post by dsnagi »

Good tip tgriep,
This is the link from old email:
http://NagiosHostName/interfacetable_v3t/tables/CiscoSwitchHostName-Interfacetable.html

Of course original link has real nagios and cisco switch host names.

Tgriep, all others, do you think that interfacetable_v3t have something with link creation?
I think something else creates those links, not intefacetable_v3t, not sure :?
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Nagios upgrade from 3 to 4.3.1 -a lot of issues

Post by tgriep »

It looks like you will have to re-setup the Interfacetable_v3t plugin on your server to fix that.
Take a look at this link for instructions.
http://www.tontonitch.com/tiki/tiki-ind ... etable_v3t
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked