Loadbalancer

There are 8 replies in this Thread which was already clicked 3,085 times. The last Post () by sync.

    Hey,


    I had the lb set at 1, so it's on and uses the fastest reader first. For some reason I just couldn't watch a thing! Everything kept freezing.


    I've turned lb to 0 and it's been fine since, the only problem is it continues to use the one reader and none of my other peers.


    Is there a happy medium? :(


    Thanks,

    without loadbalancer set it will send the request to all of your peers and you will find that the fastest response will be the one that clears it - try setting it to 1 again and find out which peer it is selecting, and then if it is freezing, try disabling this peer. Might be that there are issues on their server.

    If I take a while to respond, you can see why.....


    :red:

    I actually tried that and it kept hopping between peers, using hop 2 constantly, and then freezing on random peers (not the same one) before just 'sticking'. It wouldn't start again unless I restarted OSCAM. :ah:

    You could try reducing the retry limit.
    I have loadbalancer set to 1 and I have no issues at all with it, which is why I think it is most likely to do with your peers, but with more tweaking you can help to get it to run more smoothly.

    If I take a while to respond, you can see why.....


    :red:

    Firstly thanks musogeek and everyone who helps.


    This is how my peers are set out:



    What would you change?

    That seems fine - what I was saying is you can control what you receive from your peers if it is causing a problem on your server - what you did for JSC - services = !jsc you can add other cards/services to your oscam.services and block these off from the peers in the same way where you are getting sketchy clearance from them. I would also suggest that when you have enough on your hop 1 and 2 that you set ccmaxhops to 1 instead of 2.

    If I take a while to respond, you can see why.....


    :red:

    if you are using webinterface for Oscam then you access it by clicking 'configuration' - 'loadbalancer' - and one of the boxes is retry limit. This defaults to 800ms - to change this value then add


    lb_retrylimit = ###


    to oscam.conf, or just put in a different value in webinterface.


    hashes being the value you want - try lower values than 800ms

    If I take a while to respond, you can see why.....


    :red:

    You have it in the reader, delete it from there and add it to oscam.conf and see what your results are



    [global]
    lb_mode = 2

Your resource for OSCam softcam

Find configs, downloads, tutorials, and support for setting up and optimizing this open-source card server with wide protocol compatibility. Master the versatile OSCam softcam. Access support, configs, tutorials, and downloads for open-source card sharing and multi-protocol server management.