Opened 7 years ago

Closed 6 years ago

#810 closed defect (duplicate)

IRC connections become unstable

Reported by: efkt Owned by:
Priority: minor Milestone: 0.9.7
Component: streaming Version: 0.9.3
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

Hi. IRC connections become unstable after router has been running for about a week or two. After a fresh router restart, I can stay logged in to IRC (irc2p network) for many hours without issue. After the router has been running (for example) for a week or two, my connections become unstable, and I can only stay connected for about 1 hour (give or take). This has been observable for me from at least 0.9.1. (currently running 0.9.3 - release) and the symptom is consistent and observable - I've been watching the issue and I've tried using backup tunnels (up to 3). The behavior is observable regardless of IRC client. The issue seems to resolve itself if my router is restarted, and does not occur for several days.

There are two entries in my wrapper.log that might be of interest.

The first occurs about 7 times in wrapper.log since September (now December)

CRIT [uterWatchdog] 2p.router.tasks.RouterWatchdog?: Router appears hung, or there is severe network congestion. Watchdog starts barking!

After startup in wrapper.log:

WARNING: Native BigInteger? library jbigi not loaded - using pure Java - poor performance may result - see http://www.i2p2.i2p/jbigi for help

Notes: I use runplain.sh due to OS.


I2P version: 0.9.3-0
Java version: Oracle Corporation 1.7.0_03 (OpenJDK Runtime Environment 1.7.0_03-b04)
Wrapper version: none
Server version: 6.1.26
Servlet version: Jasper JSP 2.1 Engine
Platform: OpenBSD i386 5.2
Processor: uninitialized (unrecognized)
Jbigi: Native BigInteger? library jbigi not loaded - using pure Java - poor performance may result - see http://www.i2p2.i2p/jbigi for help
Encoding: ISO646-US
Charset: US-ASCII

Subtickets

Change History (3)

comment:1 Changed 6 years ago by str4d

Milestone: 0.9.4

comment:2 Changed 6 years ago by zzz

Component: unspecifiedstreaming
Milestone: 0.9.8
Priority: trivialminor

Yeah, this happens to me too, after about 4 days.

The wrapper logs are unrelated.

comment:3 Changed 6 years ago by zzz

Milestone: 0.9.80.9.7
Resolution: duplicate
Status: newclosed

See #644 for resolution

Note: See TracTickets for help on using tickets.