Opened 7 years ago

Closed 6 years ago

#796 closed defect (no response)

I2p Router crashing often

Reported by: DISABLED Owned by:
Priority: major Milestone:
Component: wrapper Version: 0.9.3
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

The router started crashing silently two days ago. Originally it was twice , then accelerating until it seems to crash every hour or so.
Running the latest Fux :) I2P 0.9.3-10-fux
Robert is using Bob
IRC is tunnel is in use
It seems the Java Runtime is running into trouble
log of the error is included - Nothing else in the log shows an error except an issue when I restart the router because the old router didn't exit gracefully.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x01094d8f, pid=2048, tid=3040357184
#
# JRE version: 6.0_24-b24
# Java VM: OpenJDK Client VM (20.0-b12 mixed mode, sharing linux-x86 )
# Derivative: IcedTea6 1.11.5
# Distribution: Ubuntu 12.04 LTS, package 6b24-1.11.5-0ubuntu1~12.04.1
# Problematic frame:
# V [libjvm.so+0x2f3d8f] objArrayKlass::oop_follow_contents(oopDesc*)+0xef
#
# An error report file with more information is saved as:
# /usr/local/i2p/hs_err_pid2048.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
#
JVM received a signal UNKNOWN (6).
JVM process is gone.
JVM exited unexpectedly.

Subtickets

Attachments (9)

error_again.txt (4.1 KB) - added by DISABLED 7 years ago.
error_again_again.txt (13.8 KB) - added by DISABLED 7 years ago.
Fun. fun, fun!
hs_err_pid5427.log (35.7 KB) - added by DISABLED 7 years ago.
hs_err_pid5882.log (37.2 KB) - added by DISABLED 7 years ago.
hs_err_pid10111.log (24.2 KB) - added by DISABLED 7 years ago.
hs_err_pid14030.log (36.6 KB) - added by DISABLED 7 years ago.
hs_err_pid18156.log (36.2 KB) - added by DISABLED 7 years ago.
hs_err_pid20612.log (34.5 KB) - added by DISABLED 7 years ago.
hs_err_pid28875.log (35.8 KB) - added by DISABLED 7 years ago.

Download all attachments as: .zip

Change History (21)

comment:1 Changed 7 years ago by dg

I'm no expert, but maybe:

# An error report file with more information is saved as:
# /usr/local/i2p/hs_err_pid2048.log

.. would provide some helpful information(?).

comment:2 Changed 7 years ago by DISABLED

You would think so, wouldn't you :)
I'm no expert either, but I would think dumping a log that has a shit load of identifying data on a public site in i2p would be a great way of limiting ones anonymity, especially when it is given to those who actually know how the whole system works…
Don't you think?

I will watch the ticket for questions…
*Further info* - After stopping Robert and IRC client it has run without crashing for 8 hours or so. Started Robert but will stay off IRC and see if it crashes, then will do the reverse (run IRC but not Robert)

comment:3 Changed 7 years ago by DISABLED

Right- It has crashed multiple times in just a few hours with Robert running (using Bob) - The same error with the JRE.
Without Robert running (or IRC) it has been up for quite a while (Bob client is still running BTW)

Changed 7 years ago by DISABLED

Attachment: error_again.txt added

comment:4 Changed 7 years ago by DISABLED

Well, it was happy for a while, but Once I had the IRC client using the tunnel, it fell over again, multiple times.
Looking at the log (attached - I have left the minutes &seconds in it), it seem that the Java VM falls over & then recovers multiple times, and then i2p restarts OK:
46:01 | JVM exited unexpectedly.
46:16 | Launching a JVM…
46:16 | WrapperManager?: Initializing…
46:16 | Starting I2P 0.9.3-10-fux

But after a while - it dies due to an existing .ping file:
15:06 | JVM exited unexpectedly.
15:21 | Launching a JVM…
15:21 | WrapperManager?: Initializing…
15:22 | Starting I2P 0.9.3-10-fux
15:22 | ERROR: There appears to be another router already running!
15:22 | Please make sure to shut down old instances before starting up
15:22 | a new one. If you are positive that no other instance is running,
15:22 | please delete the file /home/pbdesktop/.i2p/router.ping
15:24 | ←- Wrapper Stopped

Full log attached.

At this stage, It can run the router , but if I try to use it, it crashes… I wonder if others have this and just give up? Note that this only started happening a few days ago - Not 100% sure what changed.

comment:5 Changed 7 years ago by DISABLED

This is getting worse :(
I am considering removing i2p from my system and starting again - I really do wonder if others try it, end up with problems like this and just give up :(
The router rand for about 8 hours with me not using it, but it was creating tunnels etc all OK, then it crashed with the errors shown already (VM died repeatedly and then then after a few successful restarts of the wrapper, it dies with an existing ".ping" file) whilst i was having a meal.
When I restart it manually (and i don't delete the .ping BTW) it crashed again, restart, crash, restart crash. I restarted the computer, and now I am seeing a NEW critical error in the logs (attached) - this is happening every few minutes.., sigh.

CRIT [receiver 4/5] .transport.udp.MessageReceiver?: Error dealing with a message: IB Message: 3074778512 from [Hash: yvc3omzF69Lz0j9V5HRNheSyU5MYmI94VLelWAZsdvU=] fragment 0: unknown lifetime: 1

java.lang.IllegalStateException?: Use after free: 3074778512

just for the record:
I2P version: 0.9.3-11-fux
Java version: Sun Microsystems Inc. 1.6.0_24 (OpenJDK Runtime Environment 1.6.0_24-b24)
Wrapper version: 3.5.15
Server version: 6.1.26
Servlet version: Jasper JSP 2.1 Engine
Platform: Linux i386 3.2.0-23-generic
Processor: Pentium IV (65 nm) (pentium4)
Jbigi: Locally optimized native BigInteger? library loaded from file
Encoding: UTF-8
Charset: UTF-8

Changed 7 years ago by DISABLED

Attachment: error_again_again.txt added

Fun. fun, fun!

comment:6 Changed 7 years ago by killyourtv

CRIT [receiver 4/5] .transport.udp.MessageReceiver?: Error dealing with a message: IB Message: 3074778512 from [Hash: yvc3omzF69Lz0j9V5HRNheSyU5MYmI94VLelWAZsdvU=] fragment 0: unknown lifetime: 1

This error does not exist in -12. The 'fux' people need to update their build.

This would not cause the crashing, though.

comment:7 Changed 7 years ago by killyourtv

…or maybe they did update it. Their site still shows -11 as the most recent so I dunno.

comment:8 Changed 7 years ago by Eche|on

What is fux?
Looks like a openJDK problem to me.
The already running router is to be solved with hard killing all java processes before starting newer one.

echelon

comment:9 Changed 7 years ago by zzz

Owner: set to str4d
Status: newassigned

The crashes dumping hs_err files are unlikely to be our fault. Generally caused by bad RAM (run a RAM diagnostic test) or Java bugs (update your JVM to the latest). But in any case, we can't help you unless you are willing to attach the hs_err file.

The NoSuchElementException? in CachedIteratorArrayList? was a bug in -11, fixed in -12, see http://zzz.i2p/topics/1288 for details.

The IllegalStateException? I haven't seen in a long time, killyourtv above in comment 6 says it's fixed in -12? Not sure what's in -12 (I have been away for a week).

The 'another router running' message means exactly what it says, and it includes instructions on how to delete the ping file.

In the future, please file separate tickets for separate issues. It's very difficult to keep track of multiple problems in a single ticket. There's at least 4 issues here.

Since this is reported on the experimental -fux build, I'm assigning this ticket to str4d to make sense of it all.

Please assign all future -fux tickets to str4d.

comment:10 Changed 7 years ago by DISABLED

Component: unspecifiedwrapper
Summary: Ip2 Router crashing oftenI2p Router crashing often

I also get the same problem in 1.9.3, i have many logdiles which i will upload shortly.

Running freebsd i2p simply stops regularly, this has only happened in 0.9.3

changed to wrapper since as i understand it the wrapper's job is to estart i2p id it dies.

Changed 7 years ago by DISABLED

Attachment: hs_err_pid5427.log added

Changed 7 years ago by DISABLED

Attachment: hs_err_pid5882.log added

Changed 7 years ago by DISABLED

Attachment: hs_err_pid10111.log added

Changed 7 years ago by DISABLED

Attachment: hs_err_pid14030.log added

Changed 7 years ago by DISABLED

Attachment: hs_err_pid18156.log added

Changed 7 years ago by DISABLED

Attachment: hs_err_pid20612.log added

Changed 7 years ago by DISABLED

Attachment: hs_err_pid28875.log added

comment:11 Changed 7 years ago by str4d

Milestone: 0.9.4
Owner: str4d deleted

Fux only differs from trunk in the UI; there are no core changes, so any problems like the above in Fux would also occur with the equivalent trunk build.

As above, the build in question was a (now rather old) dev build and some of the problems have since been fixed. Could the OP (and the second poster) please confirm whether they still have (any of) these problems when using current builds?

comment:12 Changed 6 years ago by str4d

Resolution: no response
Status: assignedclosed

OP: re-open this ticket if you are still having any of these problems with current builds.

Note: See TracTickets for help on using tickets.