RE: cflowd: utility problems

From: Vincent M Furia (vmf@andrew.cmu.edu)
Date: Mon Apr 02 2001 - 19:22:18 PDT

  • Next message: Paschalis Tsiaras: "compilation error (cflowd-2-1-b1)"

    I'm running cflowdmux, cflowd, and cfdcollect all on the same Linux 2.4.1
    x86 box.

    My cflowd.conf file:
    OPTIONS {
      LOGFACILITY: local6
      TCPCOLLECTPORT: 2056
      PKTBUFSIZE: 2097152
      TABLESOCKFILE: /netflow/etc/cflowdtable.socket
      FLOWDIR: /netflow/data/cflowd/flows
      FLOWFILELEN: 1000000
      NUMFLOWFILES: 10
      MINLOGMISSED: 1000
    }

    COLLECTOR {
      HOST: 128.2.6.81 # IP address of central collector
      ADDRESSES: { 128.2.6.81, 127.0.0.1 }
      AUTH: none
    }

    CISCOEXPORTER {
      HOST: 128.2.0.2 # IP address of Cisco sending data.
      ADDRESSES: { 128.2.0.2, # Addresses of interfaces on Cisco
                      128.2.255.2, # sending data.
                      128.2.4.237 }
      CFDATAPORT: 9995 # Port on which to listen for data.
      SNMPCOMM: 'community' # SNMP community name.
      LOCALAS: 9 # Local AS of Cisco sending data.
      COLLECT: { protocol, portmatrix, ifmatrix, nexthop, netmatrix,
                      asmatrix, tos, flows }
    }

    Thanks,
    Vinny

    On Mon, 2 Apr 2001, Bleik, Mike wrote:

    > Are you running Solaris ???
    >
    > -----Original Message-----
    > From: Vincent M Furia [mailto:vmf@andrew.cmu.edu]
    > Sent: April 2, 2001 2:19 PM
    > To: cflowd@caida.org
    > Subject: cflowd: utility problems
    >
    >
    > I've been unable to use any of the cflowd tools with the exception
    > flowdump.
    >
    > When I try to run "flowwatch '*'" I get the following dumped to the log
    > file:
    > Apr 2 14:06:43 netflow flowwatch: [I] got semaphore: id 0
    > Apr 2 14:06:43 netflow flowwatch: [I] attached to 2101248 byte packet
    > queue at 0x40140000
    > Apr 2 14:06:48 netflow flowwatch: [E] semop(0,0xbffff9e4,2) failed to get
    > semaphore: Interrupted system call {CflowdPacketQueue.cc:416}
    > Apr 2 14:06:48 netflow flowwatch: [E] failed to get lock in
    > ToggleBuffers()!
    > Apr 2 14:06:48 netflow flowwatch: [E] semop(0,0xbffffa18,1) failed to
    > release buffer lock: Resource temporarily unavailable
    > {CflowdPacketQueue.cc:438}
    >
    > When I run cfdnets (or and of the cfd* tools) all I get out put is
    > something like:
    > period: 04/02/2001 13:55:18 - 03/02/2001 13:55:18 EST (0 min, 0 sec)
    >
    > I'm not sure if these problems are connected, but they may be associated
    > with another problem I'm having. cflowd, upon startup, believes the date
    > to be 12/31/1969 19:00:00 EST and this strange times to be progated to the
    > arts++ files. Within approximately 24 hours cflowd recognizes the
    > current date. But for the first several (up to 24), when I run any of the
    > cfd* tools I get the following:
    > period: 12/31/1969 19:00:00 - 12/31/1969 19:00:00 EST (0 min, 0 sec)
    >
    > Any help would be really appreciated.
    >
    > Thanks,
    > Vinny
    >
    > --
    > cflowd mailing list
    > cflowd@caida.org
    >

    --
    cflowd mailing list
    cflowd@caida.org
    



    This archive was generated by hypermail 2b29 : Mon Apr 02 2001 - 19:28:10 PDT