Repository navigation
AssertionError at TLSWrap.onhandshakestart (_tls_wrap.js:66:3) #22240
Description
Activity
IIRC I have observed that once on
10.4.1back then, which prompted me to upgrade to10.6.0@alexlamsl Would you be able to please provide a minimal Node.js application to reproduce the problem
- addedtlsIssues and PRs related to the tls subsystem.Issues and PRs related to the tls subsystem.
on Aug 10, 2018 @maclover7 crashing only 4 times over ~2 months makes investigations rather difficult.
If/when I have a reliable test case to illustrate this issue, you'll be the first to know.
FWIW this is the line that aborts
node.exe:
Line 66 in a657984
assert(now >= lastHandshakeTime); Same problem. Node v10.5.0
Reacted by MallikarjunaSame here, node v10.5.0
Aug 14 13:09:07: assert.js:269
Aug 14 13:09:07: throw err;
Aug 14 13:09:07: ^
Aug 14 13:09:07: AssertionError [ERR_ASSERTION]: false == true
Aug 14 13:09:07: at TLSWrap.onhandshakestart (_tls_wrap.js:66:3)I'm getting exactly the same 5 lines of error. It seems to occur after my ssl cert is renewed and the https server is auto-closed then recreated with the new cert+key. @alexlamsl maybe simulating a certificate change will trigger the error? If it's complex for you to try, I could try it out.
@adabru go right ahead — in my case the certificate always static.
Ok, I couldn't reproduce it with changing the certificate.
Potentially related to issue #22149 / PR #22214.
I also ran into this issue, and subtracting the date from when the process started to when I got the first assertion error was almost exactly 2^31 milliseconds. And from tracing back through the code that leads to this assertion failure, it depends on the same
GetNow()that was fixed in that PR.Reacted by Xaekai, nj and MallikarjunaReacted by Mallikarjuna@calzoneman thanks for the heads up - will test on
10.9.0for a while & report back.In my case it also were 2^31 milliseconds.
Same error here with node 10.6.0
same error here with node 10.0.0
Same error with Node 10 on a Raspberry Pi running Docker (node:latest)
Can't find any step to reproduce
@Trott yes, the problem does not occur in node >= 10.9.0
Great! I'll close this. Thanks.
A simple HTTPS server will occasionally die with the following trace:
The only relevant detail I can think of is the system clock is configured to synchronise with ntp.pool.org