Problem with trends and notification

[Timo Koskela]

I have problems with trends in my distributed Nagios server. There are a couple of servers I want to monitor and take prints with trends because they are down too often. But trends just dont show anything. In trends where you usually see red and green area, are just white line. 
What could be the problem?
And shouldn't it be possible to distributed server also send notifications, not just the central server? All contacts and contacts groups are configured ok. Or is't so, that only the central Nagios server contains the data from trend and notifications, and it isn't even possible to distributed server to send data to central Nagios server via NSCA, and still be able to notificate on it's own??

Here is my nagios.cfg file from the distributed Nagios (ver. 1.2)

I hope someone could help me, please.

##############################################################################

#

# NAGIOS.CFG - Sample Main Config File for Nagios 

#

# Read the documentation for more information on this configuration

# file. I've provided some comments here, but things may not be so

# clear without further explanation.

#

# Last Modified: 07-04-2002

###############################################################################

log_file=/usr/local/nagios/var/nagios.log

cfg_file=/usr/local/nagios/etc/checkcommands.cfg

cfg_file=/usr/local/nagios/etc/misccommands.cfg

cfg_file=/usr/local/nagios/etc/hosts.cfg

resource_file=/usr/local/nagios/etc/resource.cfg

status_file=/usr/local/nagios/var/status.log

nagios_user=nagios

nagios_group=nagios

check_external_commands=0

command_check_interval=-1

command_file=/usr/local/nagios/var/rw/nagios.cmd

comment_file=/usr/local/nagios/var/comment.log

downtime_file=/usr/local/nagios/var/downtime.log

lock_file=/usr/local/nagios/var/nagios.lock

temp_file=/usr/local/nagios/var/nagios.tmp

log_rotation_method=d

log_archive_path=/usr/local/nagios/var/archives

use_syslog=1

log_notifications=1

log_service_retries=1

log_host_retries=1

log_event_handlers=1

log_initial_states=0

log_external_commands=1

log_passive_service_checks=1

inter_check_delay_method=s

service_interleave_factor=s

max_concurrent_checks=0

service_reaper_frequency=10

sleep_time=1

service_check_timeout=60

host_check_timeout=30

event_handler_timeout=30

notification_timeout=30

ocsp_timeout=5

perfdata_timeout=5

retain_state_information=1

state_retention_file=/usr/local/nagios/var/status.sav

retention_update_interval=60

use_retained_program_state=0

interval_length=60

use_agressive_host_checking=0

execute_service_checks=1

accept_passive_service_checks=1

enable_notifications=1

enable_event_handlers=1

process_performance_data=0

obsess_over_services=1

ocsp_command=submit_check_result

check_for_orphaned_services=0

check_service_freshness=1

freshness_check_interval=60

aggregate_status_updates=1

status_update_interval=15

enable_flap_detection=0

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=us

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

illegal_macro_output_chars=`~$&|'"<>

admin_email=nagios

admin_pager=pagenagios

# EOF (End of file)


Thanks,
Timo Koskela
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040701/e5eab27c/attachment.html>