Lofesa commented on issue #1720:
URL: 
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-732709393


   Well....
   
   `[Tue, 24 Nov 2020 01:06:40 GMT] [Warning] [3868463] Failed to read cache 
clean timestamp /mnt/ram/pagespeed/!clean!time!`
   Have the user that runs nginx write permission on `/mnt/ram/pagespeed/`? If 
yes, do:
   `touch /mnt/ram/pagespeed/!clean!time!``
   logged as these user and see what happens.
   
   `[Tue, 24 Nov 2020 01:06:35 GMT] [Info] [3868463] Unable to insert object of 
size: 38080, cache limit is: 35616`
   You have some cache sort in size, not necesarly pagespeed related, maybe 
fastcgi cache or other
   
   `[Tue, 24 Nov 2020 01:06:19 GMT] [Info] [3874643] HTTPCache 
key=https://uhl.site/ fragment=uhl.site: remembering recent failure for 299 
seconds.`
   `[Tue, 24 Nov 2020 01:06:19 GMT] [Error] [3868463] PageSpeed Serf fetch 
failure rate extremely high; only 0 of 534 recent fetches fully successful; is 
fetching working?`
   Pagespeed is unable to fecht resources, and remember the failure for 299 
seconds.
   Have you set correctly the LoadFromFile? Have you set correctly the 
Fechthttps?
   
   
>/mnt/ram/pagespeed/shm_metadata_cache/snapshot/,2Fmnt/ram/pagespeed/metadata_cache
   
   Seems you have enabled 
   `pagespeed ShmMetadataCacheCheckpointIntervalSec 300;`
   This makes the metadata cache stored in shm memory to copy it to disk (in 
this case every 5min.) and donĀ“t losse the info between restarts
   
   >Should I disable gzip also, same for brotli?
   
   The prblem with gzip/brotli comes when you enable gzip compression in 
pagespeed ( `pagespeed HttpCacheCompressionLevel 9;`) and will use brotli. When 
You use HttpCacheCompressionLevel  pagespeed resources are served gziped, no 
matter if you have brotli in plaze. if you will all resources brotli 
compressed, you need set `pagespeed HttpCacheCompressionLevel 0;`
   
   
   
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to