Opened 6 years ago

Closed 5 years ago

#1228 closed defect (no response)

The i2p router inexpectedly shutdowns: Router appears hung, or there is severe network congestion.

Reported by: ak47 Owned by: zzz
Priority: major Milestone:
Component: router/general Version: 0.9.11
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

My i2p router shutdown unexpectedly. wrapper.log information follows:

###############

| "Finalizer" #3 daemon prio=8 os_prio=0 tid=0x008f6348 nid=0x82e in Object.wait() [0xaba64000]
| java.lang.Thread.State: WAITING (on object monitor)
| at java.lang.Object.wait(Native Method)
| at java.lang.ref.ReferenceQueue?.remove(ReferenceQueue?.java:142)
| - locked <0xaece5670> (a java.lang.ref.ReferenceQueue?$Lock)
| at java.lang.ref.ReferenceQueue?.remove(ReferenceQueue?.java:158)
| at java.lang.ref.Finalizer$FinalizerThread?.run(Finalizer.java:209)
|
| "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x008f4f48 nid=0x82d in Object.wait() [0xabab4000]
| java.lang.Thread.State: WAITING (on object monitor)
| at java.lang.Object.wait(Native Method)
| at java.lang.Object.wait(Object.java:502)
| at java.lang.ref.Reference$ReferenceHandler?.run(Reference.java:157)
| - locked <0xaece5810> (a java.lang.ref.Reference$Lock)
|
| "VM Thread" os_prio=0 tid=0x008f1128 nid=0x82c runnable
|
| "VM Periodic Task Thread" os_prio=0 tid=0x008a4a88 nid=0x832 waiting on condition
|
| JNI global references: 79
|
| Heap
| def new generation total 26240K, used 16978K [0xac200000, 0xade60000, 0xaeca0000)
| eden space 23424K, 64% used [0xac200000, 0xad0cfa48, 0xad8e0000)
| from space 2816K, 64% used [0xad8e0000, 0xadaa7428, 0xadba0000)
| to space 2816K, 0% used [0xadba0000, 0xadba0000, 0xade60000)
| tenured generation total 57924K, used 44872K [0xaeca0000, 0xb2531000, 0xb4200000)
| the space 57924K, 77% used [0xaeca0000, 0xb1872218, 0xb1872400, 0xb2531000)
| Metaspace used 15846K, capacity 16026K, committed 16152K, reserved 16688K
|
| CRIT [uterWatchdog] 2p.router.tasks.RouterWatchdog?: Router appears hung, or there is severe network congestion. Watchdog starts barking!
| CRIT [uterWatchdog] et.i2p.router.tasks.ThreadDump?: Threads dumped to wrapper log

###############

The router was running on a Raspberry Pi, 3.10.25+ armv6l GNU/Linux, Raspbian system, jdk1.8.0 (Early Access). {Java™ SE Runtime Environment (build 1.8.0-b129) Java HotSpot?™ Client VM (build 25.0-b69, mixed mode)}

Subtickets

Change History (6)

comment:1 Changed 6 years ago by zzz

There's nothing there about a crash. Check router log files for more clues. How long between the thread dump and the crash?

My RPi isn't restarting correctly either. Haven't had time to look into it yet. What's your wrapper version?

comment:2 Changed 6 years ago by ak47

I don't find clues in the routers log file. Just problems with a plug-in failing to update because not finding an URL (most likely due to network congestion because of the execution environment)

The wrapper is:

Java Service Wrapper Community Edition 32-bit 3.5.22
| Copyright © 1999-2013 Tanuki Software, Ltd. All Rights Reserved.
| http://wrapper.tanukisoftware.com

comment:3 in reply to:  1 Changed 6 years ago by killyourtv

Replying to zzz:
..

My RPi isn't restarting correctly either. Haven't had time to look into it yet.

Same. I'm not having problems with crashing, however. But when I click the restart button, I2P doesn't restart.

One of these days I'll try to troubleshoot it, tweaking timeout variables and whatnot.

comment:4 Changed 6 years ago by zzz

#1230 entered for the RPi-doesn't-restart problem.

comment:5 Changed 6 years ago by zzz

Component: router/transportrouter/general
Milestone: 0.9.12
Status: newinfoneeded_new

Setting to info-needed as we have no evidence of a crash. It is fairly easy to overload a RPi if the peer, bandwidth, or tunnel limits are too high. The restart issue #1230 is fixed.

comment:6 Changed 5 years ago by zzz

Resolution: no response
Status: infoneeded_newclosed
Note: See TracTickets for help on using tickets.