if shares to cards are showing it would seem they dont have cacheEX selected in their user settings for your connection .
although when i first started using cache EX it did used to show shares , so they could be using one of the very first version of oscam to have cache EX .
Not true...Originally Posted by mikie8
A cc-cam user just advertises its cards, also with cache-ex, especially for mode-1 support
In mode-3 you don't need this advertisement, so you can disable it by cccmaxhops = -1 like stated before.
thanks , i should have put
if shares to cards are showing it would seem they dont have cacheEX 3 selected in their user settings for your connection
I think you don't get my point.
There is no relation between the cache-ex settings and the advertisements of cards to or from other servers.
So, however you will setup cacheex=1/2/3/0, or whatever version you use, the result is just the same.
Advertisements of cards are a security risk though when sharing cache, because a remote peer can set cacheex=0 on the reader and act like a normal client. In other words, he can use your real cards without your permission by changing this setting. To prevent this, put cccmaxhops = -1 to disable advertising, and with that, eliminating the security risk.
--
Now on topic again
Besides PlatoonRTV, who does experience the camd35 multiple connection issue ?
Thx!
I have two oscam_7477 installed on one PC. First oscam is only used for reading cards, and normal exchanges without cacheex, this work stable. Second oscam used only cacheex, but it is not stable, crashed 2-3 in a day!?
According to information from oscam, one of my peers, making 30-50 errors. Could this peer causing a crash?
My settings are:
Code:nice = -1 clienttimeout = 3900 serialreadertimeout = 3200 waitforcards = 0 waitforcards_extra_delay = 350 dropdups = 1 saveinithistory = 1 disablelog = 1 disableuserfile = 1 clientmaxidle = 0 cachedelay = 25 cacheexwaittime = 75 max_cache_time = 7 max_cache_count = 7500 failbantime = 360 failbancount = 4 block_same_ip = 0 block_same_name = 0Code:[reader] label = xxxxx protocol = cccam device = xxxxx.zapto.org,20000 user = user password = pass reconnecttimeout = 2 cacheex = 3 cacheex_maxhop = 4 group = 13,14,15,16,17,18,19,20,21,22,23,25,26,27,28,29,30,31,33 dropbadcws = 1 cccversion = 2.3.0 cccmaxhops = 0 ccckeepalive = 1 cccreshare = 0 cccreconnect = 0 audisabled = 1Code:[account] user = user pwd = pass group = 22 uniq = 3 cacheex = 3 cacheex_maxhop = 4 cccmaxhops = -1 cccreshare = 0 keepalive = 1 numusers = 0 penalty = 0
thank you for being clear with your information .
im always willing to learn .
I allowed recording log file and saw that before oscam crash, there were a number of these messages:
Code:2012/09/22 13:19:11 88E6248 p dropping client data for user time 47s 2012/09/22 13:19:11 88E6248 p dropping client data for user time 47s 2012/09/22 13:19:11 0 --- Skipped 119 duplicated log lines --- 2012/09/22 13:19:11 88E6248 p dropping client data for user time 46s 2012/09/22 13:19:11 88E6248 p dropping client data for user time 46s 2012/09/22 13:19:11 0 --- Skipped 128 duplicated log lines --- 2012/09/22 13:19:11 88E6248 p dropping client data for user time 45s 2012/09/22 13:19:11 88E6248 p dropping client data for user time 45s 2012/09/22 13:19:11 0 --- Skipped 164 duplicated log lines --- 2012/09/22 13:19:11 88E6248 p dropping client data for user time 44s 2012/09/22 13:19:11 88E6248 p dropping client data for user time 44s 2012/09/22 13:19:11 0 --- Skipped 130 duplicated log lines --- 2012/09/22 13:19:11 88E6248 p dropping client data for user time 43s 2012/09/22 13:19:11 88E6248 p dropping client data for user time 43s
Can someone to offer a solution?
added:
Now examine carefully log and saw that these messages should have appeared, 25 minutes before a crash, so probably not the reason.
@galiano:
My oscam does crash also, once/twice in 24h. It's hard to say if this is directly related to cache-ex..
Remember Oscam 1.20 is still a beta release. Also, some segfaults are removed in 7478 / 7479. (and there will be more)
--
About the loglines:
2012/09/22 13:19:11 88E6248 p dropping client data for user time 43s
I have also seen these.. Had them in several build.
I think.. , but i'm not 100% for sure.., this is caused by slow networks, when oscam isn't able to deliver all its cache to a remote peer.
Do you have these on multiple peers ? I disabled / removed the peers that are causing these lines.. Now, i don't have them anymore.
--
About the ERR in CACHE-EX Tab:
Since i upgraded to the version that contains the ERR column, i had one peer generating errors.
This peer has upgraded now, and all errors are gone. Please ask this peer what version he runs..
thx!
@CapNCooK
Thanks for your response!
I tried 7480, after an hour and a half, also as 7477 crash. in log not see anything, just 15 minutes of inactivity before the crash. Consumption of CPU and memory are minimal.
Hmm OK.
Please do this:
- configure your oscam source with 'WITH_DEBUG' support
- make oscam with 'make DEBUG=1 OSCAM_BIN=oscam-debug'
- start oscam with 'oscam-debug -a -b -r0'
- the -a parameter will create a oscam.crash file, containing debug information for developers. Send this file to me after crash.
If no oscam.crash file was created after crashing, you miss some dependencies.
Let me know if this occurs, then we go to plan B.
Thx
Posting Permissions
Reply With Quote