Title: Unhandled TLSSocket error - internal Node error · Issue #44751 · nodejs/node · GitHub
Open Graph Title: Unhandled TLSSocket error - internal Node error · Issue #44751 · nodejs/node
X Title: Unhandled TLSSocket error - internal Node error · Issue #44751 · nodejs/node
Description: Version 18.9.0, 17.1.0 Platform Bodhi Linux (Ubuntu like) - VM guest on Windows 10 host Subsystem No response What steps will reproduce the bug? I am running my Node based peer-to-peer application in test automation mode that creates per...
Open Graph Description: Version 18.9.0, 17.1.0 Platform Bodhi Linux (Ubuntu like) - VM guest on Windows 10 host Subsystem No response What steps will reproduce the bug? I am running my Node based peer-to-peer application ...
X Description: Version 18.9.0, 17.1.0 Platform Bodhi Linux (Ubuntu like) - VM guest on Windows 10 host Subsystem No response What steps will reproduce the bug? I am running my Node based peer-to-peer application ...
Opengraph URL: https://github.com/nodejs/node/issues/44751
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Unhandled TLSSocket error - internal Node error","articleBody":"### Version\n\n18.9.0, 17.1.0\n\n### Platform\n\nBodhi Linux (Ubuntu like) - VM guest on Windows 10 host\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nI am running my Node based peer-to-peer application in test automation mode that creates persistent sockets as TLS websockets. One the first test automation run, initiated from the windows host machine, everything is fine. The application instance on the VMs continues to run so that I can frequently run test automation instances without ever touching the VMs. When I attempt to run test automation a second time only 1 of my 4 VM application instances fails.\r\n\r\nThis appears to be a node defect. The error message mentions an unhandled error event but I have extensive error handling on just about everything in my application, most especially my socket management. The stack trace also does not indicate any code from my application.\n\n### How often does it reproduce? Is there a required condition?\n\n100% reproducible. I am running 4 virtual machines each with a nearly identical install. This problem only occurs on one of those 4 VMs.\n\n### What is the expected behavior?\n\nSocket not crashing.\n\n### What do you see instead?\n\n```\r\nnode:events:491\r\n throw er; // Unhandled 'error' event\r\n\r\nError: read ECONNRESET\r\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)\r\nEmitted 'error' event on TLSSocket instance at:\r\n at emitErrorNT (node:internal/streams/destroy:151:8)\r\n at emitErrorCloseNT (node:internal/streams/destroy:116:3)\r\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {\r\n errno: -104,\r\n code: 'ECONNRESET',\r\n syscall: 'read'\r\n}\r\n\r\nNode.js v18.9.0\r\n```\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/prettydiff","@type":"Person","name":"prettydiff"},"datePublished":"2022-09-22T22:53:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/44751/node/issues/44751"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:b287cb50-eebb-8f0a-f572-0caa98d5b253 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C7C0:A74F2:13DAE52:1A81B50:69699E15 |
| html-safe-nonce | 06ffbfe12f86d2b53b3c2b29c2dba8fecb6609919cb73467f5ae6aa385dbae38 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDN0MwOkE3NEYyOjEzREFFNTI6MUE4MUI1MDo2OTY5OUUxNSIsInZpc2l0b3JfaWQiOiIxNzAwNTgwNDE4NDQ1MjIxMzk3IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | b5a301a2884be153bf012e66dbc4d7dcfa8836b9934b2c6870f047075bc73395 |
| hovercard-subject-tag | issue:1383102602 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/44751/issue_layout |
| twitter:image | https://opengraph.githubassets.com/98436797a4f8478434206fc56f7482fb9f9c1ce991177a2bf15bc393cd7c6838/nodejs/node/issues/44751 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/98436797a4f8478434206fc56f7482fb9f9c1ce991177a2bf15bc393cd7c6838/nodejs/node/issues/44751 |
| og:image:alt | Version 18.9.0, 17.1.0 Platform Bodhi Linux (Ubuntu like) - VM guest on Windows 10 host Subsystem No response What steps will reproduce the bug? I am running my Node based peer-to-peer application ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | prettydiff |
| hostname | github.com |
| expected-hostname | github.com |
| None | 24c4c97a2d520cb286b35e1a4c22d7a4df3c26a2fa28dd7cdf0e65db327b4de7 |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 124667f43168afb6c9c03b7c02eb5b1d2e1be3d9 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width