Menu

#16 error: "No such file or directory" reading key "net.netflow.

v1.6
open
nobody
5
2009-07-24
2009-07-01
Anonymous
No

Sometimes after server reload any flows do not export to netflow collector.
sysctl -a | grep netflow:
net.netflow.active_timeout = 1800
net.netflow.inactive_timeout = 15
net.netflow.debug = 0
net.netflow.hashsize = 65536
error: "No such file or directory" reading key "net.netflow.sndbuf"
net.netflow.destination = 127.0.0.1:9000
net.netflow.aggregation = none
net.netflow.maxflows = 2000000

I found only 1 decision - manualy reload module.
After reload module works fine. And in sysctl -a | grep netflow:
net.netflow.active_timeout = 1800
net.netflow.inactive_timeout = 15
net.netflow.debug = 0
net.netflow.hashsize = 65536
net.netflow.sndbuf = 260000
net.netflow.destination = 127.0.0.1:9000
net.netflow.aggregation = none
net.netflow.maxflows = 2000000

Discussion

  • Nobody/Anonymous

    I have understood!
    I put module initialization in /etc/modules.autoload.d/kernel-2.6
    So module loaded on boot runlevel when there is no any interface including lo.
    Now I load module after creating lo.

     
  • ABC

    ABC - 2009-07-24
    • labels: 1163922 --> Installation problem
     
  • ABC

    ABC - 2009-07-24

    You are right, module should be loaded after network infrastructure.

     
  • Nobody/Anonymous

    Please, add this note to README

     
  • ABC

    ABC - 2009-08-08

    Adding this to troubleshoting section of README:

    3) For autoloading module after reboot: set net.netflow.destination (or load
    module if it set on load) after interfaces loaded. Becasue module need
    exporting interface up (usually lo) to establish export connection.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.