Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: My Auto DJ on November 20, 2012, 01:40:24 pm

Title: Cluster host authentication failure for Local server: too many connections, try
Post by: My Auto DJ on November 20, 2012, 01:40:24 pm

This is on a new server I got last week, no active streams on it yet though
== it  was doing fine for several days. I created several streams and tested fully with 0 errors --  but I ran the update and there are problems , so I am sure this is related to the last update 11/20/2012

When I goto status page I get

Cluster host authentication failure for Local server: too many connections, try again later

STEVE  I have sent you FTP info to your inbox   

Title: Re: Cluster host authentication failure for Local server: too many connections, try
Post by: Headshaker on November 20, 2012, 02:02:27 pm

I have the same !

100% load on my server !

Quick help needed !

Title: Re: Cluster host authentication failure for Local server: too many connections, try
Post by: My Auto DJ on November 20, 2012, 02:06:46 pm

O I did not know about the high load -- STEVE I shut my server down for now, nobody was on it anyway... but so the login details I provided in your PM box will not work now

Title: Re: Cluster host authentication failure for Local server: too many connections, try
Post by: Headshaker on November 20, 2012, 02:31:22 pm

There is few RPC processes which are taking full CPU :/

You should do some kind of downgrade possibillity in case like this one.

Title: Re: Cluster host authentication failure for Local server: too many connections, try
Post by: Centova - Steve B. on November 20, 2012, 04:53:51 pm

Quote from: My Auto DJ on November 20, 2012, 01:40:24 pm

When I goto status page I get

Cluster host authentication failure for Local server: too many connections, try again later

Thanks!  A fixed version is up on the download server now.

Quote from: Headshaker on November 20, 2012, 02:31:22 pm

You should do some kind of downgrade possibillity in case like this one.

Not really practical.  If the upgrade involves any database or configuration file changes, it's not practical to undo those, and they'll probably cause an older version to fail if you roll back.

That's why this is called the 'unstable' branch, though. :)  Once 3.0.0 final is released, changes won't be introduced to the 'stable' branch until they're well-tested on 'unstable', so there should never be a need to roll back.