Centova Technologies Forum
Centova Cast v2 => Technical discussion => Topic started by: nEoStreams on July 20, 2009, 08:19:29 am
-
I am having troubles getting this feature to work correctly. I have 3 servers in the cluster and 1 primary all set up according to: http://www.centova.com/pages/faqs/display/enabling_api_clustering_64
When the primary server reaches the limit it stops provisioning new streams through the api and says that the server has reached it's limit. Even though there are many open spots available.
-
On the primary server, what is your "Provisioning server for API clustering" setting set to?
-
It's set to the server with the fewest accounts. Rock has 5 streams, pear (the primary) has 9 streams
nEoStreams
-
Can you confirm that you've followed the directions here (http://www.centova.com/pages/faqs/display/enabling_api_clustering_64) for enabling API clustering, and that you've added the appropriate line to config.php and set "Include in API cluster" to "yes" for the "Rock" stream?
-
I can confirm that i did follow the directions correctly and have double and triple checked all the steps have been done correctly. And all the servers in the cluster are set to yes and set up correctly.
nEoStreams
nEoStreams
-
You'd need to open a support ticket then, to have someone look at your servers. If you've precisely followed the directions it should just work.
-
The thing is that i can see all the other server's accounts on rock through pear's webpage and everything and i can even click on rock to go to it through pear. So it has to be working. The only part that isn't working is the api. It's very confusing.
I'd rather not have a staff member rifle through all my passwords and everything either.
nEoStreams
-
Is there a timeout or something in trying to contact the clustered servers, and if they don't respond within a certain amount of time they aren't used with the api?
nEoStreams
-
The thing is that i can see all the other server's accounts on rock through pear's webpage and everything and i can even click on rock to go to it through pear. So it has to be working.
If you see the remote host in your primary server's account list that means the remote server has been set up properly under "Remote servers", but that doesn't imply that API clustering is set up properly. Remote servers will show up regardless of whether ENABLE_API_CLUSTERING is defined in config.php or "Provisioning server for API clustering" is set correctly, etc.
I'd rather not have a staff member rifle through all my passwords and everything either.
Understandable, but all I can tell you is that it does work for other folks, including myself, so if it's not working for you it's either 1) a misconfiguration on your part or 2) a bug in CC triggered by something being different about your servers versus every other client using this feature. For obvious reasons we can't diagnose either case without access to your server.
Is there a timeout or something in trying to contact the clustered servers
No. There is of course a timeout, but if it timed out that'd be treated as a provisioning error -- it wouldn't just pick another host.
-
Is there any debug option or anything other than a generic error of:
SystemControl::provision (): This installation of Centova Cast has reached its licensed limit of 10 account(s); please upgrade your license if you require additional accounts
...
like maybe something saying why?
nEoStreams
-
PS. If I set Provisioning server for API clustering to 'rock' then it'll send the stream to rock...so there's a problem with the "the server with the fewest accounts option"
nEoStreams
-
Okay, so after manually setting it to rock and buying a new stream through the API, it went to rock perfectly fine.
I then changed the "Provisioning server for API clustering" setting on pear (the primary) back to "the server with the fewest accounts"
Again, it went to rock. I then changed "Include in API cluster" for rock on pear in remote servers to "no", and I get this error:
Error contacting server ID 5: Unsupported protocol:
Now please tell me how this is my issue and/or how to fix it
nEoStreams
-
Is there any debug option or anything other than a generic error of:
like maybe something saying why?
No, I think that error is pretty clear on its own. I don't mean to be facetious, but I have to genuinely ask what part of the message "This installation of Centova Cast has reached its licensed limit of 10 accounts" you're not clear about?
Error contacting server ID 5: Unsupported protocol:
That means that you've provided a bad URL to Centova Cast in whatever software you're using to provision accounts. The URL needs to be formatted as http://url-to-centovacast.com/uri/.
-
Why does it work in the one situation but not the other when only the choice of how to provision the stream is changed the issue here.....i didn't change the uri or anything, all that was changed is how to provision the god damned stream!
nEoStreams
-
Is there any debug option or anything other than a generic error of:
like maybe something saying why?
No, I think that error is pretty clear on its own. I don't mean to be facetious, but I have to genuinely ask what part of the message "This installation of Centova Cast has reached its licensed limit of 10 accounts" you're not clear about?
-- do you simply not understand that the server giving that error is the API Cluster Master, so instead of giving this silly error, it should be provisioning accoutns to one of the other servers that has more lisence slots...
- i would ask that you contact me directly with your name and email and your supervisors email address or phone number, as i'd like to file a complaint agnest you, since you appearently don't know how to read, and 2, you feel the need to insult customers.
now, please find someone that knows what they are talking about, have them look over this thread and post a reply that will actually be useful, or i will take my business elseware.
Thank you.
-
do you simply not understand that the server giving that error is the API Cluster Master, so instead of giving this silly error, it should be provisioning accoutns to one of the other servers that has more lisence slots...
No, I fully understand what you're saying, but my earlier message sums this up as best I can. Here's that excerpt again:
It does work for other folks, including myself, so if it's not working for you it's either 1) a misconfiguration on your part or 2) a bug in CC triggered by something being different about your servers versus every other client using this feature. For obvious reasons we can't diagnose either case without access to your server.
I'm not trying to give you the runaround here, but as I have already asked you to provide access to your server AND asked you to open a helpdesk ticket in this thread, and you have refused both, I'm afraid I'm kind of running out of options here on how to help you. This issue doesn't affect anyone else, so without taking a look at your server our hands are largely tied.
i would ask that you contact me directly with your name and email and your supervisors email address or phone number
Given that you're asking for my supervisor's information I assume you don't realize who I am... if anyone is interested in customers going home satisfied, it's me, but I'm afraid it's difficult to help when the only client experiencing a problem won't permit you to see it happen.
i'd like to file a complaint agnest you, since you appearently don't know how to read, and 2, you feel the need to insult customers.
I'm not sure where you've gotten the idea that I'm insulting you, although I apologize if it came across that way. The only thing I could even remotely interpret that way was my comment about the licensing error, but I did specifically say that I was not being facetious and genuinely can't see how that error message could be any clearer.
Your license limit is 10 accounts. You've created 10 accounts. Thus, you are at your license limit. It truly is as simple as that. If API clustering were working on your server, it would indeed use the other server first, but it's not working, hence the error message.
now, please find someone that knows what they are talking about, have them look over this thread and post a reply that will actually be useful, or i will take my business elseware.
For obvious reasons there isn't anyone who knows more about this issue than I do, so I'll lock this thread now as it seems clear that it's not going anywhere but downhill from this point. You are still most welcome to open a ticket with the helpdesk if you require further assistance.