ocserv-worker 100% CPU USAGE

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

 



No. also I checked syslog to see if worker process has logged anything
before hanging but there is only one line containing worker process
PID:

root at X:/var/log# grep 13880 syslog
Aug 22 07:32:36 sd-48811 ocserv[8975]: main: main.c:451: Child 13880
died with signal 9 (Yes, I had to kill it with kill -9)

I dont know if it is placebo or just luck, but I feel the frequency of
hanging workers has decreased significantly after using git version.
I had to observe processes for two days to catch one hanging process.
I am telling you this because MAY BE you have fixed one bug but a
similar bug may exist somewhere else in the code causing this loop or
the fix has mitigated the problem but not completely averting it.

On Fri, Aug 22, 2014 at 4:17 PM, Nikos Mavrogiannopoulos
<n.mavrogiannopoulos at gmail.com> wrote:
> On Fri, Aug 22, 2014 at 7:09 AM, Farzad Fallah <farzad.fallah at gmail.com> wrote:
>> Unfortunately the git version didnt resolve the issue. I am still
>> getting workers using 100% CPU.
>> Here is a strace :
>> pselect6(22, [4 7 8 21], NULL, NULL, {10, 0}, {[], 8}) = 1 (in [7],
>> left {9, 999997763})
>> recvfrom(5, 0xad9330, 18780, 0, 0, 0)   = -1 EBADF (Bad file descriptor)
>
> Thank you. That's pretty informative. Do you see anything at syslog at
> that time?
>
> regards,
> Nikos



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux