Strange scheduling

fantasio · June 6, 2005, 3:23pm

Hi there!

I got some strange Problems with the Scheduling of Nagios. After Testing Nagios 2.0b3 for a time, I finally decided to use it for our Large-Scaled-LAN. But after adding about 180 Hosts with 540 Services running, I got a strange scheduling problem. Nagios now give me that Status for about 270 Services and 20 Hosts.

service is not scheduled for being checked.

Any Idea whats the Problem?

Nagios is running on a HP DL360 G4 (Xeon 3,0 1 Gig RAM). The CPULoad is about 1,8 Percent.

Regards, Fantasio

jakkedup · June 6, 2005, 5:15pm

There is another person having a scheduling problem. I wonder if it’s related to the beta. I don’t run the beta, and don’t have a problem in 1.2 nor have I seen it. Your configs should not be all that hard to move over to 1.2, so if you have the time, I’d try 1.2 instead.

fantasio · June 6, 2005, 8:17pm

Well, thats not the way i want to solve that problem. Because one of the major advantages of Nagios2 is the parallized Service-Checks. In the final phase we’ll perform about 1800 Services checks. So, is it possible that the next Beta will fix that problem?

Regards, Fantasio

luca · June 7, 2005, 3:19pm

possible is everything

fantasio · June 8, 2005, 7:37am

I dont get it, here the info from the tactical view.

Network Outages
0 Outages

Network Health
Host Health: 100.0% Health
Service Health: 99.6% Health

Hosts
0 Down 0 Unreachable 161 Up 21 Pending

Services
0 Critical 1 Warning 1 Unknown 266 Ok 272 Pending

1 Unhandled Problems

Monitoring Features
Flap Detection Notifications Event Handlers Active Checks Passive Checks
Flap Detection Enabled
All Services Enabled
No Services Flapping
All Hosts Enabled
No Hosts Flapping

Notifications Enabled
All Services Enabled
All Hosts Enabled

Event Handlers Enabled
All Services Enabled
All Hosts Enabled

Active Checks Enabled
All Services Enabled
All Hosts Enabled

Passive Checks Enabled
All Services Enabled
All Hosts Enabled

and here the services wich dont get scheduled…

boltz18-c1

SNMP-Sysname

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

Uptime

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

boltz20-og-vh-a

SNMP-Sysname

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

Uptime

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

boltz20-ug-vh-a

SNMP-Sysname

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

Uptime

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

boltz20-ug-vh-b

SNMP-Sysname

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

Uptime

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

boltz3-keller-vh

SNMP-Sysname

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

Uptime

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

bruemmer34-v24

SNMP-Sysname

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

Uptime

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

ehren26-v24-a

SNMP-Sysname

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

Uptime

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

ehren26-v24-b

SNMP-Sysname

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

Uptime

PENDING 	N/A 	0d 16h 22m 52s+ 	1/5 	Service is not scheduled to be checked...

here comes the part of the services.cfg

define service {
hostgroup_name router,switches
service_description SNMP-Sysname
check_command check_sysname
max_check_attempts 5
normal_check_interval 1
retry_check_interval 1
check_period 24x7
contact_groups admin
notification_interval 3
notification_period 24x7
notification_options w,u,c,r,f
notifications_enabled 1
}

define service {
hostgroup_name router,switches
service_description Uptime
check_command check_uptime
max_check_attempts 5
normal_check_interval 1
retry_check_interval 1
check_period 24x7
event_handler notify-by-email
event_handler_enabled 1
flap_detection_enabled 1
contact_groups admin
notification_interval 3
notification_period 24x7
notification_options w,u,c,r,f
notifications_enabled 1
}

define service {
hostgroup_name router,switches
service_description Sys-Description
check_command check_description
max_check_attempts 5
normal_check_interval 1
retry_check_interval 1
check_period 24x7
notification_interval 5
notification_period 24x7
notification_options c,r,u,f,w
contact_groups admin
}

I defined 3 Services wich are related to the two main hostgroups.

fantasio · June 8, 2005, 11:27am

Now its getting interesting… after defining a single service for every host - it works. So, is it possible that defining only one Service wich is related to 200 Hosts causes in a bug or is there a Limit on relating hosts with services? This is getting ugly if I have to define thousands of services instead of defining three services wich are related with all hosts.

Regards, Fantasio

luca · June 8, 2005, 2:57pm

i have some 70 hosts defined for ping and have no problem on it…

Luca

jakkedup · June 9, 2005, 6:30pm

[quote=“fantasio”]Well, thats not the way i want to solve that problem. Because one of the major advantages of Nagios2 is the parallized Service-Checks. In the final phase we’ll perform about 1800 Services checks. So, is it possible that the next Beta will fix that problem?

Regards, Fantasio[/quote]

This from my v1.2 configs.
"

MAXIMUM CONCURRENT SERVICE CHECKS

This option allows you to specify the maximum number of

service checks that can be run in parallel at any given time.

Specifying a value of 1 for this variable essentially prevents

any service checks from being parallelized. A value of 0

will not restrict the number of concurrent checks that are

being executed.

max_concurrent_checks=0"

So V1.2 will also parallelize checks.

jakkedup · June 9, 2005, 6:35pm

[quote=“fantasio”]Now its getting interesting… after defining a single service for every host - it works. So, is it possible that defining only one Service wich is related to 200 Hosts causes in a bug or is there a Limit on relating hosts with services? This is getting ugly if I have to define thousands of services instead of defining three services wich are related with all hosts.

Regards, Fantasio[/quote]

A host with no services defined for it? I fail to see why you would do that. Use a template in the services.cfg to make it easier to define the same service check for hundreds of hosts.