Hi Milo,

Yes, ipdevpolld should run all the time. Is this still a problem?

We anyway need more information in order to understand your problem here. Output of the ipdevpolld log file is helpful.

regards, - Vidar

On 09.09.2011 16:59, izar@condornet.sk wrote:

Hi all,

I'm sorry for spam, but i would like to make sure that it's a real bug not just my mistake/misunderstanding before filling in the bug into lauchpad.

I upgraded NAV to 3.9.1 this monday (deb 5.0) from rep. and I noticed that ipdevpoll job is not running as it supposed to.

If I understand it right, then ipdevpolld should be daemon process running all the time, however in 3.9.1 it's not:

./ipdevpoll status ipdevpolld does not seem to be running...

If I restart NAV ,then ipdevpoll runs just once ....

Thanks, milo

On Fri, 16 Sep 2011 12:32:04 +0200 izar@condornet.sk wrote:

Hi Vidar,

Thanks for your reply, problem disappeared after upgrade to squeeze from lenny.

Hi, being back from my paternal leave, I just want to comment: Yes, this scenario is observed by me too.

NAV 3.9 added support for pynetsnmp as ipdevpoll's primary SNMP library. This is a binding to the C-library NET-SNMP, but apparently there was some bug in the version of the binding that shipped with Debian Lenny, which caused ipdevpoll to quickly crash with a segmentation fault.

The simplest solution for people running NAV 3.9 on Debian Lenny is to uninstall pynetsnmp and let ipdevpoll fall back to using the pure Python PySNMP library.