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 2024-08-06 GMT+08:00
View PDF
Share

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

Symptom 1

The deployment of the command for starting Node.js fails during the deployment of the action Start/Stop Node.js, 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 deployment of the command for stopping Node.js fails during the deployment of the action Start/Stop Node.js.

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 deployment of the command for starting Node.js fails during the deployment of the action Start/Stop Node.js.

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 is not installed on the host.

Solution

Install Node.js before action deployment.

Symptom 5

The deployment of the action Start/Stop Node.js 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.