Nav-users

nav-users@lister.sikt.no

1376 discussions

Alertengine
by odd.hauge＠hiMolde.no 10 Okt '05

10 Okt '05

Problem solved. Downloaded the DBD::Pg library and reinstalled it. Sorrow bothering you. Cheers Odd Arne > -----Original Message----- > From: nav-users-bounces(a)itea.ntnu.no > [mailto:nav-users-bounces@itea.ntnu.no] On Behalf Of Hauge Odd Arne > Sent: Monday, October 10, 2005 4:40 PM > To: nav-users(a)itea.ntnu.no > Subject: [Nav-users] Alertengine > > Hi. > > I cannot start AlertEngine. Seems like some problem with the > Pg library on my installation. The error message in the logfile is: > Uncaught exception from user code: > DBD::Pg initialisation failed: Can't locate object > method "driver" via package "DBD::Pg" at > /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi/DBI.p > m line 747. > > Perhaps the capitalisation of DBD 'Pg' isn't right. at > /usr/lib/perl5/site_perl/5.8.6/NAV/AlertEngine/Engine.pm line > 53 at > /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi/DBI.pm line > 753 > DBI::install_driver('DBI', 'Pg') called at > /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi/DBI.p > m line 573 > DBI::connect('DBI', > 'dbi:Pg:dbname=navprofiles;host=\'localhost\'', 'navwrite', > 'some-password', 'undef') called at > /usr/lib/perl5/site_perl/5.8.6/NAV/AlertEngine/Engine.pm line 53 > NAV::AlertEngine::Engine::new('NAV::AlertEngine::Engine', > 'HASH(0x8d40074)') called at ./alertengine.pl line 31 > > > Cheking if DBD:PG is installed: > > # perl -MCPAN -e 'install DBD::Pg' > CPAN: Storable loaded ok > Going to read /root/.cpan/Metadata > Database was generated on Thu, 30 Jun 2005 00:00:19 GMT > DBD::Pg is up to date. > > > Any suggestion anyone ? > > - odd arne hauge > > _______________________________________________ > Nav-users mailing list > Nav-users(a)itea.ntnu.no > http://mailman.itea.ntnu.no/mailman/listinfo/nav-users >

1 0

problems with eventengine
by Jan.Susegg＠hint.no 10 Okt '05

10 Okt '05

The eventEngine reports the following error message in eventEngine.log Okt 10 08:45:12 2005 eventEngine BOX_STATE_EVENTHANDLER-6-CALLBACK Added alert: e=7731 d=222 n=117 t=boxState s=x [status=down] Okt 10 08:45:12 2005 eventEngine DEV_DB-6-POSTALERT Posting alert: e=7731 d=222 n=117 t=boxState s=x [status=down] Okt 10 08:45:12 2005 eventEngine DEV_DB-6-POSTALERT SQLException while posting alert: java.sql.SQLException: ERROR: More than one tuple returned by a subselect used as an expression. Okt 10 08:45:12 2005 eventEngine BOX_STATE_EVENTHANDLER-4-CALLBACK While posting netel down alert, PostAlertException: Got SQLException: ERROR: More than one tuple returned by a subselect used as an expression. Okt 10 08:45:12 2005 eventEngine BOX_STATE_EVENTHANDLER-6-HANDLE Scheduling callback in 120587 ms (120 s) Does anyone know how to fix this? NAV doesn't report box down, but I know that I have a box down. >From Borge.Brunes at cc.uit.no Mon Oct 10 14:08:59 2005 From: Borge.Brunes at cc.uit.no (Borge Brunes) Date: Mon Oct 10 13:10:34 2005 Subject: [Nav-users] pping problem Message-ID: <200510101108.j9AB8xES002217(a)duke.cc.uit.no> pping is dying with the following message: [2005-10-09 11:25:24] pping.py:main:172 [Notice] 330 hosts checked in 9.957 secs. 1 hosts currently marked as down. Exception in thread sender: Traceback (most recent call last): File "/usr/local/lib/python2.4/threading.py", line 442, in __bootstrap self.run() File "/usr/local/lib/python2.4/threading.py", line 422, in run self.__target(*self.__args, **self.__kwargs) File "/usr/local/nav/lib/python/nav/statemon/megaping.py", line 261, in _sendRequests mySocket.sendto(packet, (host.ip, 0)) error: (64, 'Host is down') Exception in thread getter: Traceback (most recent call last): File "/usr/local/lib/python2.4/threading.py", line 442, in __bootstrap self.run() File "/usr/local/lib/python2.4/threading.py", line 422, in run self.__target(*self.__args, **self.__kwargs) File "/usr/local/nav/lib/python/nav/statemon/megaping.py", line 186, in _getResponses rd, wt, er = select.select([self._sock], [], [], timeout) error: (4, 'Interrupted system call') What could be wrong? -- Borge Brunes, Computer Center, University of Tromso, Norway http://www.cc.uit.no/~borge/ | http://www.freebsd.org

1 0

Bug "Report - Room search"
by Borge.Brunes＠cc.uit.no 10 Okt '05

10 Okt '05

There is a bug in the report "Reports - Room search". If I do a search? on my room tf2437 I got 24 hits The same (advanced) search? based on the report "All IP Devices" gives me 42 hits ?https://nav.uit.no/report/netbox2?roomid=tf2437&op_roomid=like ?https://nav.uit.no/report/netbox?op_roomid=like&adv=1&roomid=tf2437 Fix: use "netbox" instead of "netbox2" in the report. regards, -- Borge Brunes, Computer Center, University of Tromso, Norway http://www.cc.uit.no/~borge/ | http://www.freebsd.org

1 0

machine tracker
by kimalat＠northwood.edu 10 Okt '05

10 Okt '05

hello, i have just installed NAV 3.0 and whats steps are there to use the machine tracker? thanks kip

1 0

help with installation
by MLaTurner＠CompuNetwork.Net 07 Okt '05

07 Okt '05

Is there a "step-by-step" guide for installing Nav3 on RedHat 9.0?? I am most likely in over my head . . .

2 1

Problem with the radius-checker in servicemon
by magnus＠ntnu.no 05 Okt '05

05 Okt '05

Borge Brunes: > I try to start monitoring a radius-service using servicemon in NAV. > Added the service to a server and all looks fine in the > "Service availability": > Handler radius > Status Up > > But the servicemon.log says: > db.py:getCheckers:226 [Critical] no such checker: radius > > > Why is the "Service availability" wrong and what's wrong > with the radius-checher? I think this means (it's been a while since I looked at the code) that the servicemonitor was unable to load the radius-checker module. The most appearant reason would be that the radius-checker depends on some python radius module. The actual radius-checker is located in the lib/python/nav/statemon/checker directory. I think you can figure out the dependencies from that. Also, there is a utility called serviceChecker.py or something similar that can assist you in debugging what this checkers actually do. If you look at the service availability, it probably don't contain any data, which means it hasn't been able to measure anything. The service status should have been 'Unknown', but I don't think our data model supports i at the time. HTH, -- Magnus Nordseth

1 0

Web page of NAV 3.0.0 still says beta
by roger.aas＠hsh.no 05 Okt '05

05 Okt '05

A "cosmetic" error on the web-page of NAV 3.0.0, it still says "Welcome to NAV v3.0 _beta_!". Something to fix for 3.0.1? :-) Regards, Roger --- Roger Aas Stord/Haugesund College >From Vidar.Faltinsen at uninett.no Mon Sep 19 02:44:07 2005 From: Vidar.Faltinsen at uninett.no (Vidar Faltinsen) Date: Mon Sep 19 01:44:12 2005 Subject: [Nav-users] Release-notice: NAV 3.0.0 :-)) In-Reply-To: <432AD483.40701(a)ntnu.no> References: <432AD483.40701(a)ntnu.no> Message-ID: <Pine.LNX.4.63.0509190141110.5381(a)valentin.uninett.no> > NAV 3.0.0 is now finally available for download at > http://metanav.ntnu.no/ :-) Thanks, Morten. Very good work. - Vidar

2 1

SV: [Nav-users] Alertengine email sender machine name != real
by roger.aas＠hsh.no 05 Okt '05

05 Okt '05

The DNS data is correct for both servers so that is not the problem here. - Roger Peder Magne Sefland wrote: > Maybe some information is collected from dns and the other is from > machine name? > > Are they the same? > > Peder > > >>>>Roger Aas <roger.aas(a)hsh.no> 29.09.2005 11:20:53 >>> > > I get this email from Alertengine: > > > X-Auth-No: > > Return-Path: <navcron(a)nav3.hsh.no> > > Received: from sentinel.hsh.no not authenticated [158.37.208.20] > > by posthus.hsh.no with NetMail SMTP Agent $Revision: 3.22.1.16 > $ on Novell NetWare; > > Thu, 29 Sep 2005 10:41:26 +0200 > > Received: from artifact.hsh.no ([158.37.35.10]) > > by sentinel.hsh.no (SMSSMTP 4.1.7.33) with SMTP id > M2005092910483300240 > > for <roger(a)posthus.hsh.no>; Thu, 29 Sep 2005 10:48:33 +0200 > > Received: from sentinel.hsh.no (sentinel.hsh.no [158.37.208.20]) > > by artifact.hsh.no (8.9.3 (PHNE_28760)/8.9.3) with SMTP id > KAA07954 > > for <roger.aas(a)hsh.no>; Thu, 29 Sep 2005 10:48:33 +0200 > (METDST) > > Received: from nav3.hsh.no ([158.37.208.25]) > > by sentinel.hsh.no (SMSSMTP 4.1.7.33) with SMTP id > M2005092910483200238 > > for <roger.aas(a)hsh.no>; Thu, 29 Sep 2005 10:48:32 +0200 > > Received: from nav3.hsh.no (nav3.hsh.no [127.0.0.1]) > > by nav3.hsh.no (8.13.1/8.13.1) with ESMTP id j8T8mWdi008206 > > for <roger.aas(a)hsh.no>; Thu, 29 Sep 2005 10:48:32 +0200 > > Received: (from navcron@localhost) > > by nav3.hsh.no (8.13.1/8.13.1/Submit) id j8T8mWdW008203; > > Thu, 29 Sep 2005 10:48:32 +0200 > > Date: Thu, 29 Sep 2005 10:48:32 +0200 > > Message-Id: <200509290848.j8T8mWdW008203(a)nav3.hsh.no> > > From: alertengine(a)nav.hsh.no > > To: roger.aas(a)hsh.no > > Subject: Box haugesund-auditoriume-ap.hsh.no is up > > > > This is an automatically generated message from NAV: > > > > Box haugesund-auditoriume-ap.hsh.no (158.37.35.132) is up since > 2005-09-29 10:48:09. > > As you can see it is only the "From:" header line that says > "nav.hsh.no", the rest of > the headers give the correct name for the server "nav3.hsh.no". Anyone > know where this > is happening? Some config I have missed? Or a small bug lurking > somewhere? Or is it just > a cosmetic thing since you are not supposed to answer such an email? > Since I have called > the NAV 2.1.5 server for nav.hsh.no it gave me a small moment of > confusion... :-) > > - Roger >

1 1

Urgent: SMS sending problem
by roger.aas＠hsh.no 05 Okt '05

05 Okt '05

I was planning to get NAV 3 into service soon. So the next thing I needed to test is that NAV sends SMS'es to the person that is on duty. But I do not get this to work. Everytime I start NAV I get an email like this: > From: navcron(a)nav3.hsh.no > To: roger(a)hsh.no > Subject: smsd database connection problem > > > Status: 03.10.2005 10:29:13 PG_conn=SCALAR(0x826d464) 1 Reset > > Error was: > server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. The gammu program by itself works. I can do a command like this: echo Test | gammu nothing --sendsms TEXT 91799053 and I receive an SMS. If I use the test functionality of smsd.pl like this: /usr/local/nav/bin/smsd.pl -t 91799053 I do _not_ get an SMS and it prints just a "0" on the console. Can someone please help me with this. This is the function I need working to start using NAV 3. Best regards, Roger -- Roger Aas Stord/Haugesund College

1 1

Error in report tool "Trunked core switch ports"
by odd.hauge＠hiMolde.no 05 Okt '05

05 Okt '05

I'm having the same error messages as you Roger. I guess this can have something to do with the version of postgres we are using. I have installed Fedora Core 4 which comes with ver. 8.0.3 of postgres. I guess RHEL4 comes with ver 8 to. And I believe boolean expressions are handled in a different way in version 8 of postgres than in ver. 7. But I'm not a database expert. But if you edit /usr/local/nav/etc/report/front.html and replaces trunk=1 with trunk=t in line 80 the report works. The other "error" you reported earlier can be avoid by editing /usr/local/nav/etc/report/report.conf. Change line 290 from: GROUP BY roomid,sysname,host(ip),catid,orgid,val,netbox.netboxid,prefixid"; to GROUP BY roomid,sysname,host(ip),catid,orgid,val,netbox.netboxid,netbox.ip,prefix id"; Nice if someone of the devolpers can comment this. Cheers Odd Arne Hauge Molde University College > -----Original Message----- > From: nav-users-bounces(a)itea.ntnu.no > [mailto:nav-users-bounces@itea.ntnu.no] On Behalf Of Roger Aas > Sent: Monday, October 03, 2005 1:34 PM > To: nav-users(a)itea.ntnu.no > Subject: [Nav-users] Error in report tool "Trunked core switch ports" > > Nav version 3.0.0 > > "Toolbox -> Report -> Core Switches/Trunked core switch > ports" gives me this error: > > Configuration error! The report generator is not able to do > such things. > ERROR: operator does not exist: boolean = integer > HINT: No operator matches the given name and argument type(s). > You may need to add explicit type casts. > SELECT > b1.sysname,s1.interface,m1.module,s1.port,s1.link,s1.speed,s1. > duplex,s1.media,s1.trunk,vlan.vlan,s1.portname,b2.sysname > AS to_netboxid,m2.module AS > remote_module,s1.swportid,b1.netboxid AS netboxid,b1.catid > FROM swport AS s1 JOIN module AS m1 USING (moduleid) JOIN > netbox AS b1 USING (netboxid) LEFT JOIN netbox AS b2 ON > (to_netboxid=b2.netboxid) LEFT JOIN swportvlan ON > (s1.swportid=swportvlan.swportid AND (trunk=false OR trunk IS > NULL)) LEFT JOIN vlan using(vlanid) LEFT JOIN swport AS s2 ON > (s1.to_swportid=s2.swportid) LEFT JOIN module AS m2 ON > (s2.moduleid=m2.moduleid) WHERE s1.trunk = 1 AND b1.catid = 'SW' > ORDER BY b1.sysname,module,port LIMIT 100 OFFSET 0 > > I sent earlier an email about another error I got on another > report tool, when sorting on IP-address on servers. I have > not received any hints to what could be the problem there. > > httpd 2.0.52 > jakarta-tomcat 5.0.28 > java j2sdk1.4.2_08 > perl 5.8.5 > php 4.3.9 > postgresql 7.4.8 > python 2.3.4, mod_python 3.1.3 > > Regards, > Roger > > -- > Roger Aas > Stord/Haugesund College > > > _______________________________________________ > Nav-users mailing list > Nav-users(a)itea.ntnu.no > http://mailman.itea.ntnu.no/mailman/listinfo/nav-users >

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users