Ken Ngo - or this error{"level":30,"levelname...
or this error
{"level":30,"level_name":"info","timestamp":"2025-05-28T00:39:23.003Z","process_id":299,"correlation_id":"","tenant_identifier":"","app":{"app_version":"1","service_name":"Analytics Console","service_area":"","service_type":"NestJS Server","team":"analytics","app_area":"","specific_app_area":"","port":3000},"image":{"environment":"development","port":3000,"base_image":"node:22-alpine","base_image_version":"22.15.0","framework":"NestJS","framework_version":"11.0.20","language":"typescript","language_version":"4.9"},"security":{"user":"","user_id":"","user_masq":"","user_masq_id":""},"message":"TableService.create: started to import 15 tables"}
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at async TableService.create (/app/src/thoughtspot/services/table.service.ts:48:24)
at async TableManager.createTenantTables (/app/src/services/table.manager.ts:70:22)
at async TenantOnboardService.onboard (/app/src/services/tenant-onboard.service.ts:51:5)
at async OnboardTenantCommand.execute (/app/src/commands/onboard-tenant.command.ts:50:22) {
[cause]: SocketError: other side closed
at TLSSocket.<anonymous> (node:internal/deps/undici/undici:6294:28)
at TLSSocket.emit (node:events:530:35)
at TLSSocket.emit (node:domain:489:12)
at endReadableNT (node:internal/streams/readable:1698:12)
at processTicksAndRejections (node:internal/process/task_queues:90:21) {
code: 'UND_ERR_SOCKET',
socket: {
localAddress: '172.18.0.2',
localPort: 38540,
remoteAddress: '52.65.185.6',
remotePort: 443,
remoteFamily: 'IPv4',
timeout: undefined,
bytesWritten: 69492,
bytesRead: 20510
}
}
}
7 Replies
Can you try to import just a single one table? Do you get the same error? 15 tables might be causing a timeout.
tried with one table, same error
{"level":30,"level_name":"info","timestamp":"2025-05-28T01:45:11.488Z","process_id":326,"correlation_id":"","tenant_identifier":"","app":{"app_version":"1","service_name":"Analytics Console","service_area":"","service_type":"NestJS Server","team":"analytics","app_area":"","specific_app_area":"","port":3000},"image":{"environment":"development","port":3000,"base_image":"node:22-alpine","base_image_version":"22.15.0","framework":"NestJS","framework_version":"11.0.20","language":"typescript","language_version":"4.9"},"security":{"user":"","user_id":"","user_masq":"","user_masq_id":""},"message":"TableService.create: started to import 1 tables"}
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at async TableService.create (/app/src/thoughtspot/services/table.service.ts:48:24)
at async TableManager.createTenantTables (/app/src/services/table.manager.ts:70:22)
at async TenantOnboardService.onboard (/app/src/services/tenant-onboard.service.ts:51:5)
at async OnboardTenantCommand.execute (/app/src/commands/onboard-tenant.command.ts:50:22) {
[cause]: SocketError: other side closed
at TLSSocket.<anonymous> (node:internal/deps/undici/undici:6294:28)
at TLSSocket.emit (node:events:530:35)
at TLSSocket.emit (node:domain:489:12)
at endReadableNT (node:internal/streams/readable:1698:12)
at processTicksAndRejections (node:internal/process/task_queues:90:21) {
code: 'UND_ERR_SOCKET',
socket: {
localAddress: '172.18.0.2',
localPort: 46026,
remoteAddress: '52.65.185.6',
remotePort: 443,
remoteFamily: 'IPv4',
timeout: undefined,
bytesWritten: 7262,
bytesRead: 34035
}
}
}
This looks more like it failed at a lower http level. A quick search on chat gpt gave this response
The error TypeError: fetch failed in Node.js typically occurs when the fetch() function (provided by the undici library in recent Node.js versions) encounters a low-level network failure before an HTTP response can even be received.
🔍 Possible Causes
Here are common reasons for this error:
Invalid URL
The URL passed to fetch() is malformed (e.g., missing protocol like https://).
Typo in domain or port number.
DNS Resolution Failure
The domain name could not be resolved (e.g., offline, wrong hostname, internal DNS issues).
Connection Refused
The server is not running or is rejecting connections on the specified port.
Timeouts or Network Interruptions
The network call took too long and was aborted.
Could happen due to VPN, proxy, firewall, or unstable internet.
TLS/SSL Errors
Certificate validation failure, especially if https:// is used and server's certificate is expired or invalid.
Proxy Misconfiguration
If you're behind a proxy and it’s not correctly set up in the environment, fetch will fail.
🧪 How to Debug
In your specific error:
swift
Copy
Edit
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at async TableService.create (/app/src/thoughtspot/services/table.service.ts:48:24)
You should:
Check the URL used in fetch() in table.service.ts line 48. Is it valid and reachable?
Log the URL and options passed to fetch() right before calling it.
Try curl or Postman on the same URL to rule out server issues.
Check for Environment Variables like HTTP_PROXY, HTTPS_PROXY, and NODE_TLS_REJECT_UNAUTHORIZED.
Wrap fetch() in a try-catch and log error.cause or error.message if present—undici sometimes attaches more context.
Thanks, but we would appreciate some insight investigations
The call is not even reaching TS it is failing before that it seems from the logs. I don't think there is anything to investigate on TS side.
"The call is not even reaching TS it is failing before that it seems from the logs. I don't think there is anything to investigate on TS side."
This is a false statement.
Can you create a ticket to investigate the same? Would be good to get on a call and check the issue.