hai friends
i configured nagios with otrs according to pdf which is in this link
http://otrs-forum.net/media/nagios_conf ... 008_en.pdf
after i restart the nagios service i'm getting null as a status for otrs in nagios web interface.
Service State Information
Current Status:
WARNING
(for 0d 22h 32m 21s)
Status Information: (null)
Performance Data:
Current Attempt: 4/4 (HARD state)
Last Check Time: 09-07-2012 16:15:21
Check Type: ACTIVE
Check Latency / Duration: 0.100 / 0.433 seconds
Next Scheduled Check: 09-07-2012 16:20:21
Last State Change: 09-06-2012 17:46:01
Last Notification: 09-07-2012 15:54:51 (notification 23)
Is This Service Flapping?
NO
(0.00% state change)
In Scheduled Downtime?
NO
Last Update: 09-07-2012 16:18:18 ( 0d 0h 0m 4s ago)
please provide some solution for this problem
thanks in advance
how to resolve null error
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: how to resolve null error
When you run the check command from your Nagios system's terminal, what does it return?
Re: how to resolve null error
when i run the command, in the nagios log file it showing this error
nagiosadmin;localhost;OTRS Number of Tickets;WARNING;notify-service-by-email;(null)
command line of notify-service-by-email
/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" | /usr/bin/mailx -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$ | /usr/bin/mailx -s
nagiosadmin;localhost;OTRS Number of Tickets;WARNING;notify-service-by-email;(null)
command line of notify-service-by-email
/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" | /usr/bin/mailx -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$ | /usr/bin/mailx -s
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: how to resolve null error
Hello,
Can you try removing the extra pipe here:
So the end would be:
What the logfile is telling you is it was run, that is not an error.
Can you try removing the extra pipe here:
Code: Select all
$CONTACTEMAIL$ | /usr/bin/mailx -sCode: Select all
$CONTACTEMAIL$
Re: how to resolve null error
even though i remove that pipe ,i'm getting the same (null)error.
in error log i am getting this message
" SERVICE NOTIFICATION: nagiosadmin;CRITICAL;notify-service-by-email;(null)"
Current Status: CRITICAL (for 0d 0h 15m 29s)
Status Information: (null)
Performance Data:
Current Attempt: 3/3 (HARD state)
Last Check Time: 09-14-2012 19:57:17
Check Type: ACTIVE
Check Latency / Duration: 0.089 / 0.002 seconds
in error log i am getting this message
" SERVICE NOTIFICATION: nagiosadmin;CRITICAL;notify-service-by-email;(null)"
Current Status: CRITICAL (for 0d 0h 15m 29s)
Status Information: (null)
Performance Data:
Current Attempt: 3/3 (HARD state)
Last Check Time: 09-14-2012 19:57:17
Check Type: ACTIVE
Check Latency / Duration: 0.089 / 0.002 seconds