Oktober 2005 - Nav-users - lister.unit.no

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

Error in report tool "Trunked core switch ports"
by roger.aas＠hsh.no 03 Okt '05

03 Okt '05

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

1 0