jsmurphy wrote:Hmmmmm this all smells a lot like a lack of Nagios privileges...
Can you post the authorization section from your cgi.cfg? Are you also able to post the contact, contact-group, host, a single service and host-template if relevant for the DC4 host?
I know that's a lot of information but if my hunch is right, this information will make it pretty obvious where the problem is
Here you go
i took out some ip addresses, phone numbers, emails and so on because this i a public forum and i dont think you need it for solving this case.
Authorization from cgi.cfg, as you can see everyone has access to everything as long as they are logged in:
Code: Select all
use_authentication=1
use_ssl_authentication=0
authorized_for_system_information=*
authorized_for_configuration_information=*
authorized_for_system_commands=*
authorized_for_all_services=*
authorized_for_all_hosts=*
authorized_for_all_service_commands=*
authorized_for_all_host_commands=*
#authorized_for_read_only=user1,user2 #note, this is not enabled
The DC4 host:
Code: Select all
define host{
use windows-server ; Inherit default values from a template
host_name DC4 ; The name we're giving to this host
alias DC4 Herning ; A longer name associated with the host
hostgroups LH,windows-machines ; Host groups that the server should be a member of
address xxx.xxx.xxx.xxx ; IP address of the host
}
The windows-server template (used by DC4):
Code: Select all
define host{
name windows-server ; The name of this host template
use generic-host ; Inherit default values from the generic-host template
check_period 24x7 ; By default, Windows servers are monitored round the clock
check_interval 0.5 ; Actively check the server every minute
retry_interval 0.5 ; Schedule host check retries at minute intervals
max_check_attempts 3 ; Check each server 3 times (max)
check_command check-host-alive ; Default command to check if servers are "alive"
notification_interval 5760 ; Resend notifications every 3 days
notification_options d,r ; Only send notifications for specific host states
contact_groups hardware
register 0 ; DONT REGISTER THIS - ITS JUST A TEMPLATE
}
define hostextinfo{
hostgroup_name windows-machines
icon_image windows.gif
icon_image_alt Windows
vrml_image windows.gif
statusmap_image windows.gif.gd2
}
generic host template:
Code: Select all
define host{
name generic-host ; The name of this host template
notifications_enabled 1 ; Host notifications are enabled
event_handler_enabled 1 ; Host event handler is enabled
flap_detection_enabled 1 ; Flap detection is enabled
failure_prediction_enabled 1 ; Failure prediction is enabled
process_perf_data 0 ; Process performance data
retain_status_information 1 ; Retain status information across program restarts
retain_nonstatus_information 1 ; Retain non-status information across program restarts
notification_period off-workhours ; Send host notifications at any time
register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
}
The contact group named Hardware (i dont know what you need this for, but here you go anyway
):
Code: Select all
define contactgroup{
contactgroup_name hardware
alias Hardware
members ssj
}
The hostgroup named LH, is just a group to keep everything is that apartment together in the nagios web interface, the LH group has no associated functions, members or anything at all only an Alias.
And the contact named SSJ:
Code: Select all
define contact{
contact_name ssj ; Short name of user
use generic-contact ; Inherit default values from generic-contact
alias Steffan xxxxx ; Full name of user
pager xxxxxxxx ; phone number
email [email protected] ; Email
service_notification_period off-workhours ; service notifications can be sent anytime
host_notification_period off-workhours
}
The generic contact template:
Code: Select all
define contact{
name generic-contact ; The name of this contact template
service_notification_options c,r ; send notifications for all service states, flapping events, and scheduled downtime events
host_notification_options d,r ; send notifications for all host states, flapping events, and scheduled downtime events
service_notification_commands notify-service-by-email,notify-service-by-sms ; send service notifications via email
host_notification_commands notify-host-by-email,notify-host-by-sms ; send host notifications via email
register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL CONTACT, JUST A TEMPLATE!
service_notification_period off-workhours ; service notifications can be sent anytime
host_notification_period off-workhours
}
I then have some commands (notify-host-by-email + notify-host-by-sms for example) to create emails and sms for notifcation, but i dont think you need theese (if you do, just ask and i will post them).
The "off-workhours" notification_period is just a normal time period that defines between 16:00 and 08.00.
If there is something more you need, feel free to ask! I really want to solve this problem, and i hope you can help with this!
I'm open to try stuff in order to get this working so just post what i should do, and i will try it
+ the nagios server is running on a virtual machine, which i take a snapshot of before i make any major changes, so if anything goes horribly wrong, i can recover the entire machine within minutes.