jailkit-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Jailkit-users] jk_socketd: crash with segfault, max-count sockets: 149


From: Ingo . Lucas
Subject: [Jailkit-users] jk_socketd: crash with segfault, max-count sockets: 149
Date: Fri, 25 Jan 2008 14:57:32 +0100


I hava two problems with jk_socketd (jailkit-2.4.tar.gz).

When i try to start jk_socketd with the standard-script /etc/init.d/jailkit without tty (boot, reboot, cron for test) the jk_socketd-daemon crashes. When i start it interactively there is no problem. /var/log/messages:

Jan 25 11:35:01 jhost jk_socketd[13752]: version 2.4, listening on socket /home/abc/dev/log with rates [512:2048]/10.000000
...
Jan 25 11:35:01 jhost jk_socketd[13752]: version 2.4, listening on socket /home/xyz/dev/log with rates [512:2048]/10.000000
Jan 25 11:35:01 jhost kernel: jk_socketd[13752]: segfault at 0000000000000020 rip 00000000f7e77b2e rsp 00000000ffa09f54 error 4

The second problem is that there seems to be a limit in the max. count  of sockets. If i try to use more than 149 sockets the jk_socketd-daemon crashes again (every user has his own chroot-environment and so his own socket). Here is the output from the command "/etc/init.d/jailkit restart" after adding the 150. socket:

Shutting down jk_socketd:                                             done
Starting JAILKIT services. (jk_socketd)startproc:  signal catched /usr/sbin/jk_socketd: Segmentation fault                                                    failed

Here are some information about my environment:
OS: SLES10, Patchlevel 1 (x86_64)
uname -a : Linux jhost 2.6.16.53-0.16-smp #1 SMP Tue Oct 2 16:57:49 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux

Thank you for your assistence

Ingo
VERLAGSGRUPPE WELTBILD GMBH
Sitz der Gesellschaft: Augsburg
Handelsregister Augsburg HRB 6035 
Ust-ID-Nr: DE 127501299

Geschäftsführung:
Carel Halff (Vorsitzender), Dr. Klaus Driever, Werner Ortner, Herbert Zoch

Vorsitzender des Aufsichtsrates:
Dr. Klaus Donaubauer

reply via email to

[Prev in Thread] Current Thread [Next in Thread]