KB-1042 "Failed to append transaction to DB (\"X.kdb: Bad file descriptor\")" thrown after attempting to start engines

Nick Vigilante — Tue, 14 Feb 2017 15:04:24 GMT

Current Revision posted to Appian Knowledge Base by Nick Vigilante on 2/14/2017 3:04:24 PM

Symptoms

After running start-suite.bat|sh, one or more engines won't start.

In the APP window (Windows) or in the gw-*.log file (Unix), the following lines are displayed:

No transactions for replay
  0 (100%) replayed in 03.739s
 Booted.
("XXXX.kdb"
 `write_to_disk_failure
 "Failed to append transaction to DB (\"XXXX.kdb: Bad file descriptor\")"

Cause

The user that ran the start-suite.bat|sh command does not have read and write permissions over one or more of the .kdb files for the engine(s) in question.

Action

To correct this issue, perform the following:

Either change permissions or ownership of the .kdb file(s) causing issues so that the user intended to start the Appian engines can read and write to all .kdb files for that particular installation.
Restart the Appian engines.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2015

Tags: administration, engines, scripts