[squid-users] Random SSL bump DB corruption

[Stakres]

Hi All, Yury,

Facing the same problem at the moment with the squid 3.5.3, around 150
req/sec.
The SSL crash 5 min later with the error.

index.txt:
V	150623000000Z		7EE07E84896D06865495B87A061C4C55D03E428D	unknown
/C=US/ST=California/L=Mountain View/O=Google
Inc/CN=*.appspot.com+Sign=signTrusted+SignHash=SHA256
V	150617000000Z		4E50C8790541265060E8796852D2E1D2878D7089	unknown
/C=US/ST=California/L=Mountain View/O=Google
Inc/CN=google.com+Sign=signTrusted+SignHash=SHA256
V	150617000000Z		16802607779EC137D972E9731A3D8DD1D65F1819	unknown
/C=US/ST=California/L=Mountain View/O=Google
Inc/CN=accounts.google.com+Sign=signTrusted+SignHash=SHA256
V	150617000000Z		736D922E14C3E8E573141AC6E3E79C4218B1B541	unknown
/C=US/ST=California/L=Mountain View/O=Google
Inc/CN=*.google-analytics.com+Sign=signTrusted+SignHash=SHA256
V	150617000000Z		0A1D58F2065EA701CD60D874325AFB4D76602922	unknown
/C=US/ST=California/L=Mountain View/O=Google
Inc/CN=*.googleusercontent.com+Sign=signTrusted+SignHash=SHA256
V	150617000000Z		213231FB70E633CA37606F717BBD1A92AEA97D7B	unknown
/C=US/ST=California/L=Mountain View/O=Google
Inc/CN=*.google.com+Sign=signTrusted+SignHash=SHA256
SHA256

The last line is wrong 

Tested with 1 worker, 1 DISKD cache.

https_port 8189 intercept ssl-bump generate-host-certificates=on
cert=/etc/squid3/mycert.pem key=/etc/squid3/mycert.pem
sslproxy_capath /etc/ssl/certs
ssl_bump server-first all
sslcrtd_program /usr/local/squid3/lib/ssl_crtd -s /var/lib/ssl_db -M 16MB
sslcrtd_children 32 startup=5 idle=1

/var/lib/ssl_db is using the correct rights, all controled many times.

Any idea ?

Bye Fred





--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Random-SSL-bump-DB-corruption-tp4670289p4670630.html
Sent from the Squid - Users mailing list archive at Nabble.com.