Re: problem with subpagecolums

[Henrik Størner <henrik (at) hswn.dk>]

What you're trying to do is not really the way the Xymon webpages
was thought out to be. Xymon treats a single host as a whole,
you want to see services instead. So you have ssh for all of the
hosts in one group, conn for all of the hosts in another and so
on. The Xymon webpages works differently - it will group by
host, not by service.

So this issue is not resolved in 4.3.x, and unless someone
provides a different tool for building the webpages, it will
not be resolved. The standard bbgen tool cannot be made to
work the way you want it to.


Regards,
Henrik


On Thu, Oct 07, 2010 at 10:56:36PM +0530, akshar bhosale wrote:
> hello Henrik/Xymon Team,
> 
> Is subpagecolumns issue resolved in 4.3 version?please help us as we are
> praising xymon and encouraging other sysadmin teams to use the same.
> your kind help will be appreciated.
> 
> ---------- Forwarded message ----------
> From: akshar bhosale <akshar.bhosale (at) gmail.com>
> Date: Mon, Oct 4, 2010 at 12:01 AM
> Subject: subcolumns and display issue
> To: xymon (at) xymon.com
> 
> 
> Hi,
> we have xymon4.2.2 and rhel 5.2 os. we have a server and 100 clients.
> 
> We have 3 sub clusters and above bb-host file. Now our problem is that we
> have restriction on subcolumns argument to BBGENOPTS as this is common for
> all three subcluster pages..so if we want to add one extra test in one of
> the subcluster, we need to increase subcolumns aruments..e.g.all subclusters
> have 8 tests, so subcolumns=8, now if we want to configure one more test in
> subcluster2 only, how we should do that? because if we do subcolumns=9, all
> our display page will be disturbed as there are 8 tests for subcluster1 and
> 3 and 9 tests for subcluster2. So how to add or remove any service without
> disturbing the main display
> 
> 
> 
> 
> 
> our hostfile is like:
> 
> 
> page rack001 <I>Compute cluster</I>
> 
> title <I>Compute Nodes</I>
> 
> subpage rack900 <I>Row1-Rack6</I>    conn
> group-only conn
> 172.29.1.49   node49.mgmt.acc.in    #
> 172.29.1.50   node50.mgmt.acc.in    #
> 172.29.1.51   node51.mgmt.acc.in    #
> 172.29.1.52   node52.mgmt.acc.in    #
> 172.29.1.53   node53.mgmt.acc.in    #
> 172.29.1.54   node54.mgmt.acc.in    #
> 
> subpage rack901 cpu
> group-only cpu
> 
> 0.0.0.0 node49.mgmt.acc.in    # noconn
> 0.0.0.0 node50.mgmt.acc.in    # noconn
> 0.0.0.0 node51.mgmt.acc.in    # noconn
> 0.0.0.0 node52.mgmt.acc.in    # noconn
> 0.0.0.0 node53.mgmt.acc.in    # noconn
> 0.0.0.0 node54.mgmt.acc.in    # noconn
> 
> subpage rack904 ssh
> group-only ssh
> 
> 0.0.0.0 node49.mgmt.acc.in    # noconn
> 0.0.0.0 node50.mgmt.acc.in    # noconn
> 0.0.0.0 node51.mgmt.acc.in    # noconn
> 0.0.0.0 node52.mgmt.acc.in    # noconn
> 0.0.0.0 node53.mgmt.acc.in    # noconn
> 0.0.0.0 node54.mgmt.acc.in    # noconn
> 
> subpage rack904 ssh
> group-only ssh
> 
> 0.0.0.0 node49.mgmt.acc.in    # noconn
> 0.0.0.0 node50.mgmt.acc.in    # noconn
> 0.0.0.0 node51.mgmt.acc.in    # noconn
> 0.0.0.0 node52.mgmt.acc.in    # noconn
> 0.0.0.0 node53.mgmt.acc.in    # noconn
> 0.0.0.0 node54.mgmt.acc.in    # noconn
> ....and so on
> 
> ?
> 
> 
> 
> Kindly help