Opened 6 years ago

Closed 6 years ago

#4667 closed defect (wontfix)

Hight CPU load from oscam #cacheex-oscam #r11420

Reported by: Screamfox Owned by:
Priority: blocker Component: General
Severity: high Keywords: cacheex mod 2
Cc: Sensitive: no

Description

Revision

OSCam: 1.20-unstable_svn Build: r11420 Compiler: x86_64-linux-gnu-ssl-libusb-pcsc

Issue Description

Well, i am using cacheex cs378x mod 2 in a vps with this info:

This is the info about my vps:

Operating system Ubuntu Linux 17.10
Time on system: Sat Apr 21 13:56:27 2018
Kernel and CPU: Linux 4.13.0-17-generic on x86_64
Processor information: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz, 6 cores
CPU load averages 5.19 (1 min) 2.13 (5 mins) 0.89 (15 mins)
CPU usage: 31% user, 40% kernel, 0% IO, 25% idle
Real memory: 661.37 MB used, 29.45 GB total

so when i put the command top i have this 181% of cpu consummation (see attachement)

the configs i have is (see attachement)

and after some minutes, the oscam crash and i can't open the webinfo, and the people share with my say the server is off but i can see oscam running in process(using command top)..

When the issue occurs

after some minutes (80 minutes) oscam run, and after my peers complaints have freezes and some time the server don't show as connected in their oscam, so basicly oscam crash completele

How the issue is reproducable

Using Cacheex mod2 in cs378x

Attachments (4)

commandTOP.txt (191 bytes ) - added by Screamfox 6 years ago.
oscam.conf (6.5 KB ) - added by Screamfox 6 years ago.
oscam.server.log (2.4 KB ) - added by Screamfox 6 years ago.
oscam.user.log (1.8 KB ) - added by Screamfox 6 years ago.

Download all attachments as: .zip

Change History (8)

by Screamfox, 6 years ago

Attachment: commandTOP.txt added

by Screamfox, 6 years ago

Attachment: oscam.conf added

by Screamfox, 6 years ago

Attachment: oscam.server.log added

by Screamfox, 6 years ago

Attachment: oscam.user.log added

comment:1 by Screamfox, 6 years ago

I have this problem from some month but if i put every users in hop 2 is ok, but they complaints don't have hits so i put cacheexmax hop 3 and cpu load go up and after some minutes the oscam crash, and he consume 170~190 % cpu and crash.... i have 6 cores from a xeon E5 family, so i don't think the problem is from here,
probably some configs... or other mistake ...

if some body can tell me how can i fix this problem, is very welcome here

regards

comment:2 by Screamfox, 6 years ago

Component: ! Please select...General

comment:3 by Screamfox, 6 years ago

in my log i have a lot of this messages

2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push
2018/04/21 22:06:40 17C65B55 c   (camd35) cacheex: nodelist reached 2 nodes, no push

comment:4 by Gorgone Impertinence, 6 years ago

Resolution: wontfix
Status: newclosed

check config

Note: See TracTickets for help on using tickets.