cflowd: utility problems

From: Vincent M Furia (
Date: Mon Apr 02 2001 - 11:19:19 PDT

  • Next message: Vincent M Furia: "RE: cflowd: utility problems"

    I've been unable to use any of the cflowd tools with the exception

    When I try to run "flowwatch '*'" I get the following dumped to the log
    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 {}
    Apr 2 14:06:48 netflow flowwatch: [E] failed to get lock in
    Apr 2 14:06:48 netflow flowwatch: [E] semop(0,0xbffffa18,1) failed to
    release buffer lock: Resource temporarily unavailable

    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.


    cflowd mailing list

    This archive was generated by hypermail 2b29 : Mon Apr 02 2001 - 11:36:32 PDT