Ton Voon wrote: > > On 14 Sep 2009, at 12:48, joey wrote: > >> Ton Voon wrote: >>> Opsview 3.3.1 is out now! More information at >>> http://opsview.org/opsview3.3.1 >> >> upgrade went fine except the following: >> >> 1. After the upgrade i saw a lot of the following warnings in the logs.. >> after reloading a couple of times they went away: >> >> [2009/09/11 15:49:53] [Catalyst] [WARN] * $c->config->{default_model} # >> the name of the default model to use >> [2009/09/11 15:49:53] [Catalyst] [WARN] * $c->stash->{current_model} # >> the name of the model to use for this request >> [2009/09/11 15:49:53] [Catalyst] [WARN] * >> $c->stash->{current_model_instance} # the instance of the model to use >> for this request >> [2009/09/11 15:49:53] [Catalyst] [WARN] NB: in version 5.80, the >> "random" behavior will not work at all. >> [2009/09/11 15:49:53] [Catalyst] [WARN] Calling $c->model() will return >> a random model unless you specify one of: at >> /usr/drbdfs/usr/local/opsview-web/script/../lib/Opsview/Web/ControllerBase/Admin.pm >> >> line 84 >> >> >> 2. After every reload i see the following warning in the logs and i >> can't see the browser update time and last server update time in the >> status bar: >> >> [2009/09/14 13:05:13] [Catalyst] [ERROR] Caught exception in >> Opsview::Web::Controller::Root->end "Can't call method >> "status_update_time" on an undefined value at >> /usr/drbdfs/usr/local/opsview-web/script/../lib/Opsview/Web/Controller/Root.pm >> >> line 441." > > I think this problem suggests that you have different versions of the > model installed, ie there are different files in /usr/local/nagios. I > notice a /usr/drbdfs prefix - are they sync'd correctly?
Hm.. the setup we are using is a bit tricky. We have 2x HA-Opsview Master server with a shared DRDB partition (see: http://docs.opsview.org/doku.php?id=opsview3.3:hamaster-debian-howto - this howto was written by a collegue while we setup our monitoring-system. Maybe there are some files left from earlier versions.. i'll check that. >> 3. Enhancement: "Set appropriate SNMP version in MRTG for 64 bit >> counters" didn't work for me. The graphs are still not showing >> gigabit-links correctly. > > Which version of MRTG do you have? The Opsview change was to change the > configuration to request SNMPv2, but maybe there is something in MRTG > that isn't querying the device correctly? 2.16.2-3 (Debian Lenny amd64) _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
