Re: [squid-users] Failed to shm_open

2017-03-01 Thread Amos Jeffries
On 2/03/2017 4:21 a.m., erdosain9 wrote: > no shared cipher Exactly what it says. There are no ciphers which both the client and the server are allowing to be used. One example of this is a client that only speaks SSLv2 and a server that speaks only TLS/1.3. You will have to dig a bit deeper to

Re: [squid-users] Failed to shm_open

2017-03-01 Thread Amos Jeffries
On 2/03/2017 4:06 a.m., erdosain9 wrote: > Hi. > Now squid stop... abnormaly. > > 2017/03/01 12:04:31 kid1| helperOpenServers: Starting 5/32 'ssl_crtd' > processes > FATAL: Ipc::Mem::Segment::open failed to > shm_open(/squid-ssl_session_cache.shm): (2) No such file or directory > > Squid Cache (V

Re: [squid-users] Failed to shm_open

2017-03-01 Thread erdosain9
Im having this problem too mar 01 12:23:37 squid.x.lan squid[17628]: Error negotiating SSL connection on FD 181: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1) mar 01 12:23:38 squid.x.lan squid[17628]: Error negotiating SSL connection on FD

[squid-users] Failed to shm_open

2017-03-01 Thread erdosain9
Hi. Now squid stop... abnormaly. 2017/03/01 12:04:31 kid1| helperOpenServers: Starting 5/32 'ssl_crtd' processes FATAL: Ipc::Mem::Segment::open failed to shm_open(/squid-ssl_session_cache.shm): (2) No such file or directory Squid Cache (Version 3.5.20): Terminated abnormally. CPU Usage: 0.095 sec