Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: phil on May 11, 2010, 03:27:33 PM

Title: URS- Backup does not work after Fail-Over
Post by: phil on May 11, 2010, 03:27:33 PM

Hi there,

i produced a fail-over testing urs-backup functionality. but its not working at all. tasks are not distributed until URS primary is primary again.
HA-Setup seems to be ok. URS HA says:

look for hanged interactions: 11 at all now
there are 11 calls in progress now

should better be "there are 11 call on hold"

Can someone help please? Any clue?

Cheers Phil

Title: Re: URS- Backup does not work after Fail-Over
Post by: kubikle on May 11, 2010, 05:02:39 PM

What does new primary URS (previous backup) has in log after switchover (after "change run mode request ...." log message) about these interactions? May be entire log fragment is availabe?

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 09:09:59 AM

-- message removed due to mess--

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 09:22:12 AM

-- message removed due to mess --

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 09:27:09 AM

-- message removed due to mess --

Title: Re: URS- Backup does not work after Fail-Over
Post by: René on May 12, 2010, 09:28:27 AM

Hi Phil,

[quote]You can see my Login/Place being the selected Target but there s no distribution. Because...[/quote]
I see something different in the log...
[quote]10:15:05.939_M_I_081001ce303550ba [17:0e] VQ 026b1c00 (virtual queue "VQ_GTL", id=1), (3 Targets): SELECT MAX by statistic <StatTimeInReadyState>(random  )
    _M_I_081001ce303550ba [17:0e] VQ 026b1c00 Target "96102"(026b1b20): [b]not ready[/b] passed
    _M_I_081001ce303550ba [17:0e] VQ 026b1c00 Target "93333"(026b1510): [b]not ready[/b] passed
    _M_I_081001ce303550ba [17:0e] VQ 026b1c00 Target "99205"(026b2e90): [b]not ready[/b] passed
    _M_I_081001ce303550ba [17:0e] VQ 026b1c00 (virtual queue "VQ_GTL" id=1): Target for routing was NOT SELECTED (0 0 3 0 0)[/quote]

Information you see in User Data comes from previous route request as there are part of EventRouteRequest.

R.

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 10:09:55 AM

hi rene,

already deleted this, this log was from when i was actually "not Ready".

cheers tho

Title: Re: URS- Backup does not work after Fail-Over
Post by: René on May 12, 2010, 10:56:27 AM

Hi Phil,

OK. In that case please post the correct log :)

The one in your previous post shows EventRouteRequest but nothing else. As I wrote in my previous email - User Data you see in this log snippet comes from previous route attempt so forget about this.

R.

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 11:16:35 AM

In a flash>>>meep meep -- I have to tidy up this mess of log fragments... quite annoying, id rly appreciate upload functionality been reactivated.

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 12:13:18 PM

an enduring flash and some perceptions later...:

- indeed urs recognizes me as "not ready" (just thougth i actually was not ready, but i am and was)

what does this mean. id like to avoid posting 500 KB log snippets which part could be interesting?

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 12:13:57 PM

the original question is why does primary URS properly recognize my stauts and the backup does not

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 12:15:44 PM

...

Title: Re: URS- Backup does not work after Fail-Over
Post by: René on May 12, 2010, 12:44:13 PM

Phil,

URS retrieves info about agent's status from StatServer. Please check that backup URS is connected to the same StatServer as primary one.

R.

Title: Re: URS- Backup does not work after Fail-Over
Post by: phil on May 12, 2010, 01:01:44 PM

I checked the connection before. it was ok. Unfortunately i just checked the conenctions tab...  :-\
The Key in Annex-Tab>__ROUTER__>RoutingStatServer was populated with the name of the previous StatServer.  ::) After a naming convention rework some time ago, some names have been changed but not this entry. Arrgh. >:D Bad maintenance!! I rly enjoy finding others mistakes  ;D, could just have been a bit faster

ps: in support for the evildoer: it was the lab environment