Performance run fails to initialize

Help Hub
, ,
1

Hi All,

(@saialekhya.yerragunt - noticed you have replied to the same issue before)

Performance tests fail to initialize (started couple of months ago, after upgrade) - ”Failed to initialize performance testing system. Please try again” (logs below)

  • Windows 11, Currently on Postman 11.87.4 (used an older version, but automatically upgrades after restart)
  • I am able to download with curl (after explicitly including proxy) though: https://performance-test-artifacts.getpostman.com/windows/duckdb
  • When trying the link from browser, download window pops up, but I get “no internet connection“ icon in the ‘downloads widget’, after click on “save file” (Chrome)
  • Postman logs:
DuckDB: Checking installation in cache directory: C:\Users\..\AppData\Roaming\Postman\duckdb-cache\node_modules"]DuckDB: Checking for essential binary files in: C:\Users\…\AppData\Roaming\Postman\duckdb-cache\node_modules\@duckdb\node-bindings-win32-x64"]DuckDB: Missing essential file: C:\Users\…\AppData\Roaming\Postman\duckdb-cache\node_modules\@duckdb\node-bindings-win32-x64\duckdb.node"]DuckDB: Installation check result: NOT INSTALLED"][Main Process] DuckDB installation check: NOT FOUND"][Main Process] Initializing DuckDB…“]DuckDB: Loading for platform win32-x64”]DuckDB: Added C:\Users\…\AppData\Roaming\Postman\duckdb-cache\node_modules to module paths"]DuckDB: Loaded 0 system root CA certificates"]DuckDB: CA bundle: 0 certificates"]DuckDB: Failed to process @duckdb/node-bindings-win32-x64:“,{“name”:“Error”,“message”:“Timeout downloading https://performance-test-artifacts.getpostman.com/windows/duckdb",“stack”:"Error: Timeout downloading https://performance-test-artifacts.getpostman.com/windows/duckdb\n    at ClientRequest. (C:\Users\…\AppData\Local\Postman\app-11.87.4\resources\app.asar\main.js:942:128345)\n    at Object.onceWrapper (node:events:632:28)\n    at ClientRequest.emit (node:events:518:28)\n    at ClientRequest.emit (node:domain:489:12)\n    at TLSSocket.emitRequestTimeout (node:_http_client:849:9)\n    at Object.onceWrapper (node:events:632:28)\n    at TLSSocket.emit (node:events:530:35)\n    at TLSSocket.emit (node:domain:489:12)\n    at Socket._onTimeout (node:net:595:8)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)”}]DuckDB: Failed to load DuckDB:”,{“name”:“Error”,“message”:“Timeout downloading https://performance-test-artifacts.getpostman.com/windows/duckdb",“stack”:"Error: Timeout downloading https://performance-test-artifacts.getpostman.com/windows/duckdb\n    at ClientRequest. (C:\Users\…\AppData\Local\Postman\app-11.87.4\resources\app.asar\main.js:942:128345)\n    at Object.onceWrapper (node:events:632:28)\n    at ClientRequest.emit (node:events:518:28)\n    at ClientRequest.emit (node:domain:489:12)\n    at TLSSocket.emitRequestTimeout (node:_http_client:849:9)\n    at Object.onceWrapper (node:events:632:28)\n    at TLSSocket.emit (node:events:530:35)\n    at TLSSocket.emit (node:domain:489:12)\n    at Socket._onTimeout (node:net:595:8)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)”}]Failed to load DuckDB:“,{“name”:“Error”,“message”:“Timeout downloading https://performance-test-artifacts.getpostman.com/windows/duckdb",“stack”:"Error: Timeout downloading https://performance-test-artifacts.getpostman.com/windows/duckdb\n    at ClientRequest. (C:\Users\…\AppData\Local\Postman\app-11.87.4\resources\app.asar\main.js:942:128345)\n    at Object.onceWrapper (node:events:632:28)\n    at ClientRequest.emit (node:events:518:28)\n    at ClientRequest.emit (node:domain:489:12)\n    at TLSSocket.emitRequestTimeout (node:_http_client:849:9)\n    at Object.onceWrapper (node:events:632:28)\n    at TLSSocket.emit (node:events:530:35)\n    at TLSSocket.emit (node:domain:489:12)\n    at Socket._onTimeout (node:net:595:8)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)”}][Main Process] DuckDB initialize error:”,“Timeout downloading https://performance-test-artifacts.getpostman.com/windows/duckdb",{“context”:{“api”:“Main”,“domain”:“PerformanceTestV2”},“userId”:"…”,“teamId”:“10082637”}][“NewRelicService~RecordCustomEvent: API request failed”,{“errno”:-4039,“code”:“ETIMEDOUT”,“syscall”:“connect”,“address”:“162.247.243.33”,“port”:443,“name”:“Error”,“message”:“connect ETIMEDOUT 162.247.243.33:443”,“stack”:“Error: connect ETIMEDOUT 162.247.243.33:443\n    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)”}]
1 Like
2

Is it possible to install manually the packages Postman is trying to download?

I am able to download “duckdb-signed-win32-x64.zip” from https://performance-test-artifacts.getpostman.com/windows/duckdb through curl.

Thanks

3

Hey @v-kon :waving_hand:

Have you been able to work through this troubleshooting guide on the Postman Docs?

4

Hi,

from my machine, I am able to download with curl, where I EXPLICITLY specify the proxy.

If I try curl, without proxy, the download fails (timeout), just like within Postman.

From the Postman logs:

DuckDB: Loaded 0 system root CA certificates”]DuckDB: CA bundle: 0 certificates”]DuckDB: Failed to process @duckdb/node-bindings-win32-x64:”,{“name”:“Error”,“message”:"Timeout downloading

.

Is that an indication that it is a (proxy?) cert issue?

5

@v-kon We are pushing the fix soon, its both proxy and certificate issue.
If you have any urgent deadlines, reach out via support we will unblock you.

1 Like
6

Thank you for the quick reply,

I could wait 8-10 business days perhaps ..

BTW, Is there a way to manually install that package (which I am able to download through curl)?

7

@v-kon We expect the fix for these initialization errors to be available by Friday. I will ping this thread with the release version once it is out. We’d like to hear if this unblocks your performance testing workflows

1 Like
8

hey @v-kon
Please use the latest version v11.88.3 or v12.1.3 on which fix is available.
Let us know if you are unblocked or not

9

Hi @saialekhya.yerragunt, I tried today, no luck( v12.2.0)

Postman is using the system proxy, which is a script located at 127.0.0.1:9000 , basically Zscaler.

I can see more detailed logs from Postman, stating “DuckDB: Using system proxy: http://127.0.0.1:9000"

Again, I am able to download with CURL by specifying an actual proxy server, and not my ZScaler local proxy.

I tried by adding certificates to Postman ( got Zscaler’s through Chrome), not sure what URL though; tried 127.0.0.1:9000, https://performance-test-artifacts.getpostman.com/windows/duckdb:443.

Again, I think would be beneficial to be able to specify custom proxy for the extension download.

Question - why is postman automatic version upgrade download working, not affected by this issue?

Most importantly - how can I install these extension manually?

10

@v-kon — Please contact us via Support for a deeper investigation.

We need to identify why the extension is failing while the app works, as both should respect the system proxy and trust store (including Zscaler certificates assuming you have them added to your system trust store).
In your ticket, please share the exact error message shown on UI, screenshots, and your postman logs so we can pinpoint whether the block is happening at the network or certificate level. If its some different issue we will try to unblock with manual steps.

11

I have had no issues with Postman running Performance Runs until January.
You introduced changes that caused this issue.

You indicated a “fix”, but did not fix the issue. Seems to me you just added logging.

I can download these packages through a corporate proxy, curl.

I use the same proxy, added to Postman, to test Internet facing APIs.

There should be a way for Postman to allow a custom proxy, when installing packages, and not use the system proxy, and forcing us to get, install proxy certificate (which is not a trivial matter, as it requires generating a bundle, related to the target url ? )

I am forced to write my own scripts now, for performance testing, something I could have done last week, but waited for a “fix“.

I am sorry, but I can’t waste more time with this.