-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/01/2006 11:54, Borge Brunes uttered:

...

The fix is to change line 917 in that file from: if (macVlan.size() == 0) continue; To: if (macVlan == null || macVlan.size() == 0) continue; I can check this into svn later.

Yes! It fixed the problem. Thanks.

Lovely! Kristian, when will you be checking in the fix? :) - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx5sAXxIl0kpcOkQRArreAJ0ZKuSQ4+cj2yUBR9FnX3t6bqhArQCg1TME htAvwyGj74lbb4jPbQyevXA= =cFgk -----END PGP SIGNATURE-----

From peder.sefland at hivolda.no Fri Jan 13 13:24:47 2006 From: peder.sefland at hivolda.no (Peder Magne Sefland) Date: Fri Jan 13 13:25:25 2006 Subject: SV: Re: [Nav-users] logger.conf Message-ID: <s3c7aa3c.042@HVO-3.hivolda.no>

For us it was a useful tool in nav2, and we where looking forward to it in nav3 as well. And it has been mention by others in the "Feature request anyone" Nav is a powerfull tool to analyze your network, and collecting syslog is an importen part in this work. I understand that resources are limited,(refering to a mail from Morten with subject Re: [Nav-users] Again?) but Syslog Analyzer is a already implemented function that I hope will be stable. Peder

...

...

Morten Vold <morten.vold@ntnu.no> 13.01.2006 11:11:22 >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 04/01/2006 14:59, Wojciech Kozicki uttered:

how should be cisco box configured to have correct analyse in NAV Syslog Analyzer?

I'm sorry to say that the syslog analyzer is an ill conceived subsystem of NAV, and it is debated whether it belongs there or not. The developer that wrote it no longer works on the project, and hardly anyone I know of cares to use it (most sysadmins I know prefer to grep the log files manually). With regards to your actual question, I have no idea about the required format. Cisco equipment at NTNU still logs to our NAV 2 installation, and the syslog analyzer har been rewritten from scratch in NAV 3. - From what I can see, our logs look something like this: Jan 13 11:03:48 <router_name> 370245: Jan 13 11:03:52: %SEC-6-IPACCESSLOGP: list vlan18out denied udp <ip1>(50186) -> <ip2>(427), 1 packet What I do know, is that your logger.conf must point to the actual log file to pick up the log lines from. The default is /usr/local/nav/var/log/cisco.log, which means your syslog daemon must be configured to write log entries from external hosts to this file (or configure a different file name). The logengine cron job runs every minute to dump new entries from this file into the database. I also believe logengine will truncate the log file after it has been read. - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx3zKXxIl0kpcOkQRAiuGAKDpLWmxswuK2raIQCRS9iqDlp0MlQCdGFXg Aa2aflR3AyWhZmoaUAXiCbU= =gv6K -----END PGP SIGNATURE----- _______________________________________________ Nav-users mailing list Nav-users@itea.ntnu.no http://mailman.itea.ntnu.no/mailman/listinfo/nav-users

From morten.vold at ntnu.no Fri Jan 13 13:31:03 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 13:30:56 2006 Subject: [Nav-users] Errors when trying to make NAV on a Gentoo system with blackdown-jdk/jre In-Reply-To: <43C79AED.7040005@witelcom.com> References: <WorldClient-F200601071038.AA38330001@witelcom.com> <43C793B2.7010802@ntnu.no> <43C79AED.7040005@witelcom.com> Message-ID: <43C79D87.4060903@ntnu.no>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/01/2006 13:19, Evert Meulie uttered:

BUILD FAILED /root/nav-3.0.0/src/webapps/navAdmin/build.xml:163: taskdef class org.apache.catalina.ant.DeployTask cannot be found

Copy and paste from the lines that immediately precede build.xml:163: <!-- These properties define custom tasks for the Ant build tool that interact with the "/manager" web application installed with Tomcat 5. Before they can be successfully utilized, you must perform the following steps: - Copy the file "server/lib/catalina-ant.jar" from your Tomcat 5 installation into the "lib" directory of your Ant installation. - Create a "build.properties" file in your application's top-level source directory (or your user login home directory) that defines appropriate values for the "manager.password", "manager.url", and "manager.username" properties described above. For more information about the Manager web application, and the functionality of these tasks, see <http://localhost:8080/tomcat-docs/manager-howto.html>. - --> - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx52HXxIl0kpcOkQRAiewAKCEFDoJVBJBcWtri+eUY5p0XA1nkwCg4hSI 8OpG9KBnqIgeyEcAE09KhdE= =SbMr -----END PGP SIGNATURE-----

From morten.vold at ntnu.no Fri Jan 13 13:36:28 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 13:36:22 2006 Subject: SV: Re: [Nav-users] logger.conf In-Reply-To: <s3c7aa3c.042@HVO-3.hivolda.no> References: <s3c7aa3c.042@HVO-3.hivolda.no> Message-ID: <43C79ECC.2030602@ntnu.no>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/01/2006 13:24, Peder Magne Sefland uttered:

I understand that resources are limited,(refering to a mail from Morten with subject Re: [Nav-users] Again?) but Syslog Analyzer is a already implemented function that I hope will be stable.

I don't think it will disappear, but it may reappear in a different form. The people at the University of Troms? argue that syslog does not belong in a database, and I tend to agree - the current design is far from elegant. - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx57MXxIl0kpcOkQRAjUaAJ9vRhSIVvbq79ZgRKC9D4vj19Pt5gCgpQXj ZkrbLp0mRTnXVX0X9Tp9Iu8= =vcyJ -----END PGP SIGNATURE-----

From Borge.Brunes at cc.uit.no Fri Jan 13 13:44:29 2006 From: Borge.Brunes at cc.uit.no (Borge Brunes) Date: Fri Jan 13 13:44:36 2006 Subject: [Nav-users] Trouble with editdb and UTF-8 In-Reply-To: Message from Morten Vold <morten.vold@ntnu.no> of "Fri, 13 Jan 2006 13:11:21 +0100." <43C798E9.5020706@ntnu.no> Message-ID: <200601131244.k0DCiTgk002363@duke.cc.uit.no>

morten.vold@ntnu.no said:

How did you add them? Bulk import?

Nope, no bulk-import - added one by one.

...

I know that the encoding-consistency for Unicode has been tightened down in postgres 8.1: http://archives.postgresql.org/pgsql-hackers/2005-10/msg00972.php

Yep, that is probably what triggers the error, question is still what the input actually was. Editdb will interpret everything fed to it as UTF-8 (at least if that's what your browser indicates), but if your actual input contains invalid UTF-8 characters, editdb won't know.

My input is UTF-8, so I guess that the ugly serial number ' ??!,' came from initBox.py or another of the py-script editdb use. B?rge