Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Filippe on October 22, 2018, 06:09:57 PM

Title: ORS Cluster is not configured
Post by: Filippe on October 22, 2018, 06:09:57 PM

Hi

Im facing this problem with Orquestration Server 8.1.400.77
"This node is not operational - ORS Cluster is not configured"
I can not route an interaction because of ORS, it seems I could not configure the cluster well


I have already set up the transaction and cassandra .yalm file but it does not work!
https://imgur.com/a/Jxo2lAM
https://imgur.com/a/SoWqtOb
https://imgur.com/a/fAVIzJx

Anybody can help me to solve it?
thanks

Title: Re: ORS Cluster is not configured
Post by: hsujdik on October 22, 2018, 06:53:59 PM

On the cluster section, the Key should be the application name and the value some "site" name. Also, since your transaction name is not ORS, it should be in the Command Line parameters of the Start Info tab of Orchestration Server. In your case, you should add '-cluster "ORS CLuster"' (avoid using spaces.....)

Title: Re: ORS Cluster is not configured
Post by: Filippe on October 22, 2018, 07:00:37 PM

Hi!!!
Yes it is on command Line and i change the name of the cluster Without spaces "ORS_Cluster"
but it does not work!

Title: Re: ORS Cluster is not configured
Post by: hsujdik on October 22, 2018, 07:09:31 PM

Did you also enter a name (any name) on the value of the key "OR_Server" for the cluster section in that transaction/list?

Title: Re: ORS Cluster is not configured
Post by: Filippe on October 22, 2018, 07:30:30 PM

Yes, the value "LaCaja"
https://imgur.com/a/1waeJg1

also change the name in the .yalm in cassandra!

:(

Title: Re: ORS Cluster is not configured
Post by: Kubig on October 23, 2018, 07:21:22 AM

From provided screenshots it seems your Transaction list is configured with name "ORS_CLuster", but the start-up parameter is configured with value "-cluster ORS_Cluster" - due to the ORS looks for objects using case-sensitive, it will fails as there is no object "ORS_Cluster" at all. Repair/Fix the name of the transaction list and restart ORS, than it should work as expected.