Hi Dennis,

We just found out what the problem was.  The migration script had a bug.

Your data is in files with double-names: sysUpTime.rrd was renamed to sysUpTime_sysUpTime.rrd. That is intentional but the code that matches the names was just checked in.

-Eric

Dennis B.Hopp wrote:
I upgraded from subversion:

svn update zenossinst
cd zenossinst
./install.sh

--Dennis

On Fri, 6 Oct 2006 11:30:00 -0400, "Erik A. Dahl" <[EMAIL PROTECTED]> wrote:
Dennis,

How did you upgrade?  you may need to run zenmigrate as there have
been changes to the rrdtemplates.  also if you add:

monitor localhost

to your $ZENHOME/etc/zenperfsnmp.conf file and then run zenperfsnmp
in the forground you will get better error messages.

-EAD

On Oct 5, 2006, at 4:22 PM, Dennis B.Hopp wrote:

That worked, but I lost all of my performance graphs doing the
upgrade, all of them show 'nan' even looking at the perf tab on an
individual host.

I have changed my default snmp cycle for 60 seconds to 300
seconds.  The setting is still set to 300 seconds after the upgrade
so I don't know what to look for.

--Dennis

On Thu, 5 Oct 2006 14:55:49 -0400, "Erik A. Dahl"
<[EMAIL PROTECTED]> wrote:
Dennis,

This is fixed in the trunk revision 2512.  Here is the simple change
for the file  $ZENHOME/Products/ZenModel/skins/zenmodel/
viewSystemPerformance.pt line 33 should be:

<span tal:repeat="graph python:device.primaryAq().getDefaultGraphs
(drange=drange)">

ie add .primaryAq()

-EAD


On Oct 4, 2006, at 5:45 PM, Dennis B.Hopp wrote:

I have a number of group of systems.  For example:

Systems/Network/Routers/Branch has all of our branch routers.  If I
navigate there and click on the performance tab, it displays all of
the routers, but no graphs.  If I got to each individual router and
then to perf, the performance graphs are displayed.  Is there
something I need to do, or is this a bug?

Thanks,

--Dennis

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to