On Saturday 19 June 2010 03:36:22 Paul Landers wrote: > Does anyone have any success running fred ipv4 + ipv6 (I'm assuming > there are some ipv6 nodes out there)? I have a functioning ipv4 node > on Debian, but if I then enable ipv6 on my machine (a freenet6 tunnel) > and restart fred my node never starts. wrapper.log simply says: > > ... > INFO | jvm 1 | 2010/06/18 21:13:02 | Using the NativeThread > implementation (base nice level is 13) > INFO | jvm 1 | 2010/06/18 21:13:47 | Initializing Node using > Freenet Build #1253 rbuild01253 and freenet-ext Build #26 r23771 with > Sun Microsystems Inc. JVM version 1.6.0_20 running on i386 Linux > 2.6.32-trunk-686 > > INFO | jvm 1 | 2010/06/18 21:13:57 | Starting FProxy on > 127.0.0.1,0:0:0:0:0:0:0:1:8888 > INFO | jvm 1 | 2010/06/18 21:14:01 | INFO: Native CPUID library > 'freenet/support/CPUInformation/libjcpuid-x86-linux.so' loaded from > resource > INFO | jvm 1 | 2010/06/18 21:14:01 | > INFO | jvm 1 | 2010/06/18 21:14:01 | INFO: Optimized native > BigInteger library 'net/i2p/util/libjbigi-linux-athlon.so' loaded from > resource > ERROR | wrapper | 2010/06/18 21:21:41 | Startup failed: Timed out > waiting for signal from JVM. > ERROR | wrapper | 2010/06/18 21:21:41 | JVM did not exit on request, > terminated > STATUS | wrapper | 2010/06/18 21:21:42 | JVM exited in response to > signal SIGKILL (9). > ERROR | wrapper | 2010/06/18 21:21:42 | Unable to start a JVM > STATUS | wrapper | 2010/06/18 21:21:42 | <-- Wrapper Stopped > > Anyone with some tips on using ipv6 and fred?
Very interesting! Might be related to Windows startup failures too in some cases. Can you get a stack dump during the 40 seconds above? Use ./run.sh dump, it will dump a load of information about what the node is doing to wrapper.log, send me the file.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Support mailing list [email protected] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[email protected]?subject=unsubscribe
