How to check if the node is running successfully.

[newPepole123]

Is the following log normal?

node-app | 2025-04-01 03:20:26 - node.secret - INFO - RSA keys not found. Generating new keys...
node-app | 2025-04-01 03:20:26 - node.secret - INFO - RSA keys not found. Generating new keys...
node-app | 2025-04-01 03:20:26 - node.secret - INFO - RSA keys generated and saved to files.
node-app | 2025-04-01 03:20:26 - node.secret - INFO - AES secret not found. Generating new AES secret...
node-app | 2025-04-01 03:20:26 - node.secret - INFO - AES secret generated and saved to .env.
node-app | 2025-04-01 03:20:26 - node.secret - INFO - RSA keys already exist. Loading keys...
node-app | 2025-04-01 03:20:26 - node.secret - INFO - RSA keys loaded from files.
node-app | 2025-04-01 03:20:26 - node.secret - INFO - AES secret already exists in .env.
node-app | 2025-04-01 03:20:26 - node.user - INFO - Getting public key from /app/xyz.pem
node-app | 2025-04-01 03:20:26 - main - INFO - Skipping registration of node with hub
node-app | 2025-04-01 03:20:26 - main - INFO - Starting HTTP server on port 7001...
node-app | 2025-04-01 03:20:26 - node.secret - INFO - RSA keys generated and saved to files.
node-app | 2025-04-01 03:20:27 - node.secret - INFO - AES secret already exists in .env.
node-app | 2025-04-01 03:20:27 - node.secret - INFO - RSA keys already exist. Loading keys...
node-rabbitmq | 2025-04-01 03:20:27.481215+00:00 [info] <0.954.0> accepting AMQP connection 172.18.0.6:32986 -> 172.18.0.3:5672
node-app | 2025-04-01 03:20:27 - node.secret - INFO - RSA keys loaded from files.
node-app | 2025-04-01 03:20:27 - node.secret - INFO - AES secret already exists in .env.
node-app | 2025-04-01 03:20:27 - node.user - INFO - Getting public key from /app/xyz.pem
node-app | 2025-04-01 03:20:27 - main - INFO - Skipping registration of node with hub
node-app | 2025-04-01 03:20:27 - main - INFO - Starting WebSocket server on port 7002...
node-rabbitmq | 2025-04-01 03:20:27.745884+00:00 [info] <0.954.0> connection 172.18.0.6:32986 -> 172.18.0.3:5672: user 'username' authenticated and granted access to vhost '/'
node-app | [2025-04-01 03:20:27,748: INFO/MainProcess] Connected to amqp://username:**@rabbitmq:5672//
node-rabbitmq | 2025-04-01 03:20:27.754428+00:00 [info] <0.963.0> accepting AMQP connection 172.18.0.6:32992 -> 172.18.0.3:5672
node-rabbitmq | 2025-04-01 03:20:27.788386+00:00 [info] <0.963.0> connection 172.18.0.6:32992 -> 172.18.0.3:5672: user 'username' authenticated and granted access to vhost '/'
node-app | [2025-04-01 03:20:27,796: INFO/MainProcess] mingle: searching for neighbors
node-rabbitmq | 2025-04-01 03:20:27.816132+00:00 [warning] <0.970.0> Deprecated features: transient_nonexcl_queues: Feature transient_nonexcl_queues is deprecated.
node-rabbitmq | 2025-04-01 03:20:27.816132+00:00 [warning] <0.970.0> By default, this feature can still be used for now.
node-rabbitmq | 2025-04-01 03:20:27.816132+00:00 [warning] <0.970.0> Its use will not be permitted by default in a future minor RabbitMQ version and the feature will be removed from a future major RabbitMQ version; actual versions to be determined.
node-rabbitmq | 2025-04-01 03:20:27.816132+00:00 [warning] <0.970.0> To continue using this feature when it is not permitted by default, set the following parameter in your configuration:
node-rabbitmq | 2025-04-01 03:20:27.816132+00:00 [warning] <0.970.0> "deprecated_features.permit.transient_nonexcl_queues = true"
node-rabbitmq | 2025-04-01 03:20:27.816132+00:00 [warning] <0.970.0> To test RabbitMQ as if the feature was removed, set this in your configuration:
node-rabbitmq | 2025-04-01 03:20:27.816132+00:00 [warning] <0.970.0> "deprecated_features.permit.transient_nonexcl_queues = false"
node-rabbitmq | 2025-04-01 03:20:27.896508+00:00 [info] <0.981.0> accepting AMQP connection 172.18.0.6:32996 -> 172.18.0.3:5672
node-rabbitmq | 2025-04-01 03:20:27.902542+00:00 [info] <0.981.0> connection 172.18.0.6:32996 -> 172.18.0.3:5672: user 'username' authenticated and granted access to vhost '/'。

[sashankthapa]

het @newPepole123 , just visit the /health endpoint from your browser or terminal
curl http://localhost:7001/health
you should see: {"status":"ok!!!","communication_protocol":"http"}