Opened 11 years ago
Closed 11 years ago
#3428 closed defect (fixed)
Cache-EX mode 3 CCcam Cache Reloop
Reported by: | sat4ber | Owned by: | |
---|---|---|---|
Priority: | critical | Component: | Cache-EX |
Severity: | medium | Keywords: | Cache Reloop |
Cc: | Sensitive: | yes |
Description
Revision
Tested with OSCam 8906 and older version of OScam with or without the CW cycle patch.
Protocol: Cache-EX mode 3 with CCcam
Issue Description
Cache Reloop. Sending the same cache back from who you have received.
Server > Friend (receiving)
Friend (sending the same cache back) > Server
Friend has for now no other cache shares * See example *
I have test this with a other guy and he have the same problems.
When the issue occurs
Everytime or you must put every client in a unique group.
How the issue is reproducable
Put one cache share in a not existing group for example group 50 (user and reader). Give the reader one hop more than the user and you will see that everything you receive is sending back. You don't see this when you have more cache shares.
This problem cause a higher upload traffic.
Example from Friend:
Client Server X X REVERSE CACHE PUSH 0 9425 0 0 0
Reader Server X X REVERSE CACHE PUSH 9425 0 0 0 0
Change History (13)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
CacheEx-Mode3 is running without any problems here.
Please discuss this first in forum, coz this seems to be a configuration problem.
comment:3 by , 11 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:4 by , 11 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
This is NOT a configuration problem. Its an old loop problem that was solved before. Very critical since it also increases cpu usage over 4 times !!
comment:5 by , 11 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
Please discuss this first in the forum with config files.
You can easily create a loop by setting the false groups......
comment:6 by , 11 years ago
If you have 450 clients with cacheex you cannot solve it with separate groups. So please do not close this ticket but give a solution. Since this problem was solved before by node-checking it should not be difficult to put back the old node-checking solution. It only works the old way when you have less than 90 clients with cacheex.
comment:7 by , 11 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
I can confirm; reader is sending back all cache it receives.
Workaround: put all users in a unique group. Give all readers all groups except the one of the corresponding user. Feasible with a small number of readers/users but it becomes complex and unmanageable with larger numbers.