Opened 9 years ago

Closed 9 years ago

#3998 closed defect (invalid)

Massive cacheex ERR with build 10005, 10006, 10007 or 10008

Reported by: Dimmie Owned by: blueven
Priority: critical Component: Cache-EX
Severity: high Keywords: Cacheex ERR
Cc: Sensitive: yes

Description

Since the latest patches by blueeven you will get massive cacheex errors.

Just install 10005, 10006, 10007 or 10008 with some cacheex partners and then check the CacheEx Stats > you will see thousends of cacheex errors for each user. Till 10004 everything is fine.

Change History (15)

comment:1 by ursus007, 9 years ago

I confirm I have the same error

comment:2 by capncook, 9 years ago

Owner: set to blueven

From release 10006

  • only CWs are accepted that have a odd/even byte attached. CWs without odd/even bytes are rejected. (some reported an exception on CAID 2600, that needs fixing).
  • only correct NDS halfpair/fullpair CWs are accepted. So example 0963 = halfpair, so fullpairs get rejected.

--

However, i did some logging, and seen a possible bug in rejecting halfpair-cws. I have sent blueven a detailed log about this, so that will be analysed.

=> Therefore, leaving the ticket open.

comment:3 by Dimmie, 9 years ago

Some more testing also indicates that when the other partner is using an old version of oscam (like 9031), their cache will become totally unusable since build 100005 and you will zero hits.

comment:5 by RuBeN, 9 years ago

R10008 ws R10008 ok no error;)

please tell your peers to update oscam ;)

Last edited 9 years ago by RuBeN (previous) (diff)

comment:6 by Dimmie, 9 years ago

Also R10008 to R10008 generates massice cacheex errors, so telling peers to update is no solution.

comment:7 by horizon1, 9 years ago

I get a huge number cacheex errors, even with version 10004. Now I tried, 10001 and I see that vichko looks normal, without errors

comment:8 by jrk, 9 years ago

CACHE ERROR = bad half CW or ecm with null odd/even byte.

It's OK

comment:9 by blueven, 9 years ago

Resolution: invalid
Status: newclosed

If you like having good numbers in webif, you can use which oscam you want! If you want use correct oscam, use latest, that is safest and working correctly.

comment:10 by Dimmie, 9 years ago

Resolution: invalid
Status: closedreopened

Please read again:

Also R10008 to R10008 generates massive cacheex errors, so telling peers to update is no solution.

comment:11 by Dimmie, 9 years ago

It's not about numbers, it's about oscam dropping cache that should not be dropped. I now suddenly have several peers from who ALL cache is suddenly ERR ? I don't think so..

comment:12 by gismo2004, 9 years ago

Log?

comment:13 by michel, 9 years ago

i have the same problem if i rum oscam whits -d 512 the cache size is oke 25000 - 30000 if i run oscam whit out -d 512 the cache drops to 3000

i dont now how to fix it

comment:14 by bcs, 9 years ago

PLEASE, all who think have problem with new blueven fix for nds swap, POST your config and LOG -d 512, otherwise DO NOT write on ticket, but use instead the streamboard to discuse. I think the ones who have problems, have wrong config and exchnage with peers with old oscam. Thk

comment:15 by capncook, 9 years ago

Resolution: invalid
Status: reopenedclosed

To be strict with the ticket scope, The ERR are valid. See streamboard thread mentioned earlier in comments. Before re-opening, discuss any remaining issue on the forum first please.

Note: See TracTickets for help on using tickets.