KB-2325 Services are unable to start due to file system permissions with the db_* logs

pauline.delacruz — Wed, 16 Oct 2024 14:21:54 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 10/16/2024 2:21:54 PM

Symptoms

Services are unable to start due to issues with the file system permissions for the log files.

The service_manager.log shows the following:

Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.appian.komodo.api.exceptions.SignalException: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Inside tomcat-stdOut.log, the following errors are observed:

YYYY-MM-DD HH:MM:SS,mmm [Appian Engine Work Controller: process-execution1 Source: main ID: 3] ERROR com.appiancorp.process.background.EngineWorkController - Cannot retrieve engine burdens: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Cause

The K engines are prevented from writing to the db_*.log files, thus preventing startup. The K engines create the db_*.log files as writable, so the <APPIAN_HOME>/logs folder should have write permissions.

Action

Update the permissions of the log files to ensure the files are owned by the proper users and have write permissions.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: October 2024

Tags: engines, permissions, infrastructure, service manager

KB-2312 Services are unable to start due to file system permissions with the db_* logs

Ryan Good — Tue, 09 Jul 2024 20:32:51 GMT

Revision 8 posted to Appian Knowledge Base by Ryan Good on 7/9/2024 8:32:51 PM

Symptoms

Services are unable to start due to issues with the file system permissions for the log files.

The service_manager.log shows the following:

Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.appian.komodo.api.exceptions.SignalException: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Inside tomcat-stdOut.log, the following errors are observed:

YYYY-MM-DD HH:MM:SS,mmm [Appian Engine Work Controller: process-execution1 Source: main ID: 3] ERROR com.appiancorp.process.background.EngineWorkController - Cannot retrieve engine burdens: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Cause

Action

Update the permissions of the log files to ensure the files are owned by the proper users and have write permissions.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: July 2024

Tags: engines, permissions, infrastructure, service manager

[DRAFT SP-9812] KB-XXXX Services are unable to start due to file system permissions with the db_* logs

Ryan Good — Wed, 12 Jun 2024 21:52:18 GMT

Revision 7 posted to Appian Knowledge Base by Ryan Good on 6/12/2024 9:52:18 PM

Symptoms

Services are unable to start due to issues with the file system permissions for the log files.

The service_manager.log shows the following:

Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.appian.komodo.api.exceptions.SignalException: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Inside tomcat-stdOut.log, the following errors are observed:

YYYY-MM-DD HH:MM:SS,mmm [Appian Engine Work Controller: process-execution1 Source: main ID: 3] ERROR com.appiancorp.process.background.EngineWorkController - Cannot retrieve engine burdens: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Cause

Action

Update the permissions of the log files to ensure the files are owned by the proper users and have write permissions.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Tags: engines, permissions, infrastructure, service manager

[DRAFT SP-9812] KB-XXXX Services are unable to start due to file system permissions with the db_* logs

Ryan Good — Wed, 12 Jun 2024 21:47:06 GMT

Revision 6 posted to Appian Knowledge Base by Ryan Good on 6/12/2024 9:47:06 PM

Symptoms

Services are unable to start due to issues with file system permissions for the logs.

service_manager.log shows the following:

Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.appian.komodo.api.exceptions.SignalException: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Inside tomcat-stdOut.log, the following errors are observed:

YYYY-MM-DD HH:MM:SS,mmm [Appian Engine Work Controller: process-execution1 Source: main ID: 3] ERROR com.appiancorp.process.background.EngineWorkController - Cannot retrieve engine burdens: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Cause

The K engines are having trouble writing to the db_*.log files, thus preventing startup. K engines should be creating db_*.log files as writable, so the <APPIAN_HOME>/logs folder should have write permissions.

Action

Update the permissions of the log files to ensure the files are owned by the proper users and have write permissions.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Tags: engines, permissions, infrastructure, service manager

[DRAFT SP-9812] KB-XXXX Services are unable to start due to file system permissions with the db_* logs

pauline.delacruz — Wed, 05 Jun 2024 19:57:57 GMT

Revision 5 posted to Appian Knowledge Base by pauline.delacruz on 6/5/2024 7:57:57 PM

Symptoms

Services are unable to start due to issues with file system permissions with the logs.

service_manager.log shows the following:

Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.appian.komodo.api.exceptions.SignalException: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Inside tomcat-stdOut.log, the following errors are observed:

YYYY-MM-DD HH:MM:SS,mmm [Appian Engine Work Controller: process-execution1 Source: main ID: 3] ERROR com.appiancorp.process.background.EngineWorkController - Cannot retrieve engine burdens: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Cause

Action

Update the permissions of the log files to ensure the files are owned by the proper users and have write permissions.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Tags: engines, permissions, infrastructure, service manager

[DRAFT SP-9812] KB-XXXX Services are unable to start due to file system permissions with the db_* logs

pauline.delacruz — Wed, 05 Jun 2024 19:57:40 GMT

Revision 4 posted to Appian Knowledge Base by pauline.delacruz on 6/5/2024 7:57:40 PM

Symptoms

Services are unable to start due to issues with file system permissions with the logs.

service_manager.log shows the following:

Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.appian.komodo.api.exceptions.SignalException: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Inside the tomcat-stdOut.log, the following errors are observed.

YYYY-MM-DD HH:MM:SS,mmm [Appian Engine Work Controller: process-execution1 Source: main ID: 3] ERROR com.appiancorp.process.background.EngineWorkController - Cannot retrieve engine burdens: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Cause

Action

Update the permissions of the log files to ensure the files are owned by the proper users and have write permissions.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Tags: engines, permissions, infrastructure, service manager

[DRAFT SP-9812] KB-XXXX Services are unable to start due to file system permissions with the db_* logs

pauline.delacruz — Wed, 05 Jun 2024 19:57:23 GMT

Revision 3 posted to Appian Knowledge Base by pauline.delacruz on 6/5/2024 7:57:23 PM

Symptoms

Services are unable to start due to file system permissions with the logs.

service_manager.log shows the following:

Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.appian.komodo.api.exceptions.SignalException: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Inside the tomcat-stdOut.log, the following errors are observed.

YYYY-MM-DD HH:MM:SS,mmm [Appian Engine Work Controller: process-execution1 Source: main ID: 3] ERROR com.appiancorp.process.background.EngineWorkController - Cannot retrieve engine burdens: <APPIAN_HOME>/logs/db_*.log: Bad file descriptor

Cause

Action

Update the permissions of the log files to ensure the files are owned by the proper users and have write permissions.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Tags: engines, permissions, infrastructure, service manager

[DRAFT SP-9812] Services are unable to start due to file system permissions with the db_* logs

pauline.delacruz — Thu, 04 Apr 2024 17:08:25 GMT

Revision 2 posted to Appian Knowledge Base by pauline.delacruz on 4/4/2024 5:08:25 PM

Symptoms

Services are unable to start due to file system permissions with the logs.

Cause

The k engines are having trouble writing to the db_* files, thus preventing startup.

Action

Update the permissions of the log files to ensure the files are owned by the proper users and have write permissions.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: April 2024

[DRAFT SP-9812] Services are unable to start due to file system permissions with the db_* logs

pauline.delacruz — Wed, 03 Apr 2024 21:40:29 GMT

Revision 1 posted to Appian Knowledge Base by pauline.delacruz on 4/3/2024 9:40:29 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: April 2024