When Noobaa process starts with the required configuration (like Endpoints etc), it was observed in the noobaa log the "Error while pinging endpoint host :localhost, port 6443 Error" at the start of the process even before the Noobaa become Active. This way when the logs are looked by Customers or by Support / Dev team, there are chances of misleading , even though it is appropriate and acceptable at that point in time. Hence request is, can we not do the check until the noobaa process is started appropriately say a minute after start (given there could be many ENDPOINT_FORKS, once they are all started listening on the port 6443 for example) ..

noobaa.log

Apr 22 00:18:20 node-gui0 node[698936]: [noobaa-cli/698936]   [LOG] CONSOLE:: init_rand_seed: seeding with 32 bytes
Apr 22 00:18:20 node-gui0 node[698936]: [noobaa-cli/698936]   [LOG] CONSOLE:: Error while pinging endpoint host :localhost, port 6443 Error: Noobaa endpoi
nt is not running, all the retries failed    at func (/usr/local/noobaa-core/src/manage_nsfs/health.js:191:31)    at process.processTicksAndRejections (node:i
nternal/process/task_queues:105:5)    at async Object.retry (/usr/local/noobaa-core/src/util/promise.js:184:25)    at async NSFSHealth.get_endpoint_response (
/usr/local/noobaa-core/src/manage_nsfs/health.js:185:13)    at async NSFSHealth.nc_nsfs_health (/usr/local/noobaa-core/src/manage_nsfs/health.js:127:30)    at
 async Object.get_health_status (/usr/local/noobaa-core/src/manage_nsfs/health.js:669:35)    at async Object.manage_diagnose_operations (/usr/local/noobaa-cor
e/src/manage_nsfs/diagnose.js:24:13)    at async main (/usr/local/noobaa-core/src/cmd/manage_nsfs.js:84:13)
Apr 22 00:18:20 node-gui0 node[698936]: [noobaa-cli/698936]    [L0] core.sdk.config_fs:: config_fs.compare_host_and_config_dir_version: ver_comparison 0 running_code_config_dir_version 1.0.0 system_config_dir_version 1.0.0
Apr 22 00:18:20 node-gui0 node[698936]: [noobaa-cli/698936]    [L0] core.sdk.config_fs:: config_fs.compare_host_and_config_dir_version: ver_comparison 0 running_code_config_dir_version 1.0.0 system_config_dir_version 1.0.0
Apr 22 00:18:20 node-gui0 node[698878]: 2025-04-22 00:18:20.975553 [PID-698878/TID-698878] FS::GPFS gpfs_ganesha_noobaa_arg=args.noobaa_version=0 args.noobaa_delay=1000 args.noobaa_flags=0
Apr 22 00:18:20 node-gui0 node[698878]: [nsfs/698878]    [L0] core.upgrade.upgrade_utils:: the versions of the new_version and the current_version match. no need to upgrade
Apr 22 00:18:21 node-gui0 node[698878]: [nsfs/698878]    [L0] core.endpoint.endpoint:: endpoint: replacing old umask:  22 with new umask:  0
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]  [WARN] CONSOLE:: WORKER started { id: 1, pid: 698999 }
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]  [WARN] CONSOLE:: WORKER started { id: 2, pid: 699000 }
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]    [L0] core.util.fork_utils:: Starting metrics server 7004
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]    [L0] core.util.http_utils:: Starting METRICS server on HTTP port 7004
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]    [L0] core.util.http_utils:: Started METRICS HTTP server successfully
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]   [LOG] CONSOLE:: init_rand_seed: seeding with 32 bytes
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]    [L0] core.util.ssl_utils:: SSL certificate not found in dir /ibm/fvt_ces_root/ces/s3-config/certificates/ for service METRICS
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]  [WARN] core.util.ssl_utils:: Generating self-signed SSL certificate for METRICS
Apr 22 00:18:21 node-gui0 node[698992]: [noobaa-cli/698992]   [LOG] CONSOLE:: detect_fips_mode: found /proc/sys/crypto/fips_enabled with value 0
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]  [WARN] core.util.ssl_utils:: Certificate folder  /ibm/fvt_ces_root/ces/s3-config/certificates/  does not exist. New certificate won't be loaded.
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]    [L0] core.util.http_utils:: Starting METRICS server on HTTPS port 9443
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]    [L0] core.util.http_utils:: Started METRICS HTTPS server successfully
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]    [L0] core.util.fork_utils:: Started metrics server successfully
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]   [LOG] CONSOLE:: nsfs: listening on 'https://localhost:6443'
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]   [LOG] CONSOLE:: generate_entropy: entropy_avail 256

Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]   [LOG] CONSOLE:: generate_entropy: adding entropy: dd if=/dev/sda bs=1048576 count=32 skip=55711 | md5sum
Apr 22 00:18:21 node-gui0 [698878]: [nsfs/698878]   [LOG] CONSOLE:: init_rand_seed: done
Apr 22 00:18:21 node-gui0 node[698992]: [noobaa-cli/698992]   [LOG] CONSOLE:: read_rand_seed: reading 32 bytes from /dev/urandom ...
Apr 22 00:18:21 node-gui0 node[698992]: [noobaa-cli/698992]   [LOG] CONSOLE:: read_rand_seed: got 32 bytes from /dev/urandom, total 32 ...
Apr 22 00:18:21 node-gui0 node[698992]: [noobaa-cli/698992]   [LOG] CONSOLE:: read_rand_seed: closing fd ...
Apr 22 00:18:21 node-gui0 node[698992]: [noobaa-cli/698992]   [LOG] CONSOLE:: init_rand_seed: seeding with 32 bytes
Apr 22 00:18:21 node-gui0 node[698992]: [noobaa-cli/698992]   [LOG] CONSOLE:: Error while pinging endpoint host :localhost, port 6443 Error: Noobaa endpoint is not running, all the retries failed    at func (/usr/local/noobaa-core/src/manage_nsfs/health.js:191:31)    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)    at async Object.retry (/usr/local/noobaa-core/src/util/promise.js:184:25)    at async NSFSHealth.get_endpoint_response (/usr

/local/noobaa-core/src/manage_nsfs/health.js:185:13)    at async NSFSHealth.nc_nsfs_health (/usr/local/noobaa-core/src/manage_nsfs/health.js:127:30)    at async Object.get_health_status (/usr/local/noobaa-core/src/manage_nsfs/health.js:669:35)    at async Object.manage_diagnose_operations (/usr/local/noobaa-core/src/manage_nsfs/diagnose.js:24:13)    at async main (/usr/local/noobaa-core/src/cmd/manage_nsfs.js:84:13)
Apr 22 00:18:21 node-gui0 node[698992]: [noobaa-cli/698992]    [L0] core.sdk.config_fs:: config_fs.compare_host_and_config_dir_version: ver_comparison 0 running_code_config_dir_version 1.0.0 system_config_dir_version 1.0.0
Apr 22 00:18:21 node-gui0 node[698992]: [noobaa-cli/698992]    [L0] core.sdk.config_fs:: config_fs.compare_host_and_config_dir_version: ver_comparison 0 running_code_config_dir_version 1.0.0 system_config_dir_version 1.0.0
Apr 22 00:18:22 node-gui0 node[699072]: [noobaa-cli/699072]   [LOG] CONSOLE:: detect_fips_mode: found /proc/sys/crypto/fips_enabled with value 0
Apr 22 00:18:22 node-gui0 node[699072]: [noobaa-cli/699072]   [LOG] CONSOLE:: read_rand_seed: reading 32 bytes from /dev/urandom ...
Apr 22 00:18:22 node-gui0 node[699072]: [noobaa-cli/699072]   [LOG] CONSOLE:: read_rand_seed: got 32 bytes from /dev/urandom, total 32 ...
Apr 22 00:18:22 node-gui0 node[699072]: [noobaa-cli/699072]   [LOG] CONSOLE:: read_rand_seed: closing fd ...
Apr 22 00:18:22 node-gui0 node[699072]: [noobaa-cli/699072]   [LOG] CONSOLE:: init_rand_seed: seeding with 32 bytes
Apr 22 00:18:22 node-gui0 node[699072]: [noobaa-cli/699072]   [LOG] CONSOLE:: Error while pinging endpoint host :localhost, port 6443 Error: Noobaa endpoint is not running, all the retries failed    at func (/usr/local/noobaa-core/src/manage_nsfs/health.js:191:31)    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)    at async Object.retry (/usr/local/noobaa-core/src/util/promise.js:184:25)    at async NSFSHealth.get_endpoint_response (/usr/local/noobaa-core/src/manage_nsfs/health.js:185:13)    at async NSFSHealth.nc_nsfs_health (/usr/local/noobaa-core/src/manage_nsfs/health.js:127:30)    at async Object.get_health_status (/usr/local/noobaa-core/src/manage_nsfs/health.js:669:35)    at async Object.manage_diagnose_operations (/usr/local/noobaa-core/src/manage_nsfs/diagnose.js:24:13)    at async main (/usr/local/noobaa-core/src/cmd/manage_nsfs.js:84:13)
Apr 22 00:18:22 node-gui0 node[699072]: [noobaa-cli/699072]    [L0] core.sdk.config_fs:: config_fs.compare_host_and_config_dir_version: ver_comparison 0 running_code_config_dir_version 1.0.0 system_config_dir_version 1.0.0

Apr 22 00:18:23 node-gui0 node[698999]: [nsfs/698999]    [L0] core.upgrade.upgrade_utils:: the versions of the new_version and the current_version match. no need to upgrade
Apr 22 00:18:23 node-gui0 node[698999]: [nsfs/698999]    [L0] core.endpoint.endpoint:: endpoint: replacing old umask:  0 with new umask:  0
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]    [L0] core.endpoint.endpoint:: Configured Virtual Hosts: []
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]    [L0] core.endpoint.endpoint:: Configured Location Info: { region: '' }
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]  [WARN] core.endpoint.endpoint:: HTTP is not allowed for NC NSFS.
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]   [LOG] CONSOLE:: init_rand_seed: seeding with 32 bytes
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]    [L0] core.util.ssl_utils:: SSL certificate not found in dir /ibm/fvt_ces_root/ces/s3-config/certificates/ for service S3
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]  [WARN] core.util.ssl_utils:: Generating self-signed SSL certificate for S3
Apr 22 00:18:23 node-gui0 node[699000]: [nsfs/699000]    [L0] core.upgrade.upgrade_utils:: the versions of the new_version and the current_version match. no need to upgrade
Apr 22 00:18:23 node-gui0 node[699000]: [nsfs/699000]    [L0] core.endpoint.endpoint:: endpoint: replacing old umask:  0 with new umask:  0
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]    [L0] core.endpoint.endpoint:: Configured Virtual Hosts: []
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]    [L0] core.endpoint.endpoint:: Configured Location Info: { region: '' }
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]  [WARN] core.endpoint.endpoint:: HTTP is not allowed for NC NSFS.
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]   [LOG] CONSOLE:: init_rand_seed: seeding with 32 bytes
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]  [WARN] core.util.ssl_utils:: Generating self-signed SSL certificate for S3
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]  [WARN] core.util.ssl_utils:: Certificate folder  /ibm/fvt_ces_root/ces/s3-config/certificates/  does not exist. New certificate won't be loaded.
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]  [WARN] core.util.ssl_utils:: Certificate folder  /ibm/fvt_ces_root/ces/s3-config/certificates/  does not exist. New certificate won't be loaded.
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]    [L0] core.util.http_utils:: Starting S3 server on HTTPS port 6443
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]   [LOG] CONSOLE:: generate_entropy: entropy_avail 256
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]    [L0] core.util.http_utils:: Started S3 HTTPS server successfully
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]    [L0] core.util.background_scheduler:: Registering semaphore_monitor bg worker
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]   [LOG] core.util.background_scheduler:: run_background_worker: INIT semaphore_monitor
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]    [L0] core.util.http_utils:: Starting S3 server on HTTPS port 6443
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]    [L0] core.endpoint.endpoint:: Endpoint monitor started
Apr 22 00:18:23 node-gui0 [699000]: [nsfs/699000]   [LOG] CONSOLE:: nsfs: listening on 'https://localhost:6443'
Apr 22 00:18:23 node-gui0 [698999]: [nsfs/698999]    [L0] core.util.http_utils:: Started S3 HTTPS server successfully

am referring to the
"Apr 22 00:18:22 node-gui0 node[699072]: [noobaa-cli/699072]   [LOG] CONSOLE:: Error while pinging endpoint host :localhost, port 6443 Error: Noobaa endpoint"

Can these be avoided in the start and then print if still noobaa process is not started ?
Any thoughts

Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:

The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):

The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):

The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):

Does this issue impact your ability to continue to work with the product?

Is there any workaround available to the best of your knowledge?

Can this issue be reproduced? If so, please provide the hit rate

Can this issue be reproduced from the UI?

If this is a regression, please provide more details to justify this:

Steps to Reproduce:

1. Start the noobaa service

2.

3.

The exact date and time when the issue was observed, including timezone details:

Actual results:

Expected results:

Logs collected and log location:

Additional info: