Opened 10 years ago
Closed 9 years ago
#3480 closed defect (expired)
Share List of Remote Server gets lost when Ccckeepalive Time passed away
Reported by: | Vortex | Owned by: | |
---|---|---|---|
Priority: | major | Component: | Protocol - CCCam |
Severity: | high | Keywords: | |
Cc: | Sensitive: | no |
Description
Revision
8972
Issue Description
The problem is, that all remote servers having ccckeepalive = 0 set, will mostly never more be included in the share.
When the issue occurs
The only situation when a server with its shares comes back into the share list is, when a new cccam client comes in, and the cccam update intervall falls inside the timeframe of the inactivity timeout...
It is okay, that the share list of a server will be deleted, if it is not reachable (network error/wrong password, or whatever), but not, if the operator don't want the network loaded with unnecessary connections, when no clients are asking for cards...
Also there is a setting reconnecttimeout, directy below inactivitytimeout.
This setting looks like a wonderful way to refresh the share list, even when inactivitytimeout and ccckeepalive is set.
for example
ccckeepalive = 0
inactivitytimeout = 30
updateinterval = 240
reconnecttimeout = 239
should refresh the share list nearly every 240s propperly, as the reader got a wake up by reconnecttimeout.
But reconnecttimeout does not work in any way here!
How the issue is reproducable
Create a reader (remote server) and set minimum config but:
ccckeepalive = 0
inactivitytimeout = 30
reconnecttimeout = 239
cccam: updateinterval = 240
the Loadbalancer is disabled by
forward_origin_card = 1
to prevent jumping of card request from server to server like mad...
logs unnecessary...