[squid-users] HTTPS woes

[L.P.H. van Belle]

Hai, 

Im guess, squid is starting to soon, or there is not /dev/shm 

Check/Try adding, if not already in /etc/fstab 

none      /dev/shm        tmpfs   defaults        0 0 

And reboot the server. 


Or, i dont know and someone else can tell you. ;-) 
But on my jessie with squid 3.5.24+ssl i dont see this problem. 

A small tip about the certificates on debian or ubuntu. 
Install ca-certificates ( apt-get install ca-certificates ) 
And read : https://www.brightbox.com/blog/2014/03/04/add-cacert-ubuntu-debian/ 



Greetz, 

Louis





 

> -----Oorspronkelijk bericht-----
> Van: squid-users 
> [mailto:squid-users-bounces at lists.squid-cache.org] Namens Olly Lennox
> Verzonden: woensdag 19 april 2017 11:22
> Aan: Amos Jeffries; squid-users at lists.squid-cache.org
> Onderwerp: Re: [squid-users] HTTPS woes
> 
> Thanks Amos, I'll install this. One last question if I may! 
> Squid is working fine now with both HTTP and HTTPS but for 
> some reason it is refusing to launch on boot. 
> 
> It works perfectly when started with "service squid start" 
> but not boot. The error is:
> squid.service - LSB: Squid HTTP Proxy version 3.x
>    Loaded: loaded (/etc/init.d/squid; generated; vendor 
> preset: enabled)
>    Active: failed (Result: resources) since Wed 2017-04-19 
> 10:19:18 BST; 53s ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 598 ExecStart=/etc/init.d/squid start 
> (code=exited, status=0/SUCCESS)
> 
> Apr 19 10:19:13 raspberrypi (squid-1)[1606]: 
> Ipc::Mem::Segment::open failed to 
> shm_open(/squid-ssl_session_cache.shm): (2) No such file or 
> direct Apr 19 10:19:13 raspberrypi squid[1283]: Squid Parent: 
> (squid-1) process 1606 exited with status 1 Apr 19 10:19:16 
> raspberrypi squid[1283]: Squid Parent: (squid-1) process 1633 
> started Apr 19 10:19:18 raspberrypi squid[1283]: Squid 
> Parent: (squid-1) process 1633 exited with status 1 Apr 19 
> 10:19:18 raspberrypi squid[1283]: Squid Parent: (squid-1) 
> process 1633 will not be restarted due to repeated, frequent 
> failures Apr 19 10:19:18 raspberrypi squid[1283]: Exiting due 
> to repeated, frequent failures Apr 19 10:19:18 raspberrypi 
> systemd[1]: squid.service: Daemon never wrote its PID file. Failing.
> Apr 19 10:19:18 raspberrypi systemd[1]: Failed to start LSB: 
> Squid HTTP Proxy version 3.x.
> Apr 19 10:19:18 raspberrypi systemd[1]: squid.service: Unit 
> entered failed state.
> Apr 19 10:19:18 raspberrypi systemd[1]: squid.service: Failed 
> with result 'resources'.
> 
> Any ideas?
> 
> 
> 
> ________________________________
> From: Amos Jeffries <squid3 at treenet.co.nz>
> To: squid-users at lists.squid-cache.org
> Sent: Wednesday, 19 April 2017, 5:22
> Subject: Re: [squid-users] HTTPS woes
> 
> 
> 
> Olly,  Debian provides a ca-certificates package containing 
> the Mozilla CA list. It is updated whenever the CA set 
> changes. Though of course you should have apt connected to 
> the relevant security repository (jesse-security?) for 
> regular updates.
> 
> 
> Amos
> 
> 
> On 19/04/17 03:10, Olly Lennox wrote:
> 
> Would you mind sharing the script you use?
> > 
> >oliver at lennox-it.uk
> >lennox-it.uk
> >tel: 07900 648 252
> >
>