Marco Barbieri | 3 Sep 10:22 2007
Picon

Centos 5 and NAV 3.2.2

Hi,
first of all i'm trying to run NAV 3.2.2 on a Centos 5 and i know it's not 
supported, but with really liitle tweaking the system seem to be up and 
running, despite the problem i've always had with my HP9304m that i've 
already posted about (answer pending...).

I get some errors from: 

Cron <navcron <at> nav> $BINDIR/getBoksMacs.sh $NUM_THREADS

the body of the message is at the end of this msg, there's something i can do 
to fix it or the set of libs that comes with Centos5 is too much different to 
let NAV work as it is?

Thanks for reading and my best regards, Marco barbieri.

---Body---
org.postgresql.util.PSQLException: This statement has been closed.
   at 
org.postgresql.jdbc2.AbstractJdbc2Statement.checkClosed(postgresql-jdbc-8.1.407.jar.so)
   at 
org.postgresql.jdbc2.AbstractJdbc2Statement.getUpdateCount(postgresql-jdbc-8.1.407.jar.so)
   at 
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(postgresql-jdbc-8.1.407.jar.so)
   at no.ntnu.nav.Database.Database.update(Database.java:1004)
   at no.ntnu.nav.Database.Database.insert(Database.java:928)
   at QueryBoks.runCamQueue(QueryBoks.java:1659)
   at QueryBoks.processMacEntry(QueryBoks.java:977)
   at QueryBoks.run(QueryBoks.java:266)
SQLException for update statement: INSERT INTO cam 
(Continue reading)

Morten Brekkevold | 6 Sep 10:35 2007
Picon
Picon

Re: Problem with NAV 3.2.2 and Hp 9304M - WRONG DATA - SORRY

Marco Barbieri wrote, On 31-08-2007 08:40:
> Hi again,
> i'm sorry i've posted the wrong data, in the previous post you can find a 
> HP5412zl that NAV detects well.
> 
> Here there's the data about HP9304M (it's marked HP but it's a Foundry 
> machine) that has the problem, it's a chassis with 4 slots, 3 of them are 
> loaded with 8 gbic sockets boards.

Given the OID compatibility report you sent, NAV should be able to detect the
ports on this routing switch; the ports are detected using standard mibs.  Yet
 you say that _no_ ports are detected?  If that is so, I would like to see
what  getDeviceData.log says when it collects from this device.

When it comes to modules, I must admit that NAV's support for HP equipment is
lacking in several respects.  The HP support was written and tested using the
equipment that was available at the Norwegian University of Science and
Technology at the time, and these were all HP SwitchStacks.  Consequently, NAV
only recognizes virtual stacking in HP equipment, and cannot at all recognize
modules in your HP chassis.

It is in our plans to implement more generic module support through
interpreting the ENTITY-MIB.  I'm guessing your HP9304M presents a fairly
correct view of its physical contents through its entPhysicalTable?  Since I
have no access to a 9304M myself, but am planning to code the ENTITY-MIB
support, I would greatly appreciate it if you could provide me with the output
of this table from your device; running this command on your NAV server should
do it:

  snmptable -Ci -Cb -v2c -c <community> <ip> entPhysicalTable
(Continue reading)

Morten Brekkevold | 6 Sep 11:12 2007
Picon
Picon

Re: Centos 5 and NAV 3.2.2

Marco Barbieri wrote, On 03-09-2007 10:22:

> first of all i'm trying to run NAV 3.2.2 on a Centos 5 and i know it's not 
> supported,

That depends on what you mean by "supported" :)  We do not guaruantee support
to anyone, but you should be able to have NAV up and run on any Linux distro.
 The most common obstacle seems to be when some software that NAV depends on
comes out with a new version that breaks some backwards compatibility.

> I get some errors from: 
> 
> Cron <navcron <at> nav> $BINDIR/getBoksMacs.sh $NUM_THREADS
> 
> the body of the message is at the end of this msg, there's something i can do 
> to fix it or the set of libs that comes with Centos5 is too much different to 
> let NAV work as it is?
> 
> Thanks for reading and my best regards, Marco barbieri.
> 
> ---Body---
> org.postgresql.util.PSQLException: This statement has been closed.
>    at 
> org.postgresql.jdbc2.AbstractJdbc2Statement.checkClosed(postgresql-jdbc-8.1.407.jar.so)
[...]

I think I've seen this before, and it happened when we upgraded our PostgreSQL
JDBC driver to version 8.1.  I'm not sure what changed, since the API should
remain the same - only the driver should work better against PostgreSQL 8.1.
I assume that your CentOS installation runs the PostgreSQL 8.1 server as well?
(Continue reading)

Mels | 6 Sep 21:01 2007
Picon

Re: Centos 5 and NAV 3.2.2

Hi all,

I started this week with a clean system, installing nav on Suse 10.2

There was a problem with connecting to a remote database, for the time i 
use the local database, witch is OK for nav.

I get 3 problems:
1 I installed py-rrdtool-1.0b1, with the installation off 
py-rrdtool-0.2.1 I get a error:
building 'rrdtool._rrdtool' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mtune=i686 
-fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -fPIC 
-I/usr/local/include -I/usr/include/python2.5 -c src/_rrdtoolmodule.c -o 
build/temp.linux-i686-2.5/src/_rrdtoolmodule.o
src/_rrdtoolmodule.c: In function âPyRRD_graphâ:
src/_rrdtoolmodule.c:239: error: too few arguments to function ârrd_graphâ
error: command 'gcc' failed with exit status 1

   from the cron I get a mail with the next text:
     File "/usr/local/nav/bin/thresholdMon.py", line 46, in <module>
    from nav.rrd import presenter
  File "/usr/local/nav/lib/python/nav/rrd/presenter.py", line 54, in 
<module>
    import rrdtool
ImportError: dynamic module does not define init function (initrrdtool)

2 and 3  pping and servicemon failed to start, I tried a nav start pping 
servicemon a couple of time, also a start separate.
but they whon't start. I changed DEBUG_LEVEL = 6 in nav.conf, but can't 
(Continue reading)

Morten Brekkevold | 7 Sep 14:05 2007
Picon
Picon

Re: rrdtool and other problems on Suse 10.2

Mels wrote, On 09/06/2007 09:01 PM:

> Hi all,

Hi Mels.

> I started this week with a clean system, installing nav on Suse 10.2
> 
> There was a problem with connecting to a remote database, for the time i
> use the local database, witch is OK for nav.

Ok, if you need some tips on connecting to a remote database, please don't
hesitate to ask :)

> I get 3 problems:
> 1 I installed py-rrdtool-1.0b1, with the installation off
> py-rrdtool-0.2.1 I get a error:
> building 'rrdtool._rrdtool' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mtune=i686
> -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -fPIC
> -I/usr/local/include -I/usr/include/python2.5 -c src/_rrdtoolmodule.c -o
> build/temp.linux-i686-2.5/src/_rrdtoolmodule.o
> src/_rrdtoolmodule.c: In function âPyRRD_graphâ:
> src/_rrdtoolmodule.c:239: error: too few arguments to function ârrd_graphâ
> error: command 'gcc' failed with exit status 1

I did not recognize the version numbers you mentioned, and checking up on
things seems to reveal that there is some confusion about which python-rrdtool
library to use.  Apparently there are two very similar libraries in existance:
One is distributed alongside rrdtool itself, and one is available at
(Continue reading)

Mels | 7 Sep 20:12 2007
Picon

Re: rrdtool and other problems on Suse 10.2

Thanks for your reply.

I removed the rrdtool, wich was from the suse media.
I compiled RRDtool 1.2.15 (the suse version was the same) and install it.
I recompiled psycopg-1.1.21,  the cronjob produced a error.

After this restartapache,tomcat,postgresql and nav
Even pping and servicemon started the first time.

No errormail from the cronjobs, everythings looks fine, til i login in nav:

error

File "/usr/local/nav/lib/python/nav/web/state.py", line 250, in __new__
    raise e

Maybe i have to rebuild more modules?

Mels

Morten Brekkevold wrote:
> Mels wrote, On 09/06/2007 09:01 PM:
>
>   
>> Hi all,
>>     
>
> Hi Mels.
>
>   
(Continue reading)

Mels | 7 Sep 20:37 2007
Picon

Re: Re: rrdtool and other problems on Suse 10.2

That problem solved, was ownership of a few files.

Everything looks fine, start playing with nav.

Mels

Mels wrote:
> Thanks for your reply.
>
> I removed the rrdtool, wich was from the suse media.
> I compiled RRDtool 1.2.15 (the suse version was the same) and install it.
> I recompiled psycopg-1.1.21,  the cronjob produced a error.
>
> After this restartapache,tomcat,postgresql and nav
> Even pping and servicemon started the first time.
>
> No errormail from the cronjobs, everythings looks fine, til i login in 
> nav:
>
> error
>
> File "/usr/local/nav/lib/python/nav/web/state.py", line 250, in __new__
>    raise e
>
> Maybe i have to rebuild more modules?
>
> Mels
>
> Morten Brekkevold wrote:
>> Mels wrote, On 09/06/2007 09:01 PM:
(Continue reading)

Gheorghe Limboi | 9 Sep 22:33 2007
Picon

Re: IP address scope - graphical view / Traffic map load

Hi,

regarding..

> 2. On traffic map -- there is no  load on the link (Load: <0.01% No Data)
> but when I follow the link  (right clik - Load - this open the correct
> cricket graph .. and thre is  load on the link )

I fond this  in tomcat server logs:

SQLException for update statement: SELECT netboxid,descr,name,path,filename,key,value FROM
rrd_file JOIN rrd_datasource USING(rrd_fi
leid) WHERE subsystem='cricket' AND descr IN ('ifOutOctets','ifInOctets') AND ((key='gwport' AND
value IN (33,24,10)))
org.postgresql.util.PSQLException: ERROR: IN types character varying and integer cannot be matched

This seems to be related to postgresql  8.2.x restriction ( I have postgresql-8.2.4 installed). Is there
any  work around or the only way is to downgrade to a lower version of postgresql

tx,
Gheorghe 

----- Original Message ----
From: Morten Brekkevold <morten.brekkevold@...>
To: Gheorghe Limboi <ghitzacatalin@...>
Cc: nav-users@...
Sent: Friday, August 31, 2007 8:40:04 AM
Subject: Re: [Nav-users] IP address scope - graphical view / Traffic map load

Gheorghe Limboi wrote, On 24-08-2007 22:42:
(Continue reading)

Morten Brekkevold | 11 Sep 13:41 2007
Picon
Picon

Re: IP address scope - graphical view / Traffic map load

Gheorghe Limboi wrote, On 09-09-2007 22:33:

> I fond this  in tomcat server logs:
> 
> SQLException for update statement: SELECT netboxid,descr,name,path,filename,key,value FROM
rrd_file JOIN rrd_datasource USING(rrd_fi
> leid) WHERE subsystem='cricket' AND descr IN ('ifOutOctets','ifInOctets') AND ((key='gwport' AND
value IN (33,24,10)))
> org.postgresql.util.PSQLException: ERROR: IN types character varying and integer cannot be matched

Ah, that explains why you're not getting any load data on your traffic map!

> This seems to be related to postgresql  8.2.x restriction ( I have
> postgresql-8.2.4 installed). Is there any  work around or the only way is
> to downgrade to a lower version of postgresql

I don't see any workaround other than downgrading PostgreSQL :-(  I've just
looked at the code that creates the offending SQL statement - it looks hairy,
but I'll try to fix it.  I can post the patch here when it's done, if you like.

--

-- 
mvh
Morten Brekkevold
UNINETT
Morten Brekkevold | 11 Sep 13:45 2007
Picon
Picon

Re: Re: rrdtool and other problems on Suse 10.2

Mels wrote, On 07-09-2007 20:37:
> That problem solved, was ownership of a few files.
> 
> Everything looks fine, start playing with nav.

Great!  Just give a shout if there are any more problems :)

--

-- 
mvh
Morten Brekkevold
UNINETT

Gmane