Opened 9 years ago
Closed 9 years ago
#4111 closed defect (fixed)
Disconnected: RTO on Cs357x Reader doing Cachex 3
Reported by: | thot1414 | Owned by: | |
---|---|---|---|
Priority: | minor | Component: | Cache-EX |
Severity: | low | Keywords: | Cache-EX Cs357x |
Cc: | Sensitive: | no |
Description
Revision
Issue Description
After about 2 Minutes Cs357x Cachex 3 (Push) Reader disconnects with RTO. It takes about 30 secound to connect again. Setting Client max idle to any value >=0 dosen't make any change because it's a Reader failue.
Also duplicate Client on Cs357x Cachex 3 user, but it will be deleted by Client max idle.
When the issue occurs
When doing Cachex 3 with Cs357x Reader.
How the issue is reproducable
By using Cachex 3 with Cs357x Reader.
I can't provide a log file! But commenting this lines:
if(cl->reader->tcp_rto && (cl->reader->last_s - cl->reader->last_g > cl->reader->tcp_rto)) check if client reached timeout, if so disconnect client
{
network_tcp_connection_close(cl->reader, "rto");
return 0;
}
in module-camd35.c solves the issue. No RTO's! On Cs357x Cachex 3 Client side also no disconnect through Client max idle! Since I commented out the lines and Compiled Oscam no RTO's for about 5 hours.
Change History (38)
comment:1 by , 9 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:4 by , 9 years ago
Can't you read? http://www.streamboard.tv
Cs357x is UDP not connected: is send and forget protocol. Use cs378x for handshake protocol.
comment:5 by , 9 years ago
I know that! But when disconnecting: RTO appears on Cs357x Cachex 3 Reader Status is Unknown for 30 Secounds and not pushing Cache!
comment:7 by , 9 years ago
- There is no option in Webif for reconnecttimeout in Cs357x Reader.
- Even if I put it in oscam.server manually, Webif overwrites it when saving again(no changes).
- Webif sets keepalive = 1 in UDP Reader :D.
It is buggy! Please realize!
comment:8 by , 9 years ago
I can reproduce the issue!
Newest Oscam (self compiled) on x86_64-linux-gnu.
comment:10 by , 9 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
comment:11 by , 9 years ago
Write this line BY HAND in your reader:
reconnecttimeout = 180
There is no option in web-interface.....
http://www.streamboard.tv/wiki/OSCam/de/Config/oscam.server#reconnecttimeout
comment:12 by , 9 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
comment:13 by , 9 years ago
Even if I put it in oscam.server BY HAND, Webif overwrites it when saving again(no changes).
Webif sets keepalive = 1 in UDP Reader :D.
comment:15 by , 9 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
comment:16 by , 9 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
comment:17 by , 9 years ago
Webif sets keepalive = 1 in UDP Reader. Even there is no option in webif!
comment:18 by , 9 years ago
Even if I put it in oscam.server BY HAND, Webif overwrites it when saving again(no changes).
Webif sets keepalive = 1 in UDP Reader :D.
True.
Webif sets keepalive = 1 in UDP Reader. Even there is no option in webif!
Also true.
comment:19 by , 9 years ago
Why you put "keepalive" there, you have to add "reconnecttimeout"!!! WTF?
In UDP it gives no "keepalive" only "reconnecttimeout"! "keepalive" is for TCP!
And again, this is NOT a forum!
comment:21 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Please stop the stuff. UDP is not a handshake-protocol.
comment:22 by , 9 years ago
OMFG is it so hard to test?! Add a new cs357x Reader with cachex 3 and webif sets keepalive 1 in READER!!! ALONE!!! NOT ME!!! WTF?!?!?!
Look:
[reader]
label = Reader-2
protocol = cs357x
device = 127.0.0.1,54321
user = thot1414
password = thot1414
keepalive = 1
cacheex = 3
group = 2
That was done by WEBIF alone!
comment:23 by , 9 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:24 by , 9 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
"keepalive" is not used by UDP. btw: this is not a support-forum!
comment:25 by , 9 years ago
And why is it set by WEBIF even there is no option and reconnecttimeout which must!!!! be in webif is not there?!?!?!?!? Yes you are right its a bug forum! and I report A BUG!!!!!!!!!!!!!!!!!
comment:26 by , 9 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
comment:27 by , 9 years ago
I know that "keepalive" is not used by UDP! But why is Webif setting it? And reconnecttimeout which must be in WEBIF is not?! Even if i put reconnecttimeout = 180 manually/by hand/by editor and save! and after I go to webif in the reader and click on save ( Nothing changed in config) reconnecttimeout = 180 will be erased and keepalive = 1 is set. Try IT!!!!!!
comment:29 by , 9 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
comment:30 by , 9 years ago
Is it so hard to open a thread in forum?
I have tested this and it's working for me. Webif is not creating any entry "keepalive" as you told. So i think the problem is 40cm in front of our monitor. :-)
comment:33 by , 9 years ago
Well then Iam not a "normal" user...I'am using cache ex and I found a bug...
comment:34 by , 9 years ago
we all come down now a little bit...
anyone else with cacheex binaries can reproduce this?
and as said before - this is a ticket system, so please stop the discussion here and switch to the forum. there you will also find other people that use cacheex and you can discuss with them your config and the behaviour you found.
comment:35 by , 9 years ago
There should be no problem anymore.
theparasol, someone who acually thinks a little bit solved the issue!
Thank you very much theparasol!!!!
comment:37 by , 9 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
try this in your reader (oscam.server)
reconnecttimeout = 180
But this is no support forum. Please use the real forum and open a thread with your configs.