Opened 11 years ago

Closed 11 years ago

#2432 closed defect (invalid)

Clients connection closed loop

Reported by: anonsat Owned by:
Priority: critical Component: ! Please select...
Severity: high Keywords: loop
Cc: Sensitive: no

Description

Revision

6453

Issue Description

Looping clients disconnect notice filling the log files till the process dies. The client using cccam. This problem never occur with other protocols.

When the issue occurs

randomly when clients disconnect

How the issue is reproducable

randomly

2012/03/03 19:40:50 B69ED888 c cccam(s) cs1: connection closed by client.
2012/03/03 19:40:50 B69EFCB0 c cccam(s) cs1: connection closed by client.
2012/03/03 19:40:50 B69F14E0 c cccam(s) cs2: connection closed by client.
2012/03/03 19:40:50 B6929F48 c cccam(s) cs2: connection closed by client.
2012/03/03 19:40:50 B69ED888 c cccam(s) cs1: connection closed by client.
2012/03/03 19:40:50 B69EFCB0 c cccam(s) cs1: connection closed by client.
2012/03/03 19:40:50 B69F14E0 c cccam(s) cs2: connection closed by client.
2012/03/03 19:40:50 B6929F48 c cccam(s) cs2: connection closed by client.
2012/03/03 19:40:50 B69ED888 c cccam(s) cs1: connection closed by client.
2012/03/03 19:40:50 B69EFCB0 c cccam(s) cs1: connection closed by client.
2012/03/03 19:40:50 B69F14E0 c cccam(s) cs2: connection closed by client.
2012/03/03 19:40:50 B6929F48 c cccam(s) cs2: connection closed by client.
2012/03/03 19:40:50 B69ED888 c cccam(s) cs1: connection closed by client.
2012/03/03 19:40:50 B69EFCB0 c cccam(s) cs1: connection closed by client.
2012/03/03 19:40:50 B69F14E0 c cccam(s) cs2: connection closed by client.
2012/03/03 19:40:50 B6929F48 c cccam(s) cs2: connection closed by client.

Change History (1)

comment:1 by Deas, 11 years ago

Resolution: invalid
Status: newclosed

please discuss this in the forum as it only can be a config issue...

Note: See TracTickets for help on using tickets.