Help Center/ CodeArts Deploy/ FAQs/ Custom Application Actions/ Starting or Stopping Node.js/ Node.js Fails to Be Started or Stopped on a Linux Host
Updated on 2025-01-14 GMT+08:00
View PDF
Share

Node.js Fails to Be Started or Stopped on a Linux Host

Symptom 1

The command for starting the Start/Stop Node.js action fails, and the error message Cannot start forever is displayed.

Cause Analysis

The startup file is not found in the service path.

Solution

Enter the correct service path.

Symptom 2

The command for stopping the Start/Stop Node.js action fails.

Cause Analysis

The service has been stopped or the service path is incorrect.

Solution

Cancel the operation of stopping the service, or enter the correct service path.

Symptom 3

On a Linux host, the command for starting the Start/Stop Node.js action fails.

Cause Analysis

Node.js has been started, but the deployment status is STOPPED.

Figure 1 Deployment status

Solution

View the service startup log to check whether the service can be started properly. If the service can be started properly, deploy the startup command again.

Symptom 4

The error message Node service not installed, service start failed! is displayed.

Cause Analysis

The Node.js service has not been installed yet.

Solution

Install the Node.js service before you deploy this action.

Symptom 5

The Start/Stop Node.js action does not respond for a long time and then fails, with the error message Install forever failure! displayed.

Cause Analysis

The host cannot connect to the platform.

Solution

Ensure that the host can connect to the external network and the DNS is correctly configured.