Question
AI4Process
GB
Last activity: 4 Jul 2017 6:47 EDT
ERROR - PegaRULES initialization failed
Hi,
We are getting below error while logging into the application after server restart. Pega version 6.3
Error 503: PegaRULES server not available.
error in logs: ERROR - PegaRULES initialization failed.
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed.
Also attached error log file.
Please let me know if there is a solution for this.
Thanks,
Veera
***Updated by moderator: Lochan to add Categories***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
AI4Process
GB
Hi Basavaraj,
We are able to find the issue where the pr_data_admin table in our non-working environment Env 2 has the BLOB column showing a value of NULL for all 307 records. Just by restoring the single table we are able to bring the servers up.
But do you have any idea why the BLOB column become null.
-Veera-
Pegasystems Inc.
IN
Hi Veerareddy,
The root cause of this problem might be defect/misconfiguration in the PRPC operating environment.and OS User running the application server does not have proper file permission to create/delete files in the file system. Can you check those and provide all the permission
AI4Process
GB
Hi Prashant,
Sorry for the late response! My team was trying some options to bring our environment back but unfortunately it is still an issue!
As you said "OS User running the application server does not have proper file permission to create/delete files in the file system" Can you help me to find the permissions of the os user on files please? Do we need to check the log files?
Thanks,
Veera
AI4Process
GB
Update..
We have also verified the OS user access and it has full control on temp directory as well.
Thanks,
Veera
Pegasystems Inc.
AU
Hi Veera,
As per the logs, it indicates that the blob data corruption and hence PRPC is not starting up when it reads the data from the p4_* tables;
Caused by:
java.lang.ArrayIndexOutOfBoundsException
at com.pega.pegarules.data.internal.access.CompressImpl.isCompressed(CompressImpl.java:239)
at com.pega.pegarules.data.internal.clipboard.StorageStreamCommonImpl.inflateStream(StorageStreamCommonImpl.java:624)
at com.pega.pegarules.data.internal.access.PageDatabaseMapperImpl.populatePageOrStringMapFromStreamColumn(PageDatabaseMapperImpl.java:2148)
As per our suggestions on the SR-B56197, since you have a DB back up taken 2 weeks back. Kindly restore the same.
Regards,
Basavaraj Kadakol
Accepted Solution
AI4Process
GB
Hi Basavaraj,
We are able to find the issue where the pr_data_admin table in our non-working environment Env 2 has the BLOB column showing a value of NULL for all 307 records. Just by restoring the single table we are able to bring the servers up.
But do you have any idea why the BLOB column become null.
-Veera-
Pegasystems Inc.
AU
Hi Veera,
Good to know that just restoring the table(rather than a whole db) worked.
Have shared the probable root cause for the blob corruption on the SR. Please refer to the SR note for further information.
Regards,
Basavaraj
AI4Process
GB
Hi Basavaraj,
Now our test application is up and running and no issues further.
I am wondering what caused the blob columns set to null in pr_data_admin table. Any reason/root cause behind this please?
Thanks,
Veera