Nagios Support Forum

I mentioned the children hosts issue in comment #832 on the issue tracker, but I need to post about the schedule downtime part. I've gone further down the rabbit hole in trying to understand how the hosts struct is managed, but I haven't been able to pinpoint where things are going wrong.

It was be courteous to us users if the tracker issue was assigned to someone. At least we would know that someone is looking into the problem.

moorereason wrote: It was be courteous to us users if the tracker issue was assigned to someone. At least we would know that someone is looking into the problem.

I agree, it would be nice. But with the world conference only 4 days out, I don't think this bug, along with any of the others (unless they are core 4 show stoppers), will be delegated before early October.

abrist wrote:I agree, it would be nice. But with the world conference only 4 days out, I don't think this bug, along with any of the others (unless they are core 4 show stoppers), will be delegated before early October.

Fair enough.

I did manage to get the circular maps to at least draw, but they only draw the top-level nodes (similar to the non-circular modes). So, I think there's actually two problems. I haven't figured out why it's not drawing past that first layer (the top-level hosts).

I've updated the tracker issue with my findings (comment #839). It's about as far as I can take it. I've already spent more time than I intended to on this (although I do like hacking on other people's code!). I'll let the real developers take it from here.

Thanks for updating the issue on our tracker!

Even though I said I would stop working on it, I finally got the status map working. I couldn't help myself. I knew I was close earlier.

So, if you feel adventurous, I attached a patch to the tracker issue. I only copied statusmap.cgi into production after compiling, so I don't know if it will cause any issues with any other cgi programs. YMMV. Use at your own risk and all that...

It's a rough patch, so I doubt the devs will be able to just apply the patch and move on. I mainly just wanted it working on-site here, so I'm happy.

Oh excellent! We will pass the patch out if others run into this issue!