Re: ssl bump
Andrey K <[email protected]> Thu, 16 Jul 2026 18:19:24 +0300
| Newsgroups | gmane.comp.web.squid.general |
|---|---|
| Message-ID | <CADJd0Y0BdfYdAH_T7DosdLFzg3LCbOi24nMvT8L2Lhb9ysgTmg@mail.gmail.com> |
--===============4380089054180496280== Content-Type: multipart/alternative; boundary="000000000000bd42b00656bbf798" --000000000000bd42b00656bbf798 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable @Vacheslav: > sudo /usr/libexec/squid/security_file_certgen -c -s > /var/cache/squid/ssl_db/certs -M 4MB You specified the wrong path (the correct one is /var/cache/squid/ssl_db )= . To recreate a certificate database you should do: sudo rm -rf /var/cache/squid/ssl_db sudo /usr/libexec/squid/security_file_certgen -c -s /var/cache/squid/ssl_db -M 4MB sudo chown -R squid:squid /var/cache/squid/ssl_db =D1=87=D1=82, 16 =D0=B8=D1=8E=D0=BB. 2026=E2=80=AF=D0=B3. =D0=B2 16:36, Ale= x Rousskov <[email protected] >: > On 2026-07-16 01:57, Vacheslav wrote: > > > 2026/07/16 08:34:24 kid1| WARNING: sslcrtd_program #Hlpr1 exited > > We need to figure out why your security_file_certgen helpers are > exiting. IIRC, those helpers have not been upgraded to report their > fatal failures to cache.log. There are a few tricks you can use to see > what the problem is, but I would probably start with these three: > > 1. Run security_file_certgen with sslcrtd_program parameters from the > command line, as Squid user. If you are lucky, it will complain about > something before it starts waiting for the helper request. > > 2. Redirect security_file_certgen stderr (but not stdout!) output into a > dedicated log file. It may be possible to do that right on the > sslcrtd_program line, without wrapping the helper into another script. > > 3. Enable full debugging, reproduce the problem with a single > transaction, and send a link to the corresponding compressed cache.log > file for analysis as detailed at > > https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-single-tra= nsaction > > > Cheers, > > Alex. > > _______________________________________________ > squid-users mailing list > [email protected] > https://lists.squid-cache.org/listinfo/squid-users > --000000000000bd42b00656bbf798 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">@Vacheslav:=C2=A0<div>> sudo /usr/libexec/squid/securit= y_file_certgen -c -s=C2=A0</div><div>> /var/cache/squid/ssl_db/certs -M = 4MB=C2=A0</div><div>You specified the wrong path (the correct one is=C2=A0 /var/cache/squid/ssl_db ).</div><div><br></div><div>To recreate a certifica= te database you should do:<div><br></div><div>sudo rm -rf=C2=A0<span style= =3D"background-color:transparent">/var/cache/squid/ssl_db</span></div><div>= sudo /usr/libexec/squid/security_file_certgen -c -s=C2=A0/var/cache/squid/s= sl_db -M 4MB</div><div>sudo chown -R squid:squid=C2=A0<span style=3D"backgr= ound-color:transparent">/var/cache/squid/ssl_db</span></div></div></div><br= ><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D= "gmail_attr">=D1=87=D1=82, 16 =D0=B8=D1=8E=D0=BB. 2026=E2=80=AF=D0=B3. =D0= =B2 16:36, Alex Rousskov <<a href=3D"mailto:rousskov@measurement-factory= .com">[email protected]</a>>:<br></div><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex">On 2026-07-16 01:57, Vacheslav wrote:<br> <br> > 2026/07/16 08:34:24 kid1| WARNING: sslcrtd_program #Hlpr1 exited<br> <br> We need to figure out why your security_file_certgen helpers are <br> exiting. IIRC, those helpers have not been upgraded to report their <br> fatal failures to cache.log. There are a few tricks you can use to see <br> what the problem is, but I would probably start with these three:<br> <br> 1. Run security_file_certgen with sslcrtd_program parameters from the <br> command line, as Squid user. If you are lucky, it will complain about <br> something before it starts waiting for the helper request.<br> <br> 2. Redirect security_file_certgen stderr (but not stdout!) output into a <b= r> dedicated log file. It may be possible to do that right on the <br> sslcrtd_program line, without wrapping the helper into another script.<br> <br> 3. Enable full debugging, reproduce the problem with a single <br> transaction, and send a link to the corresponding compressed cache.log <br> file for analysis as detailed at <br> <a href=3D"https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-s= ingle-transaction" rel=3D"noreferrer" target=3D"_blank">https://wiki.squid-= cache.org/SquidFaq/BugReporting#debugging-a-single-transaction</a><br> <br> <br> Cheers,<br> <br> Alex.<br> <br> _______________________________________________<br> squid-users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">squi= [email protected]</a><br> <a href=3D"https://lists.squid-cache.org/listinfo/squid-users" rel=3D"noref= errer" target=3D"_blank">https://lists.squid-cache.org/listinfo/squid-users= </a><br> </blockquote></div> --000000000000bd42b00656bbf798-- --===============4380089054180496280== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ squid-users mailing list [email protected] https://lists.squid-cache.org/listinfo/squid-users --===============4380089054180496280==--