Menu

#50 A lot of disconnected from same ip in network status window

open
nobody
None
6
2005-02-02
2004-07-27
Anonymous
No

I get a lot of disconnected lines in the network status
window (mostly from the same id). This (probably) causes
waste to freak out and eat all the cpu time. I tried to
disable the routing option, but no luck.

The ip/user is a valid user, and i got his public key.

See the attached screenshot.

Discussion

  • Eric

    Eric - 2004-09-10

    Logged In: YES
    user_id=945916

    The screenshot was never attached, can you please attach it to more clearly explain the problem?

     
  • Chris

    Chris - 2004-09-27

    Logged In: YES
    user_id=573676

    Can't reproduce and the poster isn't offering any more
    information, I'm going to reduce the priority on this until
    anonymous returns to explain his problem more concretely.

     
  • Chris

    Chris - 2004-09-27
    • priority: 5 --> 2
     
  • Adam

    Adam - 2005-02-02

    Logged In: YES
    user_id=1066359

    I can corroborate this one, as can two others on my network.
    In addition to the symptom the OP described, the following
    lines are hosing down the log file with thousands of entries:

    (3)Error :<05/02/01 22:23:01:46231> connection::run:
    select() notified of error
    (3)Error :<05/02/01 22:23:04:46232> connection::run:
    select() notified of error
    (3)Error :<05/02/01 22:23:07:46233> connection::run:
    select() notified of error
    (3)Error :<05/02/01 22:23:34:46234> connection::run:
    select() notified of error
    (3)Error :<05/02/01 22:23:37:46235> connection::run:
    select() notified of error
    (3)Error :<05/02/01 22:23:40:46236> connection::run:
    select() notified of error
    (3)Error :<05/02/01 22:23:43:46237> connection::run:
    select() notified of error

    It's just one or two selected clients on the network, not
    random. It started happening after we all upgraded from 1.4
    to 1.5b2. The clients in question are on a variety of
    different network types/speeds.

     
  • Chris

    Chris - 2005-02-02
    • priority: 2 --> 6
     
  • Chris

    Chris - 2005-02-02

    Logged In: YES
    user_id=573676

    Same as bug #1070734

    Thanks for the extra input, rumblies. Those error messages
    will help. I have promoted this bug to #6 to match it's
    duplicate. This will be fixed for 1.5final

     

Log in to post a comment.

MongoDB Logo MongoDB