-
Notifications
You must be signed in to change notification settings - Fork 862
Closed
Description
When I try to connect, I keep getting this in H2O' error.log:
received fatal signal 11
worker 6478 died unexpectedly with status:11, restarting
starting new worker 6519
/usr/bin/h2o[0x4aa6fe] neverbleed_init at ??:?
/lib64/libpthread.so.0(+0x10f50)[0x7f2272777f50] ?? ??:0
[INFO] raised RLIMIT_NOFILE to 8192
h2o server (pid:6519) is ready to serve requests
received fatal signal 11
/usr/bin/h2o[0x4aa6fe] neverbleed_init at ??:?
/lib64/libpthread.so.0(+0x10f50)[0x7f513f56af50] ?? ??:0
fetch-ocsp-response (using LibreSSL 2.5.1)
sending OCSP request to http://ocsp.int-x3.letsencrypt.org/
/foo/bar/something/something.crt: good
This Update: Feb 27 14:00:00 2017 GMT
Next Update: Mar 6 14:00:00 2017 GMT
verifying the response signature
verify OK (used: -VAfile /tmp/alcu6uraw1/issuer.crt)
new worker 6519 seems to have failed to start, exit status:11
starting new worker 6536
It work fine if I disable the TLS 1.3 flag (#ssl-version-max) on Chromium 56.
Also, as because I use ECDSA and don't have openssl >= 1.1.0, neverbleed is deactivated. Don't know why the log keep mentioning about neverbleed. This is somehow related?!
Metadata
Metadata
Assignees
Labels
No labels