Portal 4.1 deployment error

Document ID : KB000008981
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

Can not start Portal Service.

portal-enterprise_1 in  "unealthy".

The following error happens frequently. 

  

portal14229.l7tech.com start-portal[1616]: portal-enterprise_1   | YYYY-MM-DD hh:mm:ss.xxx  INFO 1 --- [           main] liquibase                                : Waiting for changelog lock....

portal14229.l7tech.com start-portal[1616]: monitor | INFO     Performing container health checks

portal14229.l7tech.com start-portal[1616]: apim_1                | Mon DD, YYYY hh:mm:ss AM com.l7tech.server.management.db.CALiquibaseLogger info

portal14229.l7tech.com start-portal[1616]: apim_1                | INFO: Successfully acquired change log lock

portal14229.l7tech.com start-portal[1616]: monitor | WARNING  Container /run_portal-enterprise_1 failing streak: 3 (exceeds threshold)

Cause:

The root cause is related to locked - portal required- entities.We found two databases where DATABASECHANGELOG tables values must be flushed. 

Resolution:

mysql> update DATABASECHANGELOGLOCK set LOCKED=0,LOCKGRANTED=NULL,LOCKEDBY=NULL where ID = 1; 

 

Process must be applied to rbac and portal databases (first we flushed only the portal database databasechangeloglock table, which is not sufficient). 

We validate the fact that the issue is fixed by restarting several times the portal.