Closed riasvdv closed 1 year ago
In our exception tracker, we're regularly getting the following exception: SSL_connect failed: (null) (RELAY_ERR_IO; cache.c:551)
SSL_connect failed: (null) (RELAY_ERR_IO; cache.c:551)
Is there a way to see exactly how or why it failed?
Relay Support => enabled Relay Version => 0.6.8 Available cache => 160 Available serializers => php, json, igbinary, msgpack Available compression => lzf, zstd, lz4 Binary UUID => 85974504-c02b-45d5-b507-650c8539b8a8 Git SHA => 5b490b90dc22ec28cf8f930286221ee196bbfd49 Allocator => relay Build OS => Ubuntu 16.04.7 LTS Architecture => x86_64 OpenSSL version => OpenSSL 1.1.1p 21 Jun 2022 License state => unknown License memory cap => 0 License request id => relay.enabled => false relay.environment => development relay.key => relay.maxmemory => 0 relay.maxmemory_pct => 95 relay.eviction_policy => noeviction relay.eviction_sample_keys => 128 relay.initial_readers => 128 relay.invalidation_poll_usec => 5 relay.pconnect_default => 1 relay.max_endpoint_dbs => 32 relay.loglevel => none relay.logfile =>
Seems like this was happening on servers that weren't on the latest version yet, I'll re-open if it happens again after updating them all
Description
In our exception tracker, we're regularly getting the following exception:
SSL_connect failed: (null) (RELAY_ERR_IO; cache.c:551)
Is there a way to see exactly how or why it failed?
Relay diagnostics