Sreethi G (SreethiG)

SreethiG Member since 2017 16 posts
Posted: August 31, 2017
Last activity: September 20, 2017
Posted: 31 Aug 2017 20:34 EDT
Last activity: 20 Sep 2017 11:38 EDT

Pega Chat does not work in redis protected mode and different port other than 6379

Redis master listens to port 6379 and requirepass=***** is set
Redis slave listens to port 6380 and masterauth=***** is set. Redis slave is started with "--protected-mode no"

Master-Slave replication works fine. When integrating with Pega Chat with below entry in config.json,
1. It does not pass the password to redis master and we get authentication error
"Redis master ready check failed: Error: NOAUTH Authentication required"
2. It does not pick any port other than 6379
"Redis sub [Error: Redis connection to ec2-54-252-172-239:6379 failed = connect ECONNREFUSED]" - which is correct since nothing is listening on port 6379 and correct port is 6380

Below is our config.json entry

"redis" : {
"master" : {
"host": " "
"port": 6379
"password": "*****"
"slave" : {
"host": ""
"port": 6380

Note: We also face the below behaviour:
If I mention a redis.slave.port on which slave is not listening, chat tries to connect to the mentioned wrong port. If I pass the correct port number, then it always tries connecting to 6379. I guess Chat do pick the port mentioned in config.json, but there is some other inline script which resets redis port to 6379 by default.

Attached are more details

***Updated by moderator: Lochan to remove host details as it's proprietary information; edit topic categories; tag SR details***

Pega Customer Service Conversational Channels Support Case Created
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.