KB-1895 Execution engines fail to start with "pe.kr: file not found" message in the db_PX* log file

Jordan Horwat — Mon, 25 Mar 2019 14:47:23 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 3/25/2019 2:47:23 PM

Symptoms

Execution engine fails to start due to the following error printed in the service_manager.log file located in the <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

The following error is printed in db_PX*.log file located in the <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when the pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for the execution engines.

Action

Restore the pe.kr file from a backup or from another install on the exact Appian version.
Start the execution engines again as noted in the Start Script documentation.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure, service manager

KB-1895 Execution engines fail to start with "pe.kr: file not found" message in the db_PX* log file

Jordan Horwat — Mon, 25 Mar 2019 10:47:15 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 3/25/2019 10:47:15 AM

Symptoms

Execution engine fails to start due to the following error printed in the service_manager.log file located in the <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

The following error is printed in db_PX*.log file located in the <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when the pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for the execution engines.

Action

Restore the pe.kr file from a backup or from another install on the exact Appian version.
Start the execution engines again as noted in the Start Script documentation.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure

DRAFT KB-XXXX Execution engines fail to start with "pe.kr: file not found" message in the db_PX* log file

Anirudh Rathi — Mon, 25 Mar 2019 10:42:14 GMT

Revision 8 posted to Appian Knowledge Base by Anirudh Rathi on 3/25/2019 10:42:14 AM

Symptoms

Execution engine fails to start due to the following error printed in the service_manager.log file located in the <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

The following error is printed in db_PX*.log file located in the <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when the pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for the execution engines.

Action

Restore the pe.kr file from a backup or from another install on the exact version.
Start the execution engines again as noted in the Start Script documentation.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure

DRAFT KB-XXXX Execution engines fail to start with "pe.kr: file not found" message in the db_PX* log file

Jordan Horwat — Fri, 22 Mar 2019 17:50:13 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 3/22/2019 5:50:13 PM

Symptoms

Execution engine fails to start due to the following error printed in the service_manager.log file located in the <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

The following error is printed in db_PX*.log file located in the <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when the pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for the execution engines.

Action

Restore the pe.kr file from a backup and start the execution engines again as noted in the Start Script documentation.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure

DRAFT KB-XXXX Engines fail to start with "pe.kr: file not found" message in the db_PX* log file

Jordan Horwat — Fri, 22 Mar 2019 17:49:10 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 3/22/2019 5:49:10 PM

Symptoms

Execution engine fails to start due to the following error printed in the service_manager.log file located in the <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

The following error is printed in db_PX*.log file located in the <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when the pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for the execution engines.

Action

Restore the pe.kr file from a backup and start the execution engines again as noted in the Start Script documentation.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure

DRAFT KB-XXXX Engines fail to start with "pe.kr: file not found" message in the db_PX* log file

Jordan Horwat — Fri, 22 Mar 2019 17:48:50 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 3/22/2019 5:48:50 PM

Symptoms

Execution engine fails to start due to the following error printed in the service_manager.log file located in the <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

The following error is printed in db_px.log file located in the <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when the pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for the execution engines.

Action

Restore the pe.kr file from a backup and start the execution engines again as noted in the Start Script documentation.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure

DRAFT KB-XXXX Engines fail to start due to missing pe.kr file

Jordan Horwat — Fri, 22 Mar 2019 17:47:59 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 3/22/2019 5:47:59 PM

Symptoms

Execution engine fails to start due to the following error printed in the service_manager.log file located in the <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

The following error is printed in db_px.log file located in the <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when the pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for the execution engines.

Action

Restore the pe.kr file from a backup and start the execution engines again as noted in the Start Script documentation.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure

DRAFT KB-XXXX Engines fail to start due to missing pe.kr file

Anirudh Rathi — Fri, 22 Mar 2019 16:29:34 GMT

Revision 1 posted to Appian Knowledge Base by Anirudh Rathi on 3/22/2019 4:29:34 PM

Symptoms

Execution Engine fails to start due to the following error pasted in service_manager.log file located in <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

Following error is printed in db_px.log file located in <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for execution engine.

Action

Restore the pe.kr file from a backup and try starting execution engines again.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure

DRAFT KB-XXXX Engines fail to start due to missing pe.kr file

Anirudh Rathi — Fri, 22 Mar 2019 12:35:08 GMT

Revision 3 posted to Appian Knowledge Base by Anirudh Rathi on 3/22/2019 12:35:08 PM

Symptoms

Execution Engine fails to start due to the following error pasted in service_manager.log file located in <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

Following error is printed in db_px.log file located in <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for execution engines.

Action

Restore the pe.kr file from a backup and try starting execution engines again.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure

DRAFT KB-XXXX Engines fail to start due to missing pe.kr file

Anirudh Rathi — Fri, 22 Mar 2019 12:34:54 GMT

Revision 2 posted to Appian Knowledge Base by Anirudh Rathi on 3/22/2019 12:34:54 PM

Symptoms

Execution Engine fails to start due to the following error pasted in service_manager.log file located in <APPIAN_HOME>/logs directory:

ERROR com.appian.komodo.engine.EngineComponentService - execution01 failed to start with context RestartContext{mode=REPLICA, epoch=null, restart=true, attempt=3}
java.lang.RuntimeException: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type
...
Caused by: com.appian.komodo.engine.invoker.SignalReturnedException: Signal returned by engine: type

Following error is printed in db_px.log file located in <APPIAN_HOME>/logs directory:

[PX011] {pe1045.kdb ,0} () FATAL .a.db "pe.kr: file not found"

Cause

This issue is witnessed when pe.kr file located in <APPIAN_HOME>/server/process/exec is missing. This file is utilized to build KDB files for execution engines.

Action

Restore the pe.kr file from a backup and try starting execution engines again.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2019

Tags: engines, infrastructure