Posts - 295
Likes - 482
Joined - January 1970
Forum Group: - Administrator Forum Group: - Global Moderator Forum Group: - Tester Multics 1 - Not Public r100
in new versions starting from rc44 there is implemented double cycle check
if someone has too much dcw rejected, as there is this system redundant with DCW CHECK and also AI, which is in real not only for NDS, but for all systems
than, if sometimes occurred timeout for example on caid 1810, means there was dcw rejected and it's too often, it may bad interpreting as bad dcw also some suspicious dcw, in touch with DCW CHECK and AI
than in this case is better to let it on implemented system AI and double cycle check and not use DCW CHECK
to do this, disable all DCW CHECK in default and on profiles:
CACHE DCWCHECK2: NO CACHE DCWCHECK3: NO
NDS_AI_OPTION ACTIVE: YES
DEFAULT DCW CHECK: NO
DCW CYCLE_CHECK: YES #for each profile
CCCAM DCW CHECK: NO
MGCAMD DCW CHECK: NO
CAMD35 DCW CHECK: NO
CS378X DCW CHECK: NO
if you want strictly system with redundancy, use DCW CHECKS to YES, but sometimes may reject also valid dcw and timeout occurred, it's very hard to set fast and immediately replacement of those rejected
There are many different races, religions and ideas and everyone is entitled to their own views, but this is the right momentum that moves humanity forward, beyond better destiny and freedom, so let others live their own dream, which makes up our better common world...
Posts - 295
Likes - 482
Joined - January 1970
Forum Group: - Administrator Forum Group: - Global Moderator Forum Group: - Tester Multics 1 - Not Public r100
There are many different races, religions and ideas and everyone is entitled to their own views, but this is the right momentum that moves humanity forward, beyond better destiny and freedom, so let others live their own dream, which makes up our better common world...
Posts - 295
Likes - 482
Joined - January 1970
Forum Group: - Administrator Forum Group: - Global Moderator Forum Group: - Tester Multics 1 - Not Public r100
I found that starting from rc44 there was added function to support also caches priority and one parameter for this is missing in config and readme.txt, it will be added on next release
this parameter is : LOADBALANCER PRIORITY: NO
when this parameter is set to YES, there is needed to set { priority=1 ; } for N line or other lines, otherwise is not working it from server sides
for this is also mandatory set parameter SERVER VALIDECMTIME: 0 , it must be zero 0 to working it with priority
as I saw it was not working for someone and there was solution to set validecmtime to value above zero, than there was probably this parameter of loadblancer priority seto to YES
in default , if it's not in config, it's seto to zero 0
There are many different races, religions and ideas and everyone is entitled to their own views, but this is the right momentum that moves humanity forward, beyond better destiny and freedom, so let others live their own dream, which makes up our better common world...