LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 07-27-2010, 04:10 AM   #1
Xanios
Member
 
Registered: Jul 2010
Posts: 216

Rep: Reputation: 30
nagiosgrapher in ubuntu 9.10


hello.

i tried to configure nagiosgrapher by following this guide:http://www.heuers.org/wp/?p=64. i managed to do finish all the steps listed but i ain't getting the nagiosgrapher icon to appear beside the services on the browser?

whats wrong.
 
Old 07-27-2010, 11:55 AM   #2
sem007
Member
 
Registered: Nov 2006
Distribution: RHEL, CentOS, Debian Lenny, Ubuntu
Posts: 638

Rep: Reputation: 113Reputation: 113
Hi Xanios,

can you provide some more info?
1) had you get any error or missing package error?

paste output of below commands

ls -la /usr/local/nagios/var
cat /usr/local/nagios/var/ngraph.log
cat /usr/local/nagios/etc/nagios.cfg

Last edited by sem007; 07-27-2010 at 11:58 AM.
 
Old 07-27-2010, 09:15 PM   #3
Xanios
Member
 
Registered: Jul 2010
Posts: 216

Original Poster
Rep: Reputation: 30
Hi,

Nope, there isn't any missing packages. When i ran those commands, all are 'found'.

ls -la /usr/local/nagios/var
Code:
xanios@ubuntu:~$ ls -la /usr/local/nagios/var
total 4492
drwxrwxr-x  7 nagios nagios    4096 2010-07-27 17:27 .
drwxr-xr-x 10 root   root      4096 2010-07-27 00:55 ..
drwxrwxr-x  2 nagios nagios    4096 2010-07-27 00:00 archives
drwxr-xr-x  2 root   root      4096 2010-07-27 00:55 nagios_grapher
-rw-r--r--  1 nagios nagios       6 2010-07-27 00:59 nagios.lock
-rw-r--r--  1 nagios nagios   75356 2010-07-27 17:27 nagios.log
-rw-r--r--  1 root   root     86016 2010-07-26 18:01 .nagios.log.swp
-rw-r--r--  1 nagios root         0 2010-07-27 00:55 ngraph.log
-rw-r--r--  1 nagios nagios   49842 2010-07-27 01:03 objects.cache
-rw-------  1 nagios nagios   73636 2010-07-27 17:03 retention.dat
drwxr-xr-x  2 nagios root      4096 2010-07-27 00:55 rrd
drwxrwsr-x  2 nagios nagcmd    4096 2010-07-27 00:59 rw
-rw-rw-r--  1 nagios nagios 4189898 2010-07-27 17:27 service-perfdata.out
drwxr-xr-x  3 root   root      4096 2010-07-11 18:11 spool
-rw-rw-r--  1 nagios nagios   74521 2010-07-27 17:27 status.dat
Hmm, what is 'cat' in the command? I used 'sudo'.
And i got this:
Code:
xaniosg@ubuntu:~$ sudo /usr/local/nagios/var/ngraph.log
[sudo] password for xanios: 
sudo: /usr/local/nagios/var/ngraph.log: command not found
If i used 'cat' instead of 'sudo', there isn't any output:
Code:
xanios@ubuntu:~$ cat /usr/local/nagios/var/ngraph.log
xanios@ubuntu:~$
For 'cat /usr/local/nagios/etc/nagios.cfg':

Code:
# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
# These commands are run after every host and service check is
# performed.  These commands are executed only if the
# enable_performance_data option (above) is set to 1.  The command
# argument is the short name of a command definition that you 
# define in your host configuration file.  Read the HTML docs for
# more information on performance data.

#host_perfdata_command=process-host-perfdata
service_perfdata_command=process-service-perfdata



# HOST AND SERVICE PERFORMANCE DATA FILES
# These files are used to store host and service performance data.
# Performance data is only written to these files if the
# enable_performance_data option (above) is set to 1.

#host_perfdata_file=/tmp/host-perfdata
service_perfdata_file=/tmp/service-perfdata



# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
# These options determine what data is written (and how) to the
# performance data files.  The templates may contain macros, special
# characters (\t for tab, \r for carriage return, \n for newline)
# and plain text.  A newline is automatically added after each write
# to the performance data file.  Some examples of what you can do are
# shown below.

#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$

service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$



# HOST AND SERVICE PERFORMANCE DATA FILE MODES
# This option determines whether or not the host and service
# performance data files are opened in write ("w") or append ("a")
# mode. If you want to use named pipes, you should use the special
# pipe ("p") mode which avoid blocking at startup, otherwise you will
# likely want the defult append ("a") mode.

#host_perfdata_file_mode=a

service_perfdata_file_mode=a



# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
# These options determine how often (in seconds) the host and service
# performance data files are processed using the commands defined
# below.  A value of 0 indicates the files should not be periodically
# processed.

#host_perfdata_file_processing_interval=0


service_perfdata_file_processing_interval=30



# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
# These commands are used to periodically process the host and
# service performance data files.  The interval at which the
# processing occurs is determined by the options above.

#host_perfdata_file_processing_command=process-host-perfdata-file

service_perfdata_file_processing_command=process-service-perfdata-file



# OBSESS OVER SERVICE CHECKS OPTION
# This determines whether or not Nagios will obsess over service
# checks and run the ocsp_command defined below.  Unless you're
# planning on implementing distributed monitoring, do not enable
# this option.  Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over services, 0 = do not obsess (default)

obsess_over_services=0



# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
# This is the command that is run for every service check that is
# processed by Nagios.  This command is executed only if the
# obsess_over_services option (above) is set to 1.  The command 
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ocsp_command=somecommand



# OBSESS OVER HOST CHECKS OPTION
# This determines whether or not Nagios will obsess over host
# checks and run the ochp_command defined below.  Unless you're
# planning on implementing distributed monitoring, do not enable
# this option.  Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over hosts, 0 = do not obsess (default)

obsess_over_hosts=0



# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
# This is the command that is run for every host check that is
# processed by Nagios.  This command is executed only if the
# obsess_over_hosts option (above) is set to 1.  The command 
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ochp_command=somecommand



# TRANSLATE PASSIVE HOST CHECKS OPTION
# This determines whether or not Nagios will translate
# DOWN/UNREACHABLE passive host check results into their proper
# state for this instance of Nagios.  This option is useful
# if you have distributed or failover monitoring setup.  In
# these cases your other Nagios servers probably have a different
# "view" of the network, with regards to the parent/child relationship
# of hosts.  If a distributed monitoring server thinks a host
# is DOWN, it may actually be UNREACHABLE from the point of
# this Nagios instance.  Enabling this option will tell Nagios
# to translate any DOWN or UNREACHABLE host states it receives
# passively into the correct state from the view of this server.
# Values: 1 = perform translation, 0 = do not translate (default)

translate_passive_host_checks=0



# PASSIVE HOST CHECKS ARE SOFT OPTION
# This determines whether or not Nagios will treat passive host
# checks as being HARD or SOFT.  By default, a passive host check
# result will put a host into a HARD state type.  This can be changed
# by enabling this option.
# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT

passive_host_checks_are_soft=0



# ORPHANED HOST/SERVICE CHECK OPTIONS
# These options determine whether or not Nagios will periodically 
# check for orphaned host service checks.  Since service checks are
# not rescheduled until the results of their previous execution 
# instance are processed, there exists a possibility that some
# checks may never get rescheduled.  A similar situation exists for
# host checks, although the exact scheduling details differ a bit
# from service checks.  Orphaned checks seem to be a rare
# problem and should not happen under normal circumstances.
# If you have problems with service checks never getting
# rescheduled, make sure you have orphaned service checks enabled.
# Values: 1 = enable checks, 0 = disable checks

check_for_orphaned_services=1
check_for_orphaned_hosts=1



# SERVICE FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of service results.  Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_service_freshness=1



# SERVICE FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of service check results.  If you have
# disabled service freshness checking, this option has no effect.

service_freshness_check_interval=60



# HOST FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of host results.  Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_host_freshness=0



# HOST FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of host check results.  If you have
# disabled host freshness checking, this option has no effect.

host_freshness_check_interval=60




# ADDITIONAL FRESHNESS THRESHOLD LATENCY
# This setting determines the number of seconds that Nagios
# will add to any host and service freshness thresholds that
# it calculates (those not explicitly specified by the user).

additional_freshness_latency=15




# FLAP DETECTION OPTION
# This option determines whether or not Nagios will try
# and detect hosts and services that are "flapping".  
# Flapping occurs when a host or service changes between
# states too frequently.  When Nagios detects that a 
# host or service is flapping, it will temporarily suppress
# notifications for that host/service until it stops
# flapping.  Flap detection is very experimental, so read
# the HTML documentation before enabling this feature!
# Values: 1 = enable flap detection
#         0 = disable flap detection (default)

enable_flap_detection=1



# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
# Read the HTML documentation on flap detection for
# an explanation of what this option does.  This option
# has no effect if flap detection is disabled.

low_service_flap_threshold=5.0
high_service_flap_threshold=20.0
low_host_flap_threshold=5.0
high_host_flap_threshold=20.0



# DATE FORMAT OPTION
# This option determines how short dates are displayed. Valid options
# include:
#	us		(MM-DD-YYYY HH:MM:SS)
#	euro    	(DD-MM-YYYY HH:MM:SS)
#	iso8601		(YYYY-MM-DD HH:MM:SS)
#	strict-iso8601	(YYYY-MM-DDTHH:MM:SS)
#

date_format=euro






# TIMEZONE OFFSET
# This option is used to override the default timezone that this
# instance of Nagios runs in.  If not specified, Nagios will use
# the system configured timezone.
#
# NOTE: In order to display the correct timezone in the CGIs, you
# will also need to alter the Apache directives for the CGI path 
# to include your timezone.  Example:
#
#   <Directory "/usr/local/nagios/sbin/">
#      SetEnv TZ "Australia/Brisbane"
#      ...
#   </Directory>

#use_timezone=US/Mountain
#use_timezone=Australia/Brisbane




# P1.PL FILE LOCATION
# This value determines where the p1.pl perl script (used by the
# embedded Perl interpreter) is located.  If you didn't compile
# Nagios with embedded Perl support, this option has no effect.

p1_file=/usr/local/nagios/bin/p1.pl



# EMBEDDED PERL INTERPRETER OPTION
# This option determines whether or not the embedded Perl interpreter
# will be enabled during runtime.  This option has no effect if Nagios
# has not been compiled with support for embedded Perl.
# Values: 0 = disable interpreter, 1 = enable interpreter

enable_embedded_perl=1



# EMBEDDED PERL USAGE OPTION
# This option determines whether or not Nagios will process Perl plugins
# and scripts with the embedded Perl interpreter if the plugins/scripts
# do not explicitly indicate whether or not it is okay to do so. Read
# the HTML documentation on the embedded Perl interpreter for more 
# information on how this option works.

use_embedded_perl_implicitly=1



# ILLEGAL OBJECT NAME CHARACTERS
# This option allows you to specify illegal characters that cannot
# be used in host names, service descriptions, or names of other
# object types.

illegal_object_name_chars=`~!$%^&*|'"<>?,()=



# ILLEGAL MACRO OUTPUT CHARACTERS
# This option allows you to specify illegal characters that are
# stripped from macros before being used in notifications, event
# handlers, etc.  This DOES NOT affect macros used in service or
# host check commands.
# The following macros are stripped of the characters you specify:
#	$HOSTOUTPUT$
#	$HOSTPERFDATA$
#	$HOSTACKAUTHOR$
#	$HOSTACKCOMMENT$
#	$SERVICEOUTPUT$
#	$SERVICEPERFDATA$
#	$SERVICEACKAUTHOR$
#	$SERVICEACKCOMMENT$

illegal_macro_output_chars=`~$&|'"<>



# REGULAR EXPRESSION MATCHING
# This option controls whether or not regular expression matching
# takes place in the object config files.  Regular expression
# matching is used to match host, hostgroup, service, and service
# group names/descriptions in some fields of various object types.
# Values: 1 = enable regexp matching, 0 = disable regexp matching

use_regexp_matching=0



# "TRUE" REGULAR EXPRESSION MATCHING
# This option controls whether or not "true" regular expression 
# matching takes place in the object config files.  This option
# only has an effect if regular expression matching is enabled
# (see above).  If this option is DISABLED, regular expression
# matching only occurs if a string contains wildcard characters
# (* and ?).  If the option is ENABLED, regexp matching occurs
# all the time (which can be annoying).
# Values: 1 = enable true matching, 0 = disable true matching

use_true_regexp_matching=0



# ADMINISTRATOR EMAIL/PAGER ADDRESSES
# The email and pager address of a global administrator (likely you).
# Nagios never uses these values itself, but you can access them by
# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
# commands.




admin_email=layleng91@hotmail.com
admin_pager=pagenagios@localhost



# DAEMON CORE DUMP OPTION
# This option determines whether or not Nagios is allowed to create
# a core dump when it runs as a daemon.  Note that it is generally
# considered bad form to allow this, but it may be useful for
# debugging purposes.  Enabling this option doesn't guarantee that
# a core file will be produced, but that's just life...
# Values: 1 - Allow core dumps
#         0 - Do not allow core dumps (default)

daemon_dumps_core=0



# LARGE INSTALLATION TWEAKS OPTION
# This option determines whether or not Nagios will take some shortcuts
# which can save on memory and CPU usage in large Nagios installations.
# Read the documentation for more information on the benefits/tradeoffs
# of enabling this option.
# Values: 1 - Enabled tweaks
#         0 - Disable tweaks (default)

use_large_installation_tweaks=0



# ENABLE ENVIRONMENT MACROS
# This option determines whether or not Nagios will make all standard
# macros available as environment variables when host/service checks
# and system commands (event handlers, notifications, etc.) are
# executed.  Enabling this option can cause performance issues in 
# large installations, as it will consume a bit more memory and (more
# importantly) consume more CPU.
# Values: 1 - Enable environment variable macros (default)
#         0 - Disable environment variable macros

enable_environment_macros=1



# CHILD PROCESS MEMORY OPTION
# This option determines whether or not Nagios will free memory in
# child processes (processed used to execute system commands and host/
# service checks).  If you specify a value here, it will override
# program defaults.
# Value: 1 - Free memory in child processes
#        0 - Do not free memory in child processes

#free_child_process_memory=1



# CHILD PROCESS FORKING BEHAVIOR
# This option determines how Nagios will fork child processes
# (used to execute system commands and host/service checks).  Normally
# child processes are fork()ed twice, which provides a very high level
# of isolation from problems.  Fork()ing once is probably enough and will
# save a great deal on CPU usage (in large installs), so you might
# want to consider using this.  If you specify a value here, it will
# program defaults.
# Value: 1 - Child processes fork() twice
#        0 - Child processes fork() just once

#child_processes_fork_twice=1



# DEBUG LEVEL
# This option determines how much (if any) debugging information will
# be written to the debug file.  OR values together to log multiple
# types of information.
# Values: 
#          -1 = Everything
#          0 = Nothing
#	   1 = Functions
#          2 = Configuration
#          4 = Process information
#	   8 = Scheduled events
#          16 = Host/service checks
#          32 = Notifications
#          64 = Event broker
#          128 = External commands
#          256 = Commands
#          512 = Scheduled downtime
#          1024 = Comments
#          2048 = Macros

debug_level=0



# DEBUG VERBOSITY
# This option determines how verbose the debug log out will be.
# Values: 0 = Brief output
#         1 = More detailed
#         2 = Very detailed

debug_verbosity=1



# DEBUG FILE
# This option determines where Nagios should write debugging information.

debug_file=/usr/local/nagios/var/nagios.debug



# MAX DEBUG FILE SIZE
# This option determines the maximum size (in bytes) of the debug file.  If
# the file grows larger than this size, it will be renamed with a .old
# extension.  If a file already exists with a .old extension it will
# automatically be deleted.  This helps ensure your disk space usage doesn't
# get out of control when debugging Nagios.

max_debug_file_size=1000000

Last edited by Xanios; 07-27-2010 at 09:16 PM.
 
Old 07-28-2010, 03:09 AM   #4
sem007
Member
 
Registered: Nov 2006
Distribution: RHEL, CentOS, Debian Lenny, Ubuntu
Posts: 638

Rep: Reputation: 113Reputation: 113
Did you compile with custom option?

Some value of your nagios configuration is different then default.

for exa.

Code:
service_perfdata_file=/tmp/service-perfdata

service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
and there is no entry of cfg_dir. (i think full nagios.cfg is not here.)

If you didn't compile with option i suggest use default configuration for nagios.

Quote:
cfg_dir=/usr/local/nagios/etc/serviceext
process_performance_data=1
service_perfdata_file=/usr/local/nagios/var/service-perfdata
service_perfdata_file_template=$HOSTNAME$\t$SERVICEDESC$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\t$TIMET $
service_perfdata_file_mode=a
service_perfdata_file_processing_interval=30
service_perfdata_file_processing_command=process-service-perfdata-file
let us know what happen with default configuration.
 
Old 07-28-2010, 03:26 AM   #5
Xanios
Member
 
Registered: Jul 2010
Posts: 216

Original Poster
Rep: Reputation: 30
Sorry but what you mean by compile with custom option?

Is it this:

Code:
sudo /etc/init.d/nagios restart
I tried to use the default configuration (by adding in "service_perfdata_file=/usr/local/nagios/var/service-perfdata" and "service_perfdata_file_template=$HOSTNAME$\t$SERVICEDESC$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\t$TIME T $" cause i don't have these 2 in the config file). The result still the same, there's no icon there.

By the way, it should be "t$TIMET$" and not "t$TIMET $" i suppose?

Last edited by Xanios; 07-28-2010 at 03:30 AM.
 
Old 07-28-2010, 03:49 AM   #6
sem007
Member
 
Registered: Nov 2006
Distribution: RHEL, CentOS, Debian Lenny, Ubuntu
Posts: 638

Rep: Reputation: 113Reputation: 113
hmm....

did you restart nagios_grapher service ?

after changes just restart service and check is service-perfdata file created or not.

/etc/init.d/nagios_grapher restart
/etc/init.d/nagios restart
 
Old 07-28-2010, 04:01 AM   #7
Xanios
Member
 
Registered: Jul 2010
Posts: 216

Original Poster
Rep: Reputation: 30
I restarted nagios_grapher.

they gave me:

Code:
xanios@ubuntu:~/NagiosGrapher-1.7.1$ /etc/init.d/nagios_grapher restart
Stopping nagios_grapher: No process in pidfile `/usr/local/nagios/var/nagios_grapher/nagios_grapher.pid' found running; none killed.
collect2.pl.
Starting nagios_grapher: collect2.pl.
Code:
xanios@ubuntu:~/NagiosGrapher-1.7.1$ ls -la /usr/local/nagios/var
total 5204
drwxrwxr-x  7 nagios nagios    4096 2010-07-28 01:07 .
drwxr-xr-x 10 root   root      4096 2010-07-27 00:55 ..
drwxrwxr-x  2 nagios nagios    4096 2010-07-28 00:00 archives
drwxr-xr-x  2 root   root      4096 2010-07-27 00:55 nagios_grapher
-rw-r--r--  1 nagios nagios       6 2010-07-28 00:32 nagios.lock
-rw-r--r--  1 nagios nagios    9701 2010-07-28 01:07 nagios.log
-rw-r--r--  1 root   root     86016 2010-07-26 18:01 .nagios.log.swp
-rw-r--r--  1 nagios root         0 2010-07-28 00:20 ngraph.log
-rw-r--r--  1 nagios nagios   43428 2010-07-28 00:32 objects.cache
-rw-------  1 nagios nagios   63308 2010-07-28 00:32 retention.dat
drwxr-xr-x  2 nagios root      4096 2010-07-27 00:55 rrd
drwxrwsr-x  2 nagios nagcmd    4096 2010-07-28 00:32 rw
-rw-rw-r--  1 nagios nagios    1330 2010-07-28 01:07 service-perfdata
-rw-rw-r--  1 nagios nagios    1838 2010-07-28 00:26 service-perfdata.1280302015
-rw-rw-r--  1 nagios nagios    2533 2010-07-28 00:27 service-perfdata.1280302045
-rw-rw-r--  1 nagios nagios    1658 2010-07-28 00:27 service-perfdata.1280302075
-rw-rw-r--  1 nagios nagios    2375 2010-07-28 00:28 service-perfdata.1280302105
-rw-rw-r--  1 nagios nagios    1658 2010-07-28 00:28 service-perfdata.1280302135
-rw-rw-r--  1 nagios nagios    2375 2010-07-28 00:29 service-perfdata.1280302165
-rw-rw-r--  1 nagios nagios    1658 2010-07-28 00:29 service-perfdata.1280302195
-rw-rw-r--  1 nagios nagios    2520 2010-07-28 00:30 service-perfdata.1280302225
-rw-rw-r--  1 nagios nagios    2071 2010-07-28 00:30 service-perfdata.1280302255
-rw-rw-r--  1 nagios nagios    2538 2010-07-28 00:31 service-perfdata.1280302285
-rw-rw-r--  1 nagios nagios    1894 2010-07-28 00:31 service-perfdata.1280302315
-rw-rw-r--  1 nagios nagios    2553 2010-07-28 00:32 service-perfdata.1280302356
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:32 service-perfdata.1280302386
-rw-rw-r--  1 nagios nagios    1065 2010-07-28 00:33 service-perfdata.1280302416
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:33 service-perfdata.1280302446
-rw-rw-r--  1 nagios nagios    1065 2010-07-28 00:34 service-perfdata.1280302476
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:34 service-perfdata.1280302506
-rw-rw-r--  1 nagios nagios    1333 2010-07-28 00:35 service-perfdata.1280302536
-rw-rw-r--  1 nagios nagios    2172 2010-07-28 00:35 service-perfdata.1280302566
-rw-rw-r--  1 nagios nagios    1374 2010-07-28 00:36 service-perfdata.1280302596
-rw-rw-r--  1 nagios nagios    2068 2010-07-28 00:36 service-perfdata.1280302626
-rw-rw-r--  1 nagios nagios    1128 2010-07-28 00:37 service-perfdata.1280302656
-rw-rw-r--  1 nagios nagios    2068 2010-07-28 00:37 service-perfdata.1280302686
-rw-rw-r--  1 nagios nagios    1000 2010-07-28 00:38 service-perfdata.1280302716
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:38 service-perfdata.1280302746
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:39 service-perfdata.1280302776
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:39 service-perfdata.1280302806
-rw-rw-r--  1 nagios nagios    1334 2010-07-28 00:40 service-perfdata.1280302836
-rw-rw-r--  1 nagios nagios    2172 2010-07-28 00:40 service-perfdata.1280302866
-rw-rw-r--  1 nagios nagios    1375 2010-07-28 00:41 service-perfdata.1280302896
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:41 service-perfdata.1280302926
-rw-rw-r--  1 nagios nagios    1194 2010-07-28 00:42 service-perfdata.1280302956
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:42 service-perfdata.1280302986
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:43 service-perfdata.1280303016
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:43 service-perfdata.1280303046
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:44 service-perfdata.1280303076
-rw-rw-r--  1 nagios nagios    2068 2010-07-28 00:44 service-perfdata.1280303106
-rw-rw-r--  1 nagios nagios    1268 2010-07-28 00:45 service-perfdata.1280303136
-rw-rw-r--  1 nagios nagios    2172 2010-07-28 00:45 service-perfdata.1280303166
-rw-rw-r--  1 nagios nagios    1375 2010-07-28 00:46 service-perfdata.1280303196
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:46 service-perfdata.1280303226
-rw-rw-r--  1 nagios nagios    1194 2010-07-28 00:47 service-perfdata.1280303256
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:47 service-perfdata.1280303286
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:48 service-perfdata.1280303316
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:48 service-perfdata.1280303346
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:49 service-perfdata.1280303376
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:49 service-perfdata.1280303406
-rw-rw-r--  1 nagios nagios    1334 2010-07-28 00:50 service-perfdata.1280303436
-rw-rw-r--  1 nagios nagios    2172 2010-07-28 00:50 service-perfdata.1280303466
-rw-rw-r--  1 nagios nagios    1375 2010-07-28 00:51 service-perfdata.1280303496
-rw-rw-r--  1 nagios nagios    2068 2010-07-28 00:51 service-perfdata.1280303526
-rw-rw-r--  1 nagios nagios    1128 2010-07-28 00:52 service-perfdata.1280303556
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:52 service-perfdata.1280303586
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:53 service-perfdata.1280303616
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:53 service-perfdata.1280303646
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:54 service-perfdata.1280303676
-rw-rw-r--  1 nagios nagios    2068 2010-07-28 00:54 service-perfdata.1280303706
-rw-rw-r--  1 nagios nagios    1268 2010-07-28 00:55 service-perfdata.1280303736
-rw-rw-r--  1 nagios nagios    2172 2010-07-28 00:55 service-perfdata.1280303766
-rw-rw-r--  1 nagios nagios    1375 2010-07-28 00:56 service-perfdata.1280303796
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:56 service-perfdata.1280303826
-rw-rw-r--  1 nagios nagios    1194 2010-07-28 00:57 service-perfdata.1280303856
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:57 service-perfdata.1280303886
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:58 service-perfdata.1280303916
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 00:58 service-perfdata.1280303946
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 00:59 service-perfdata.1280303976
-rw-rw-r--  1 nagios nagios    2068 2010-07-28 00:59 service-perfdata.1280304006
-rw-rw-r--  1 nagios nagios    1268 2010-07-28 01:00 service-perfdata.1280304036
-rw-rw-r--  1 nagios nagios    2172 2010-07-28 01:00 service-perfdata.1280304066
-rw-rw-r--  1 nagios nagios    1375 2010-07-28 01:01 service-perfdata.1280304096
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 01:01 service-perfdata.1280304126
-rw-rw-r--  1 nagios nagios    1194 2010-07-28 01:02 service-perfdata.1280304156
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 01:02 service-perfdata.1280304186
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 01:03 service-perfdata.1280304216
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 01:03 service-perfdata.1280304246
-rw-rw-r--  1 nagios nagios    1066 2010-07-28 01:04 service-perfdata.1280304276
-rw-rw-r--  1 nagios nagios    2068 2010-07-28 01:04 service-perfdata.1280304306
-rw-rw-r--  1 nagios nagios    1268 2010-07-28 01:05 service-perfdata.1280304336
-rw-rw-r--  1 nagios nagios    2172 2010-07-28 01:05 service-perfdata.1280304366
-rw-rw-r--  1 nagios nagios    1375 2010-07-28 01:06 service-perfdata.1280304396
-rw-rw-r--  1 nagios nagios    2002 2010-07-28 01:06 service-perfdata.1280304426
-rw-rw-r--  1 nagios nagios    1194 2010-07-28 01:07 service-perfdata.1280304456
-rw-rw-r--  1 nagios nagios 4673593 2010-07-28 01:07 service-perfdata.out
drwxr-xr-x  3 root   root      4096 2010-07-11 18:11 spool
-rw-rw-r--  1 nagios nagios   63749 2010-07-28 01:07 status.dat
Still no icon is seen.

Last edited by Xanios; 07-28-2010 at 04:05 AM.
 
Old 07-28-2010, 04:22 AM   #8
sem007
Member
 
Registered: Nov 2006
Distribution: RHEL, CentOS, Debian Lenny, Ubuntu
Posts: 638

Rep: Reputation: 113Reputation: 113
also restart nagios service after nagios_grapher service.

now paste output of below command

Code:
sudo grep performance_data /usr/local/nagios/etc/nagios.cfg
sudo grep serviceext /usr/local/nagios/etc/nagios.cfg
 
Old 07-28-2010, 05:35 AM   #9
Xanios
Member
 
Registered: Jul 2010
Posts: 216

Original Poster
Rep: Reputation: 30
Code:
xanios@ubuntu:~/NagiosGrapher-1.7.1$ sudo grep performance_data /usr/local/nagios/etc/nagios.cfg
process_performance_data=1
# enable_performance_data option (above) is set to 1.  The command
# enable_performance_data option (above) is set to 1.
Code:
cfg_dir=/usr/local/nagios/etc/serviceext
Yeah, i restarted nagios too.
 
Old 07-28-2010, 06:10 AM   #10
sem007
Member
 
Registered: Nov 2006
Distribution: RHEL, CentOS, Debian Lenny, Ubuntu
Posts: 638

Rep: Reputation: 113Reputation: 113
hmmm....

all configurations are ok..
and as per #7 servie-prefer file and tmp files also create.

also check command entry in commands.cfg
it should be,
Code:
command_line mv /usr/local/nagios/var/service-perfdata /usr/local/nagios/var/service-perfdata.$TIMET$
now check nagios web interface.

Still if you have problem check log file for error.

Code:
tail -f /usr/local/nagios/var/ngraph.log
let us know what happen
 
Old 07-29-2010, 12:15 AM   #11
Xanios
Member
 
Registered: Jul 2010
Posts: 216

Original Poster
Rep: Reputation: 30
sudo vi /usr/local/nagios/var/service-perfdata /usr/local/nagios/var/service-perfdata.$TIMET$:

Code:
wins server 2003        FTP     Connection refused              1280376430
wins 7  IMAP    CRITICAL - Socket timeout after 10 seconds              1280376430
wins 7  PING    PING OK - Packet loss = 0%, RTA = 0.33 ms       rta=0.332000ms;250.000000;600.000000;0.000000 pl=0%;20;60;0     1280376440
localhost       FTP     FTP OK - 0.008 second response time on port 21 [220 (vsFTPd 2.2.0)]     time=0.007664s;;;0.000000;10.000000     1280376440
wins 7  SMTP    CRITICAL - Socket timeout after 10 seconds              1280376440
wins xp sp2     HTTP    CRITICAL - Socket timeout after 10 seconds              1280376440
localhost       POP3    Connection refused              1280376450
ubuntu  HTTP    HTTP OK: HTTP/1.1 200 OK - 452 bytes in 0.004 second response time      time=0.004101s;;;0.000000 size=452B;;;0 1280376450
wins server 2003        SSH     Connection refused              1280376450
wins server 2003        POP3    Connection refused              1280376450
wins vista      SSH     CRITICAL - Socket timeout after 10 seconds              1280376450
wins xp sp2     IMAP    CRITICAL - Socket timeout after 10 seconds              1280376450
localhost       IMAP    Connection refused              1280376450
wins 7  POP3    CRITICAL - Socket timeout after 10 seconds              1280376450
why i typed this : "tail -f /usr/local/nagios/var/ngraph.log", there is no output?
 
Old 07-29-2010, 08:01 AM   #12
Xanios
Member
 
Registered: Jul 2010
Posts: 216

Original Poster
Rep: Reputation: 30
someone? >.<
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Ubuntu Restricted Extras - Lets Ubuntu Play Everything [Ubuntu for Beginners Sc LXer Syndicated Linux News 0 04-20-2010 01:10 AM
LXer: NagiosGrapher: HTTP Response Time LXer Syndicated Linux News 0 04-13-2010 12:50 PM
LXer: NagiosGrapher on CentOS LXer Syndicated Linux News 0 04-06-2010 08:50 PM
NagiosGrapher: any perl expert to help interpret error? Akhran Linux - Software 3 04-20-2007 10:23 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 06:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration