Restarting ocserv doesn't clean up all workers

Nikos Mavrogiannopoulos n.mavrogiannopoulos at
Wed Sep 24 07:44:54 PDT 2014

On Wed, Sep 24, 2014 at 4:25 PM, Niels Peen <niels at> wrote:
> I noticed when I stop or restart ocserv it will occasionally leave one or more
> worker processes behind.
> These processes appear idle and unused. Attaching an strace shows them waiting
> to receive something, which never changes:
> #strace -p 510
> Process 510 attached - interrupt to quit
> recvfrom(8,
> Could this be related to the EGAIN issue?

Could you provide the log output of such cases? Unless killed with
SIGKILL ocserv shouldn't have left children hanging.


More information about the openconnect-devel mailing list