Project0 commented on issue #1516:
URL: 
https://github.com/apache/incubator-pagespeed-ngx/issues/1516#issuecomment-717932867


   > You are right that it would be nicer not to print that spurious message, 
so it's perfectly fine to have the startup script touch that file if it's not 
present. However that's not something PageSpeed itself does.
   
   My problem is really that file will never be created by nginx/pagespeed 
itself and throws continuously errors. The error starts usually after 1h and 
never stops. As i told already, this happens only when memcache is enabled: 
   ```
   2020/10/28 09:01:35 [warn] 428#434: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:01:35 [warn] 428#434: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:01:35 [warn] 421#427: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:01:35 [warn] 435#441: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:01:36 [warn] 428#434: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:01:59 [warn] 392#399: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:03 [warn] 392#399: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:10 [warn] 428#434: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:10 [warn] 428#434: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:15 [warn] 428#434: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:18 [warn] 428#434: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:22 [warn] 392#399: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:30 [warn] 428#434: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:35 [warn] 392#399: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:36 [warn] 392#399: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:46 [warn] 442#448: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   2020/10/28 09:02:49 [warn] 392#399: [ngx_pagespeed 1.13.35.2-0] Failed to 
read cache clean timestamp /var/cache/nginx/pagespeed/!clean!time!.  Doing an 
extra cache clean to be safe.
   ```


----------------------------------------------------------------
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