Question

82
Views
AbikashKumarS Member since 2014 14 posts
Cognizant
Posted: 1 month ago
Last activity: 1 month 1 week ago

Could not get CDK from systemKeyManagementCache and not able to login to pega

We are running Pega 8.4 which was upgraded a month from 8.2.1. The system was running fine until we restarted it today. After restart no operator was able to login. In the logs it was throwing error.

2020-08-14 19:03:08,111 INFO  [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [     default task-34] [  STANDARD] [                    ] [CommonLogin:01.01.01] (dataencryption.DataKeyProvider) ERROR 172.31.10.40|10.85.0.43 kumam - Could not get CDK from systemKeyManagementCache 2020-08-14 19:03:08,111 INFO  [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [     default task-34] [  STANDARD] [                    ] [CommonLogin:01.01.01] (dataencryption.DataKeyProvider) ERROR 172.31.10.40|10.85.0.43 kumam - System CDK is null 2020-08-14 19:03:08,127 INFO  [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [     default task-34] [  STANDARD] [                    ] [CommonLogin:01.01.01] (o.dataencryption.CryptoHandler) ERROR 172.31.10.40|10.85.0.43 kumam - Failed to initialize Cipher :  

We saw a similar issue and resolution in the communication post but it does not provide how to execute it.

https://community.pega.com/support/support-articles/login-screen-refres…

When we restore the system to a week before DB backup, it runs fine. But restoring any backup after it is not helping. Something happened within last week but it didn't appear until we restarted it.

Please help us on it, its urgent and is stopping completely the development.

Pega Platform 8.4 Case Management
Share this page LinkedIn