AW: hilfe - plötzlich rejected group bzw. no matching reader
hi mogelhieb,
es läuft ja alles gut, bis zu dem Zeitpunkt, wenn sich der Client (warum auch immer) disconnected und wieder neu verbindet. In einem anderen Board sagte man mir, dass es nicht viel unterschied macht zwischen Stable und Unstable. Egal, jedenfalls schau mal her - habe jetzt die 1.00 5574 am laufen:
oscam(filtered): [LOG643]2012/01/10 11:30:23 41E12950 c nea (0D00&0000C0/10CE/84:84EB): found (2392 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG671]2012/01/10 11:30:32 41E12950 c nea (0D00&0000C0/10CE/84
561): found (682 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG712]2012/01/10 11:30:42 41E12950 c nea (0D00&0000C0/10CE/84:E43F): found (1398 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG753]2012/01/10 11:30:53 41E12950 c nea (0D00&0000C0/10CE/84:8BCE): found (2278 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG803]2012/01/10 11:31:06 41E12950 c nea (0D00&0000C0/10CE/84:3F3D): rejected reader peer (5270 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG852]2012/01/10 11:31:20 41E12950 c nea (0D00&0000C0/10CE/84:1804): timeout (5506 ms) by proxy38 (of 31 avail 32) - ATV
oscam(filtered): [LOG860]2012/01/10 11:31:21 41E12950 c nea (0D00&0000C0/10CE/84:6D95): rejected group (0 ms) (of 0 avail 32) - ATV (no matching reader)
oscam(filtered): [LOG897]2012/01/10 11:31:31 41E12950 c nea (0D00&0000C0/10CE/84:7298): rejected group (0 ms) (of 0 avail 32) - ATV (no matching reader)
oscam(filtered): [LOG949]2012/01/10 11:31:43 41E12950 c nea (0D00&0000C0/10CE/84:66C5): found (1627 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG995]2012/01/10 11:31:52 41E12950 c nea (0D00&0000C0/10CE/84:5FBD): found (1138 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG036]2012/01/10 11:32:03 41E12950 c nea (0D00&0000C0/10CE/84:8D13): found (2186 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG086]2012/01/10 11:32:14 41E12950 c nea (0D00&0000C0/10CE/84:548C): found (2784 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG118]2012/01/10 11:32:23 41E12950 c nea (0D00&0000C0/10CE/84:2B04): found (1673 ms) by proxy54 (of 25 avail 32) - ATV
oscam(filtered): [LOG169]2012/01/10 11:32:33 41E12950 c nea (0D00&0000C0/10CE/84:BE0E): found (2293 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG205]2012/01/10 11:32:43 41E12950 c nea (0D00&0000C0/10CE/84:4E18): found (1603 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG261]2012/01/10 11:32:57 41E12950 c nea (0D00&0000C0/10CE/84:F7B8): timeout (5494 ms) by proxy37 (of 3 avail 32) - ATV
oscam(filtered): [LOG293]2012/01/10 11:33:05 41E12950 c nea (0D00&0000C0/10CE/84:B084): rejected reader peer (50 ms) by proxy38 (of 1 avail 32) - ATV
oscam(filtered): [LOG330]2012/01/10 11:33:14 41E12950 c nea (0D00&0000C0/10CE/84:B7A4): rejected group (0 ms) (of 0 avail 32) - ATV (no matching reader)
oscam(filtered): [LOG383]2012/01/10 11:33:28 41E12950 c nea (0D00&0000C0/10CE/84:5E5D): timeout (5504 ms) by proxy34 (of 9 avail 32) - ATV
oscam(filtered): [LOG437]2012/01/10 11:33:41 41E12950 c nea (0D00&0000C0/10CE/84:7173): rejected group (0 ms) (of 0 avail 32) - ATV (no matching reader)
oscam(filtered): [LOG485]2012/01/10 11:33:51 41E12950 c nea (0D00&0000C0/10CE/84:E6C8): rejected group (0 ms) (of 0 avail 32) - ATV (no matching reader)
oscam(filtered): [LOG526]2012/01/10 11:34:02 41E12950 c nea (0D00&0000C0/10CE/84:E40B): found (1297 ms) by proxy54 (of 2 avail 32) - ATV
oscam(filtered): [LOG568]2012/01/10 11:34:12 41E12950 c nea (0D00&0000C0/10CE/84:38DB): found (659 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG614]2012/01/10 11:34:23 41E12950 c nea (0D00&0000C0/10CE/84:306C): found (2389 ms) by proxy54 (of 1 avail 32) - ATV
oscam(filtered): [LOG655]2012/01/10 11:34:33 41E12950 c nea (0D00&0000C0/10CE/84:CEA7): found (2277 ms) by proxy54 (of 23 avail 32) - ATV
da gibts das selbe Problem - nur gibts keine disconnects mehr und der Sender kommt irgendwann mal wieder. Für mich sieht das so aus, als ob nach einem Timeout der Sender auf no matching reader gesetzt wird und dann plötzlich doch wieder vom Loadbalancer gefunden wird?
Kann das sein?
Danke, lg burn