[squid-dev] squid3.5.27 can't show correctly https website.how can i certain the wrong area in code.

Amos Jeffries squid3 at treenet.co.nz
Fri Nov 10 03:42:48 UTC 2017


On 09/11/17 15:19, G~D~Lunatic wrote:
> i used squid 3.5.27  . the website is www.hupu.com  . Serveral websites 
> like this can't been shown correctly.
> i use command "./squid -k debug". The result like
> 2017/11/08 16:06:03.996 kid1| 41,5| AsyncCall.cc(38) make: make call 
> MaintainSwapSpace [call49573]
> 2017/11/08 16:06:03.996 kid1| 47,5| ufs/UFSSwapDir.cc(448) maintain: 
> space still available in /usr/local/squid/var/cache/squid
> 2017/11/08 16:06:03.996 kid1| 41,7| event.cc(322) schedule: schedule: 
> Adding 'MaintainSwapSpace', in 1.00 seconds
> 2017/11/08 16:06:03.996 kid1| 41,5| AsyncCallQueue.cc(57) fireNext: 
> leaving MaintainSwapSpace()
> 
> i can't understand because i thought debug message come from following 
> codes.
The output you see on the screen with that command is the debug from the 
"squid" process you just ran to start the debugging happening in the 
proxy process that was already running.
  The output from the running Squid proxy is in cache.log. The instant 
it gets the debug signal that log should start to fill with its details, 
until it exists or gets another signal to disable the debugging again.


The above log entries do not come from, and have nothing to do with the 
code lines you quoted below.


> debugs(33, 3, "Connection gone while waiting for ssl_crtd helper reply; 
> helper reply:" << reply);
> debugs(33, 5, HERE << "Certificate for " << sslConnectHostOrIp << " was 
> successfully recieved from ssl_crtd");
> 
> how can i certain the wrong area in code.
> 


These debugs() lines you quoted are part of the TLS/SSL certificate 
helper API code. So only get output when that code runs.

* The first debugs() line is in the event of a ssl_crtd helper 
disconnecting/terminating/crashing unexpectedly.

This is an error situation, so you should never see it anywhere in your 
logs. If it does happen it means the helper crashed or something equally 
bad. So start debugging the helper itself, not Squid.

* The second debugs() line is in the event of a certificate being 
successfully received by Squid from that helper.

Obviously that should happen a lot and is not much use other than to 
identify timing of when things happened in the TLS/SSL processing.


Amos


More information about the squid-dev mailing list