Failed to shm_open

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Failed to shm_open

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 seconds = 0.074 user + 0.021 sys
Maximum Resident Size: 134144 KB
Page faults with physical i/o: 0
2017/03/01 12:04:31| Set Current Directory to /var/spool/squid

What is happend??
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Failed to shm_open

erdosain9
Im having this problem too
mar 01 12:23:37 squid.xxxxxxxxxxxxxxxxx.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.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 467: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
mar 01 12:23:38 squid.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 471: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
mar 01 12:23:39 squid.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 414: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
mar 01 12:23:39 squid.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 446: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
mar 01 12:23:41 squid.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 266: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
mar 01 12:23:42 squid.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 276: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
mar 01 12:23:42 squid.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 266: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
mar 01 12:23:43 squid.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 211: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
mar 01 12:23:43 squid.xxxxxxxxxxxxxxxxx.lan squid[17628]: Error negotiating SSL connection on FD 136: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher (1/-1)
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Failed to shm_open

Amos Jeffries
Administrator
In reply to this post by erdosain9
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 (Version 3.5.20): Terminated abnormally.
> CPU Usage: 0.095 seconds = 0.074 user + 0.021 sys
> Maximum Resident Size: 134144 KB
> Page faults with physical i/o: 0
> 2017/03/01 12:04:31| Set Current Directory to /var/spool/squid
>
> What is happend??
>

One of three things, in order of likelihood:

a) your OS does not have /dev/shm running.

b) your Squid was not started with appropriate privileges to access
/dev/shm and create the shared-memory area. ie root.

c) a previous Squid process that was supposed to create that
shared-memory area is not running.


Amos

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Failed to shm_open

Amos Jeffries
Administrator
In reply to this post by erdosain9
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 figure out what ciphers are needed.
Unfortunately Squid does not have much useful debug information in this
area yet.

Amos

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Failed to shm_open

gutemberg.aci
This post has NOT been accepted by the mailing list yet.
Ola, isto ocorre quando executamos dois comandos de verificação e um de inicialização dentro de um script, exemplo:

arquivo executasquid.sh
echo '
#/bin/sh
/usr/local/squid/sbin/squid -z
/usr/local/squid/sbin/squid
' > executasquid.sh

chmod +x executasquid.sh

# sh executasquid.sh

tail -f /var/log/syslog
(squid-1): Ipc::Mem::Segment::open failed to shm_open(/squid-ssl_session_cache.shm): (2) No such file or directory
Squid Parent: (squid-1) process 28096 exited with status 1
 Squid Parent: (squid-1) process 28103 started
Ipc::Mem::Segment::open failed to shm_open(/squid-ssl_session_cache.shm): (2) No such file or directory
 Squid Parent: (squid-1) process 28103 exited with status 1


ocorre que o processo squid -z ainda esta esta sendo executado e por isso da o problema.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Failed to shm_open

nahor13
This post has NOT been accepted by the mailing list yet.
In reply to this post by Amos Jeffries
Hi,

I am facing a similar issue.

The pretext is as follows;

Squid's memory usage reaches a fairly high level, after which squid exits (not always) and starts again. The following logs are observed in case of such an event.

Apr 17 19:30:35 squid[32207]: Squid Parent: (squid-1) process 20196 exited with status 0
Apr 17 19:30:37 squid[27421]: Squid Parent: will start 1 kids
Apr 17 19:30:37 squid[27421]: Squid Parent: (squid-1) process 27423 started
Apr 17 19:30:37  squid[27421]: Squid Parent: (squid-1) process 27423 exited with status 0
Apr 17 19:30:37  squid[27428]: Squid Parent: will start 1 kids
Apr 17 19:30:37  squid[27428]: Squid Parent: (squid-1) process 27430 started
Apr 17 19:30:37  (squid-1): Ipc::Mem::Segment::open failed to shm_open(/squid-ssl_session_cache.shm): (2) No such file or directory
Apr 17 19:30:37  squid[27428]: Squid Parent: (squid-1) process 27430 exited with status 1
Apr 17 19:30:40  squid[27428]: Squid Parent: (squid-1) process 27460 started
Apr 17 19:30:40  (squid-1): Ipc::Mem::Segment::open failed to shm_open(/squid-ssl_session_cache.shm): (2) No such file or directory
Apr 17 19:30:40  squid[27428]: Squid Parent: (squid-1) process 27460 exited with status 1
Apr 17 19:30:43  squid[27428]: Squid Parent: (squid-1) process 27480 started

I believe is the third case which you have mentioned "c) a previous Squid process that was supposed to create that
shared-memory area is not running"

Is there a solution for this as of now? Or is there a way to stop this from happening?
Loading...