Hi,

My service groups are not getting more than a couple (2-3) hosts in them. I'm using hostgroups to feed service groups. I've checked the config files and see that NagiosQL is not putting all of the hosts from the specified hostgroups in the config file for the service groups. In the group I looked at I've got 3 hostgroups listed and I only get 3 hosts in the service group. If I pull one of the hostgroups out of the servicegroup definition then I only get two hosts in the servicegroup. It's pretty weird because the hosts that ARE being put in when I remove a hostgroup from the servicegroup, does not even belong to the hostgroups that are still defined in the servicegroup.

These groups were working under QL 3.0.2 when I had first configured them, since then I've upgraded to 3.0.3 but I'm not sure if that's when it broke. I'm not seeing any errors, I'm not sure where to start troubleshooting on this, any ideas/suggestions?

Thanks,

-greg

NagiosQL doesn not write any host name to the servicegroup cfg file if you are using only hostgroups. NagiosQL writes the hostgroup names to the cfg files.

I do not exactly understand what you mean, because the hostgroup based servicegroups are not belong to any single hosts.

Martin,

What you are saying totally makes sense. I'm not sure what's wrong, let me show you what I'm seeing, maybe that will help.

I'm uploading a screenshot of the service group config in QL and the resulting Nagios servicegroup config.

Here's a screen shot of my QL config for the servicegroup:

This image is hidden for guests. Please login or register to see it.

Here is the resulting definition in the servicegroup.cfg:



For some reason none of my service groups, which all use hostgroups (not individual hosts) are writing the configs as hostgroups. Instead it's writing out individual hosts/service combinations, but only writing a few of the hosts that should be output.

If you want to see anything else let me know, I'd be glad to provide it.

Thanks for your help,

-greg

Could be an SQL link problem. I will check that. It is probably already fixed in the actual SVN version.