fail to send close messages to the radius server

[Yick Xie]

Hi Nikos,

The stuck process doesn't occupy any CPU time, from ps -elf the process shows:

F S UID        PID  PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY          TIME CMD
5 S nobody   62297 19349  0  80   0 - 10185 sk_wai Jan06 ?
00:00:00 ocserv

The system version is Ubuntu14.04 with the default kernel
3.13.0-32-generic, the libc shows:

 /lib/x86_64-linux-gnu/libc.so.6 --version
GNU C Library (Ubuntu EGLIBC 2.19-0ubuntu6.6) stable release version
2.19, by Roland McGrath et al.
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.8.2.
Compiled on a Linux 3.13.11 system on 2015-02-25.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
libc ABIs: UNIQUE IFUNC
For bug reporting instructions, please see:
<https://bugs.launchpad.net/ubuntu/+source/eglibc/+bugs>.

Regards,
Yick

2016-01-07 20:29 GMT+08:00 Nikos Mavrogiannopoulos
<n.mavrogiannopoulos at gmail.com>:
> On Wed, Jan 6, 2016 at 12:23 PM, Yick Xie <yick.xie at gmail.com> wrote:
>> Hi Nikos,
>> gdb /usr/bin/ocserv 30080
>>
>> (gdb) bt full
>> #0  0x00007f9d0a80538d in __libc_recv (fd=0, buf=0x118ea96, n=154,
>> flags=-1) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:29
>
> What did you see in the process that got stuck? Did it consume a lot
> of CPU time? I see some issues that resemble what you describe are
> caused due to a Linux kernel bug. Which linux kernel and libc do you
> use?
>
> regards,
> Nikos