FYI, compiled Nagios 3.0.6 from source against the GD libraries that are
available via the RHEL5/CentOS 5 repository. This is GD releaes 2.0.33. I
still have the same problem with images being displayed on the status map.
Wondering if this is a problem with GD packages, I complied GD 2.0.35 from
source and then recompiled Nagios against the new GD 2.0.35 libraries.
Still no dice.
There does not appear to be a problem with my Nagios configuration and this
worked flawlessly in Nagios 2.8 and 2.9. The images also display correctly
when viewing the 3D status map.
James Moseley
Jon Angliss
<j...@netdork.net>
To
01/02/2009 12:03 nagios-users@lists.sourceforge.net
AM cc
Subject
Re: [Nagios-users] icons not
displaying on Nagios 3.0.6 status
map
On Wed, 31 Dec 2008 17:20:06 -0600, jmose...@corp.xanadoo.com wrote:
>
>Been using Nagios 2.x for years and never had this problem. Just upgraded
>a test server to 3.0.6 via Dag RPM (from Dag 2.9 RPM) and everything seems
>to work fine, except that icons do not display on the status map. I
>basically get a blank square, regardless if I use .png, .jpg, .gd2, etc.
>The icons display just fine in the host detail, hostgroup overview, etc.
>Yes, per upgrade instructions, this extended host info has been moved into
>the hosts config. Sample looks like:
>
> icon_image firewall_router.png
> vrml_image firewall_router.png
> statusmap_image firewall_router.gd2
> 2d_coords 100,200
>
>Attached is screen shot. Anyone else seen this?
You probably don't have the related GD libraries installed that were
used to build the RPM. All the other locations are simply links to
the image (html <img>), whilst the images in the status maps are
imported using the GD libraries if I remember correctly.
--
Jon Angliss
------------------------------------------------------------------------------
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
