I am now on build 7509 now.
Installed it this afternoon, no crashes at all till now, so seems to work stable.
I am now on build 7509 now.
Installed it this afternoon, no crashes at all till now, so seems to work stable.
Hmm.. Are you sure ? Check your CPU usage with top..
Mine is very high with the latest release.
I'm back to 7480 which seems stable for me..
I need to test where this breaks...
I've build also svn7480 with DEBUG=1! In the last 3 days I had few crashes, but in oscam.crash it's nothing special, only something like this:
and nothing more!!Code:Thu Sep 27 13:44:29 2012 OSCam cardserver v1.20-unstable_svn, build #7480 (i486-linux-gnu-ssl-libusb-debug) FATAL: Signal 11: Segmentation Fault. Logged StackTrace:
I did something wrong at build?
Strangely, when published first fix in 7474, there were crashes, but they were rare, 1-2 in one day. In recent days, significantly more frequent crashes. I tried almost all versions without changing the settings, but all are equally unstable for me. Today, even tested, highly stripped down version only cccam, camd35 and cacheex module, but the end result was the same again, crash within 3 hours.
Well..
Its getting better and better.. :(
Check this : http://www.streamboard.tv/oscam/ticket/2787
For all cache3 users, please read this:
http://www.satsupreme.com/showthread.php/230179-For-all-CACHE-EX-Mode-3-Users-(must-read!)?p=943877
Update on 7518; stays stable, no crashes.
Start: 28.09.12 - 03:00:43 | UpTime: 19:09:47
BUT... if I put the above described settings, I get duplicate login errors on all clients ! .. Will test a bit further with other builds..
I have build 7528 running since 4am this morning and so far no crashes, but still dup users. I have ticked drop dub users and it´s fine. Cache 3 is flowing good in and out. Guess the rest of the day will test how it runs.
Can not recommended build 7528 only my findings so far. I will revert back to tried and tested build 7190 if it falls over.
Napper
all users should have a restriction to their dyndns so your sure its them thats trying to connect and noone else .
hostname = share.dyndns.org
also to stop duplicate logins , you can restrict the user to use only the last ip they logged into with , in case they update there ip , they will log in and the old ip account will be auto logged out
uniq = 3
edit :- just upgrade from 7516 to 7536 , no double log in from users and still 100% cache hits .