What should I do if I get an error when starting node?

was the solution to the error when starting node: 1. Open the command window; 2. Run the "bin/initOSGIcfg.sh" command; 3. Rerun the "startNode.sh" command.

The operating environment of this tutorial: linux7.3 system, node18.4.0 version, Dell G3 computer.

What should I do if I get an error when starting node?

Under Linux, was started startnode.sh and reported an error, was started startNode and reported an error

Error:

************* End Display Current Environment *************
[2/13/12 5:10:03:143 EST] 00000000 ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[2/13/12 5:10:03:195 EST] 00000000 AdminTool A ADMU0128I: Starting tool with the AppSrv01 profile
[2/13/12 5:10:03:196 EST] 00000000 AdminTool A ADMU3100I: Reading configuration for server: nodeagent
[2/13/12 5:10:03:324 EST] 00000000 AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
[2/13/12 5:10:04:909 EST] 00000000 AdminTool A ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in zOS) and other log files under /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent should contain failure information.

Solution:

Just run bin/initOSGIcfg.sh and then run startNode.sh

Before, I followed the online method to synchronize the node. I tried many methods without success. This trick taught by a colleague is quite effective. Remember Next

If the same problem occurs in startManager.sh, it is estimated that it can be solved by this method

Recommended study: "nodejs video tutorial"

The above is the detailed content of What should I do if I get an error when starting node?. For more information, please follow other related articles on the PHP Chinese website!