Menu
▾
▴
#239 Wrapper does not launch on Debian GNU/Linux 6.0
On the current Debian GNU/Linux testing version (6.0) the Wrapper does not launch as it binds to an IPv6 socket only, see wrapper.log below.
Debian 6.0 disabled a common workaround to see if all software is compliant to new IPv6 environments. This workaround will be enabled again in the final Debian 6.0 release, but modern software should also work with the workaround disabled.
Configuration file in Debian 6.0: /etc/sysctl.d/bindv6only.conf
# This sysctl sets the default value of the IPV6_V6ONLY socket option.
#
# When disabled, IPv6 sockets will also be able to send and receive IPv4
# traffic with addresses in the form ::ffff:192.0.2.1 and daemons listening
# on IPv6 sockets will also accept IPv4 connections.
#
# When IPV6_V6ONLY is enabled, daemons interested in both IPv4 and IPv6
# connections must open two listening sockets.
# This is the default behaviour of almost all modern operating systems.
net.ipv6.bindv6only = 1
After changing activate with: sysctl -p /etc/sysctl.d/bindv6only.conf
For discussion see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560238
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562804
wrapper.log:
DEBUG | wrapper | 2010/06/22 13:52:48 | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=300
STATUS | wrapper | 2010/06/22 13:52:48 | Launching a JVM...
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@799134f4
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager: Initializing...
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: JVM #1
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Running a 64-bit JVM.
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Registering shutdown hook
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Using wrapper
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Load native library. One or more attempts may fail if platform specific libraries do not exist. This is NORMAL and is only a problem if they all fail.
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Loaded native library: libwrapper-linux-x86-64.so
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Calling native initialization method.
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperJNI Debug: Inside native WrapperManager initialization method
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Java Version : 1.6.0_17-b04 Java HotSpot(TM) 64-Bit Server VM
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Java VM Vendor : Sun Microsystems Inc.
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: OS Name : Linux
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: OS Arch : amd64
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug:
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Control event monitor thread started.
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Startup runner thread started.
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Communications runner thread started.
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Open socket to wrapper...Wrapper-Connection
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Error: Unexpected exception opening backend socket: java.net.SocketException: Invalid argument
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Debug: Open socket to wrapper...Wrapper-Connection
INFO | jvm 1 | 2010/06/22 13:52:51 | WrapperManager Error: Unexpected exception opening backend socket: java.net.SocketException: Invalid argument
INFO | jvm 1 | 2010/06/22 13:52:52 | WrapperManager Debug: Open socket to wrapper...Wrapper-Connection
INFO | jvm 1 | 2010/06/22 13:52:52 | WrapperManager Error: Unexpected exception opening backend socket: java.net.SocketException: Invalid argument
[...]
INFO | jvm 1 | 2010/06/22 13:53:21 | WrapperManager Error: Unexpected exception opening backend socket: java.net.SocketException: Invalid argument
INFO | jvm 1 | 2010/06/22 13:53:21 | WrapperManager Debug: Open socket to wrapper...Wrapper-Connection
INFO | jvm 1 | 2010/06/22 13:53:21 | WrapperManager Error: Unexpected exception opening backend socket: java.net.SocketException: Invalid argument
ERROR | wrapper | 2010/06/22 13:53:21 | JVM did not exit on request, terminated
DEBUG | wrapper | 2010/06/22 13:53:21 | Signal trapped. Details:
DEBUG | wrapper | 2010/06/22 13:53:21 | signal number=17 (SIGCHLD), source="unknown"
DEBUG | wrapper | 2010/06/22 13:53:21 | Received SIGCHLD, checking JVM process status.
STATUS | wrapper | 2010/06/22 13:53:21 | JVM received a signal SIGKILL (9).
STATUS | wrapper | 2010/06/22 13:53:21 | Automatic JVM Restarts disabled. Shutting down.
STATUS | wrapper | 2010/06/22 13:53:21 | <-- Wrapper Stopped
Other workaround as given in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560056:
Add to wrapper.conf:
wrapper.java.additional.NNN=-Djava.net.preferIPv4Stack=true