On 12 Dec 2004 at 18:07, Chris Gentile wrote:
bash-2.05b$ more hs_err_pid6154.log
Unexpected Signal : 11 occurred at PC=0x40324F3A
Function=(null)+0x40324F3A
Library=/usr/java/j2sdk1.4.2_04/jre/lib/i386/client/libjvm.so
Signal 11 is segmentation fault isn't it?
NOTE: We are unable to
Quoting Paul Derbyshire [EMAIL PROTECTED]:
The final few lines before the crash would perhaps be more useful.
Then we'd know what it was doing, or trying to do, when it shot
itself in the foot.
Screwing the pooch, maybe?
-todd
___
Support mailing
On 12 Dec 2004 at 21:43, [EMAIL PROTECTED] wrote:
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
Have you done that? Might help. Unlikely, with Sun, but possible.
Are you sure you're not thinking about Microsoft here rather than
Sun? :)
Its been up for hours now.
I pulled a completely new tarball and restarted.
It behaved very differently on startup.
Presumably the start/stop/update scripts changed somewhere along the
lines and the 'old' update script wasn't adequate.
Thanks Anyhow,
Chris
On Sun, 2004-12-12 at 22:38, [EMAIL
Quoting Chris Gentile [EMAIL PROTECTED]:
Haven't been running a node for a few months lately.
So just yesterday I updated and relaunched.
I've wiped my routing clean, my store, and reseeded.
I get a crash like this after at most 2 hours of uptime!
Though you may be able to get help from
