Nagios Support Forum

So I just installed Centos 6.4 64bit on another box, installed, Nagios Core 4.0.0 Beta1 from source. Used just the sample cfgs and the status map has the same message ("You have not supplied any host drawing coordinates, so you cannot use this layout method.") Installed Nagios Core 3.5.0 from source on same box. Used just the sample cfgs and the status map displays correctly, in Nagios 3.5.0. Leads me to believe the hosts have the right config, something off on the Nagios Core 4.0.0 Beta1.

If you could post your findings to the Core tracker it would be great. This will get the visibility of the Core developers.

http://tracker.nagios.org

abrist mentioned the core devs were aware, but I have filed Issue ID 0000470.

Unlocked

I've now installed Nagios Core 4.0.0 Beta1 on four separate hosts and I get the same behavior on each, with the sample configs and with my configs. Hosts are two new built CentOS 6.4 64-bit (same install media), a new built Oracle Linux 6.4 64-bit and on FC14 64-bit which has my current production Nagios Core 3.2.3. I just moved the Core 3.2.3 aside and installed a Nagios Core 4.0.0 Beta1 instance.
The Beta install was done following these instructions

This seems pretty definitive that there is a bug with 4.0 beta 1. Keep us updated on your findings and we will make sure to keep you updated if the core devs fix this issue (though you may even know first as your bug on tracker will closed as resolved). Thank you kindly for your testing and due diligence.

I have upgraded from Core 3.5.1 to 4.0.0 and I am also experiencing this issue.
running on Turnkey Lamp - Debian Squeeze

Thanks for the heads up. The issue can be found on tracker:
http://tracker.nagios.org/view.php?id=470
Though it looks like either you, or someone else on squeeze has already piled on. The url above is the one to watch for updated information about this bug.

I've been updating the Tracker Issue, but I wanted to make some noise here, too.

After doing some debugging, and it appears to be a problem with the child_hosts on each host struct (that is, it's empty). The child_hosts is a new feature of 4.0.0. What has me confused is that the "schedule downtime for this host and all it's children" feature uses that same child_hosts list to accomplish it's work, and that feature appears to work fine.

Been too long since I've hacked on C. If this was Perl, I'd have it fixed by now.

Thanks for the due diligence. We are on it.
Did you append the bug with your newest findings?