Posts by cybermega

I totally agree with sync on that...the CSP MySQL User Manager is only really helpful if you had a lot of users being added and removed on a daily basis, and i think we all know the kind of setups that is most applicable to! - the easiest thing to do is simply edit the config file as sync has suggested :)

I copied this tutorial from a fellow forum member afc007 so all kudos to him for a fine bit of work - i copied it exactly as he instructed and my CSP clustered cache is fully working:

Continued..........

How to Setup Clustered Cache

Step 1, firstly you need to choose yourself a port different from what you csp is using,for the cache which must be forwarded in your router and instead of tcp define it as a udp port lets say for example "17500 "

Step 2, make sure you forward this port in UDP to your CSP Server's ip address,

Step 3, in your proxy xml file locate this :

Code:

<cache-handler class="com.bowman.cardserv.DefaultCache">
<cache-config>
<cw-max-age>14</cw-max-age>
<max-cache-wait>11</max-cache-wait>
</cache-config>
</cache-handler>

it is normally near the bottom of the xml file, do not worry if its not exactly the same, now you are going to delete all of that and replace it, I will show with what shortly.

Step 4, you need to locate where your csp is kept, for example mine is /usr/local/csp
there also should be a cache directory, you need to open that and make a file just called " cluster "

Step 5, open / edit the new file ( cluster ) you made, in there will go your dns and port that you forwarded earlier ... ie myserver.homelinux.net :17500
also if someone has already given you details to exchange cache that would go on the next line

so you would have a file that looks like:

Code:

myserver.homelinux.net :17500
friends.dyndns.addy :30001

save that file and if any other cache exchange lines are given to you they will go in there as well.

Step 6, you will need to chmod the new file ie

Code:

chmod 755 /usr/local/csp/cache/cluster

or whatever path your csp is in.

step 7, this will be the replacement part of the xml file that you have deleted as of step 3
now remember the udp port you have forwarded also your dns you put in the cluster file and also the path where the cluster file is.

Code:

<cache-handler class="com.bowman.cardserv.ClusteredCache">
<cache-config>
<cw-max-age>11</cw-max-age>
<max-cache-wait>150ms</max-cache-wait>
<local-host>myserver.homelinux.net </local-host>
<local-port>17500</local-port>
<tracker-url>file:///usr/local/csp/cache/cluster</tracker-url>
<tracker-update>1</tracker-update>
<sync-period>5</sync-period>
<hide-names>true</hide-names>
<debug>true</debug>
</cache-config>
</cache-handler>

save the xml " save changes "

Step 8, Restart your CSP Proxy

that's all

to check if it works , go to Status page and you should see
Cache-Handler: com.bowman.cardserv.ClusteredCache
click on it and it opens up. you should see something like the example below

Code:

avg-received-bytes/s: 113
avg-sent-bytes/s: 292
cache-peers: 3
cached-ecms: 73
instant-hits: 893
pending-ecms: 6
received-cached: 37926
received-discarded: 15322
received-pending: 30190
remote-hits: 533
sent-cached: 15895
sent-pending: 17336
timeouts: 443
tracker-failures: 0
wait-hits: 1225

so I understand then, when your use your local network IP address is works fine, but when you use a forwarding address such as dyndns it fails?

your tracker url looks incorrect....it should be: <tracker-url>file:/usr/local/csp/cache/cluster</tracker-url>

Intresting information Zebbros, though i cannot get my head around why 3 connections to the same local card will make any more difference than only having 1 connection? am i missing something completley obvious here!!:confuse:

you also need to make sure that when creating the cluster file in windows notepad that you save it as file type "all files" from the dropdown menu as saving it as a standard txt file will not work...this also got me for a while! - then when you have transferred the cluster file to your CSP server then edit it directly form within winscp to add the cache details.

also dont forget to save and refresh the directory when you make any changes to the cluster file, and if you want to make 100% sure then stop and restart your CSP server with the commands ./cardproxy.sh stop > ./cardproxy.sh start

also, have you correctly setup the portfoward to your cache file on your server setup, as this would be another reason the csp is unable to connect with it.

you need to login as root and change the /cache/ file permissions to 755 so that you can save any changes you make to it - i had the same problem and it was a file permission problem

did you create a new cluster file and CHMOD 755 it? at location /usr/local/csp/cache/ and did you put your own cache url at the top of the list? in the format xxxxxxxx.dyndns.us:1000000 - if you want to pm me your cache url i will add it to see it its operational and i will send mine by return for you to use as well if you want :)

as it was over 3 days i personally would not be bothered about such a small amount of failed ECMs as it is such a small amount i would not waste to much time on it, and it is probably down to short disconnects that you dont notice, but which are just enough to trigger a failed ecm.

If you want to exchange connectors just PM me, as having a csp connector will increase your server capacity massively...its like adding another sever to your setup with just one simple connection!

CM

HI Cyberhack,

over what period of time did you get the 11 ecm failures? - because it generally does not have any impact on your server or card...how many csp connectors do you have? as one of these could be playing up as well and generating ecm failures - by the sounds of it your server is wrking fine, it just maybe someone your connected to is not setup correctly.

I forgot to tell you earlier that you can enable cache debug mode by going to CSP>admin>ClusteredCache commands (near the bottom)>Toggle debug>click ok - if debug is of then clicking OK will switch it on, and it its on, clicking OK will switch it of :) you will now get a very detailed breakdown of your cache operation.

HI all,

im currently looking to create a VPS based server....i cannot find any clear opinions on what VPS providers are best for allowing to install your own software etc such as cccam and CSP etc - and i have read stories about providers closing VPS's that run these...so can anyone recommend a good VPS thats reliable and secure for my little hobby :)

I get that sometimes as well - dont forget that the cache url's you have been given will usually be a forwarder URL such as noip or dyndns etc - once received by the cache they are converted to the the proper IP address of cache sender...what you need to do is establish what cache peer has that IP address thats giving the errors and then, if you find it a problem, ask them nicely to remove your cache url form theirs :)

rikjaard-real,

if i follow your question right, the answer is it will only reduce (not stop completely) your personal web connection from being used if you host CSP on a VPS, and even then you still need to have your local card fed into the CSP so it still uses your home internet connection - hope this helps :)

when you click on Cache-Handler: com.bowman.cardserv.ClusteredCache in your CSP "status" page you should a very detailed breakdown of ecms received and sent to what peers IP address etc - its great to see whats going and coming from where :)

I also find my cache hit % does vary from time to time, and it depends if your cache peers have ecms for the profile you want at that particular time of day, as i find early morning to later afternoon a certain profile i use drops in the number of remote hits as there are clearly not that many people watching their TVs, but as the evening and night moves on, the cache hit rate increases very fast as there are more viewers, and therefore more ecms cached :)

HI zebbros,

tired PM'ing you this morning to exchange cache details but your mailbox is full....when you are able to accept mail let please PM me and i will send the cache details to you

CM