Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: ExodusSS on September 29, 2011, 07:45:41 AM
-
Hi All,
Wondering if anyone else has come across opening IRD, which appears to crash Config Server for no apparent reason (possible memory leak?)
(WINTEL)
IRD: 7.6.200.05
URS: 7.6.200.04
Config Server: 7.6.000.56
Also tried with:
IRD: 8.0.100.12
- same result - crashes Config Server... :(
Has anyone else come across this, as a combination - and maybe know what the "fix" is? ;D
Thanks!
ESS
-
On which OS?
-
It's all WINTEL cav...
-
Hello,
We have been able to reproduce that issue by enabling/disabling about 30 statsitical days when IRD was starting. In that case, Config server is crashing about 50% of the time.
We are nearly sure that the crash of Config server occurs in the production environment when it is busy with configuration changes and IRD is starting.
Regards,
Erik
-
Hi Erik,
Just to let everyone know that I raised this question on your behalf....
Would it be true that the Config Server is crashing as a result of IRD attempting to register with it, when the Config Server is actually busy broadcasting updates to all Clients?
I know we discussed the option of using a Config Proxy - but that, apparently, does not allow updates and is simply a "rebroadcast" element of the Framework.
ESS
-
The point is that the only crashes of the config server we are facing occured when somebody was starting IRD. It tooks time to link both events (crash of config server and startibg of IRD) because every start of IRD is not crashing config server. The only way we found to reproduce the crash is by loading the config server with updates and starting IRD at the same time.
The proxy server is supposed to be a read-only instance of config server. We are able to start IRD, to look into the strategies but we are not able to compile the strategies (due to the read-only restriction). Having a dedicated config server proxy is thus not a solution.
Regards,
Erik
-
Hmmmm.....
Release Number 7.6.000.54: Configuration Server no longer terminates because of memory allocation problems. Previously, but in very rare cases, Configuration Server terminated unexpectedly because of memory allocation problems in internal storage.
?