cache not working

[Maciej Jackowski]

OpenLiteSpeed 1.4.39
I am getting errors like this
[ERROR] [HTTP2-65:lsapi] [Module-Cache] createEntry failed.
and cache is not working,
also no X-LiteSpeed-Cache:
header in response only
x-litespeed-tag:
37a1_PGSRP,37a1_URL.a739ea1a803bb4f59a7bb71b7054256e,37a1_Po.2,37a1_PGS,37a1_

server cache config

checkPrivateCache 1
checkPublicCache 1
maxCacheObjSize 10000000
maxStaleAge 200
qsCache 1
reqCookieCache 1
respCookieCache 1
ignoreReqCacheCtrl 1
ignoreRespCacheCtrl 0

enableCache 1
expireInSeconds 3600
enablePrivateCache 0
privateExpireInSeconds 3600
storagePath /tmp/lscache_server

Vhost is running with DocUID
and server on Ubuntu 16.04 as www-data,www-data user/group

whats wrong?

 

[David]

Please change the errorlog level to DEBUG High and reproduce this error.
The you will get more logs which can say the reason.
Thanks.
David

 

[Maciej Jackowski]

I changed to DEBUG High
and still and only the same error
[ERROR] [HTTP2-65:lsapi] [Module-Cache] createEntry failed.

 

[David]

Yes. Please paste the log around this one, actually, all logs about module cache should help.

 

[Maciej Jackowski]

I came to some conclusions after trials and errors
OpenLiteSpeed 1.4.39 compiled with server user/group www-data cant create subdirectory 'priv' in storagePath
but if I create 'priv' with www-data owner - it works

I think OpenLiteSpeed 1.4.38 works ok so it is regression, but 1.4.38 and 1.5rc5 cannot run SSL with Letsencrypt certs.

Another problem, same config for vhost and VHost Template PHP_SuEXEC

checkPrivateCache 1
checkPublicCache 1
maxCacheObjSize 10000000
maxStaleAge 200
qsCache 1
reqCookieCache 1
respCookieCache 1
ignoreReqCacheCtrl 1
ignoreRespCacheCtrl 0

expireInSeconds 3600
enablePrivateCache 1
privateExpireInSeconds 3600
storagePath $VH_ROOT/lscache
enableCache 0

but different results in response headers
vhost: X-Litespeed-Cache: hit,private
template: X-Litespeed-Cache: hit

why?

 

[David]

The 'hit' means served with public cache and 'hit,private' means served with private cache.

 

[Maciej Jackowski]

Ok I understand that but why same config give different result?
Private cache not available to template by design?

 

[David]

If the response header says server can save to private cache and private cache will be automatically enabled.
While serving, if there is private cache, server will serve it.

 

[Maciej Jackowski]

Sorry I understand nothing from your last quote

 

[David]

1, While serving a request, if the response header says 'server can save to private cache', then the private cache function will be automatically enabled, even if it is disabled in setting.
2, While serving a request, if there is private cache saved, server will serve this request with the private cache.