Opened 6 years ago

Closed 6 years ago

#821 closed defect (no response)

Determine the Root Cause Behind Otherwise Inexplicable Router Self-Tear Downs...

Reported by: guest Owned by:
Priority: minor Milestone:
Component: apps/plugins Version: 0.9.4
Keywords: Router Self-Tear Down test Cc:
Parent Tickets:

Description

Periodically, my router after having been up, and running correctly for multiple hours, will begin tearing itself down, meaning going from 25+ Client Tunnels to > 5 tunnels, in the space of 4-5 minutes. Often, my router can self-recover in 15+ minutes, but I have noted several times where in hung in "limbo" for hours, doing nothing. Snark. Bote, eepsite, iiRC, zzzOT, and outertubes all in concurrent use.

...and, If I remember correctly, this same behaviour has been occurring since 0.9.1.

During these events, Tor continues to function normally.

I2P version: 0.9.4-1
Java version: Oracle Corporation 1.7.0_10 (Java(TM) SE Runtime Environment 1.7.0_10-b18)
Wrapper version: 3.5.nakServer version: 6.1.26
Servlet version: Jasper JSP 2.1 Engine
Platform: Linux amd64 3.6.0-11.dmz.1-liquorix-amd64
Processor: uninitialized (unrecognized)
Jbigi: Locally optimized native BigInteger? library loaded from file
Encoding: UTF-8
Charset: UTF-8

Most Recent, albeit, Partial entry from my Router Logs:

12.26.17.51.12 WARN [Finisher 1/4] router.transport.TransportImpl?: NTCP afterSend slow (success 16051/16051): 1044 byte TunnelDataMessage? 2022521985 from ykmRg7 to g8Dh2w: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:06 GMT 2012 priority 415 targetting g8Dh2wwzGFa1FZQQrvDt-GOlZ777iy7cAGjvYyflrGg=?
12.26.17.51.12 WARN [Finisher 1/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 2022521985 to g8Dh2w took 16051 ms
12.26.17.51.12 WARN [Finisher 3/4] router.transport.TransportImpl?: NTCP afterSend slow (success 14004/14004): 1044 byte TunnelDataMessage? 2852439546 from ykmRg7 to yIrXMG: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:08 GMT 2012 priority 415 targetting yIrXMGnTeD~g7VU6sbVbUadCPdLVPDHoI9IvNvOp4DY=?
12.26.17.51.12 WARN [Finisher 3/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 2852439546 to yIrXMG took 14004 ms
12.26.17.51.12 WARN [Finisher 4/4] router.transport.TransportImpl?: NTCP afterSend slow (success 14207/14207): 1044 byte TunnelDataMessage? 2161672783 from ykmRg7 to yIrXMG: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:08 GMT 2012 priority 415 targetting yIrXMGnTeD~g7VU6sbVbUadCPdLVPDHoI9IvNvOp4DY=?
12.26.17.51.12 WARN [Finisher 4/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 2161672783 to yIrXMG took 14207 ms
12.26.17.51.12 WARN [Finisher 2/4] router.transport.TransportImpl?: NTCP afterSend slow (success 14282/14282): 1044 byte TunnelDataMessage? 1338580806 from ykmRg7 to yIrXMG: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:08 GMT 2012 priority 415 targetting yIrXMGnTeD~g7VU6sbVbUadCPdLVPDHoI9IvNvOp4DY=?
12.26.17.51.12 WARN [Finisher 2/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 1338580806 to yIrXMG took 14282 ms
12.26.17.51.12 WARN [Finisher 1/4] router.transport.TransportImpl?: NTCP afterSend slow (success 14282/14282): 1044 byte TunnelDataMessage? 341291143 from ykmRg7 to yIrXMG: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:08 GMT 2012 priority 415 targetting yIrXMGnTeD~g7VU6sbVbUadCPdLVPDHoI9IvNvOp4DY=?
12.26.17.51.12 WARN [Finisher 1/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 341291143 to yIrXMG took 14282 ms
12.26.17.51.12 WARN [Finisher 3/4] router.transport.TransportImpl?: NTCP afterSend slow (success 14394/14393): 1044 byte TunnelDataMessage? 2019821309 from ykmRg7 to yIrXMG: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:08 GMT 2012 priority 415 targetting yIrXMGnTeD~g7VU6sbVbUadCPdLVPDHoI9IvNvOp4DY=?
12.26.17.51.12 WARN [Finisher 3/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 2019821309 to yIrXMG took 14393 ms
12.26.17.51.12 WARN [Finisher 4/4] router.transport.TransportImpl?: NTCP afterSend slow (success 8454/8454): 1044 byte TunnelDataMessage? 1446070206 from ykmRg7 to XM6WHC: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:14 GMT 2012 priority 415 targetting XM6WHC6YAaVhP7CWiAPLsn98oagV9Jp75HeC4TRAscM=?
12.26.17.51.12 WARN [Finisher 4/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 1446070206 to XM6WHC took 8454 ms
12.26.17.51.12 WARN [Finisher 2/4] router.transport.TransportImpl?: NTCP afterSend slow (success 14479/14479): 1044 byte TunnelDataMessage? 1478947438 from ykmRg7 to yIrXMG: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:08 GMT 2012 priority 415 targetting yIrXMGnTeD~g7VU6sbVbUadCPdLVPDHoI9IvNvOp4DY=?
12.26.17.51.12 WARN [Finisher 2/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 1478947438 to yIrXMG took 14479 ms
12.26.17.51.12 WARN [Finisher 1/4] router.transport.TransportImpl?: NTCP afterSend slow (success 14480/14480): 1044 byte TunnelDataMessage? 2586876124 from ykmRg7 to yIrXMG: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:08 GMT 2012 priority 415 targetting yIrXMGnTeD~g7VU6sbVbUadCPdLVPDHoI9IvNvOp4DY=?
12.26.17.51.12 WARN [Finisher 1/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 2586876124 to yIrXMG took 14480 ms
12.26.17.51.12 WARN [Finisher 3/4] router.transport.TransportImpl?: NTCP afterSend slow (success 14673/14673): 1044 byte TunnelDataMessage? 1559363939 from ykmRg7 to yIrXMG: containing a 1044 byte TunnelDataMessage expiring on Wed Dec 26 17:51:07 GMT 2012 priority 415 targetting yIrXMGnTeD~g7VU6sbVbUadCPdLVPDHoI9IvNvOp4DY=?
12.26.17.51.12 WARN [Finisher 3/4] router.transport.TransportImpl?: NTCP afterSend slow: success 1044 byte TunnelDataMessage? 1559363939 to yIrXMG took 1467

Subtickets

Change History (3)

comment:1 Changed 6 years ago by zzz

The first thing I suggest you try is disabling bote. See several tickets here about bote's problems. If that doesn't work, try disabling the other plugins too.

It's also helpful to keep an eye on the router memory graph.

comment:2 Changed 6 years ago by str4d

  • Keywords test added
  • Milestone 0.9.5 deleted

comment:3 Changed 6 years ago by zzz

  • Component changed from unspecified to apps/plugins
  • Resolution set to no response
  • Status changed from new to closed

No response, closing. Assumed to be bote-related. Please reopen if you do respond.

Note: See TracTickets for help on using tickets.