Opened 11 years ago
Closed 9 years ago
#3347 closed defect (expired)
cacheex=3 readers sometime stop pushing cache
Reported by: | iluvatar | Owned by: | |
---|---|---|---|
Priority: | minor | Component: | Cache-EX |
Severity: | medium | Keywords: | |
Cc: | Sensitive: | no |
Description
Revision
all versions
Issue Description
cacheex reader no longer actively pushes cache to its peer (using cacheex=3). If you try to pause the reader, via webif, the command does not get processed and webif kind of 'hangs'
When the issue occurs
Usualy after a restart/reboot of the peer, but not always
How the issue is reproducable
setup a cacheex=3 exchange, with peer A as a reader(cccam) and peer B as a user. Now reboot peer B.
Change History (4)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
I have exactly the same problem here. Makes me mad. One client told me not to make excuses because he does not believe me. It's a really annoying problem since it's only recurring on certain peers and not recurring to all peers.
comment:3 by , 11 years ago
After a lot of testing and some info from members of another forum, I found out that the CW Cycle check is the cause of this problem. When CW cycle check is disabled, the reader stay connected and the cache does not stop pushing.
So in fact it is a defect in the CW Cycle Check.
comment:4 by , 9 years ago
Resolution: | → expired |
---|---|
Status: | new → closed |
I've tried to create a logfile, however, as I stated before, it does not happen everytime a cacheex peer reboots. I have several oscam servers with cacheex connections between them, and I have not been able to reproduce this between my own servers