andrewbrg commented on issue #1686: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-653889352
It's a docker system with a mounted stateful drive for cache. There are multiple restarts (on every release) however the drive remains intact between deployments. I dunno, it's just info I am giving you guys in case it helps with other similar issues. I noticed that dropping the pagespeed cache folder completely and re-creating it fixed the issue. The re-written images were available immediately from the memcached server. I set the server to allow a max size of 3mb i think, nothing is really bigger than that. Thanks :) On Sun, 5 Jul 2020 at 12:15, Lofesa <notificati...@github.com> wrote: > Have you done a system restart? > Some systems when restarted re-create folders with determined user and > permisions, and may be these user/permision don´t permit write to the user > that runs the apache/nginx processes. > For example, in Centos distro you have the /etc/tempfiles.d/ directory > that may contain config files with lines like: > D /var/run/cache/nginx/ 0755 nginx nginx - > This line creates a directory (D) in this path with this permissions and > user/group owner. > This directory is created each restart if don´t exists. > > In other hand, memcached don´t store all pagespeed cache objects. Their > default config, stores only objects until 1Mb. This size is configurable > but allways fixed. If you configure it to store objects until 5Mb, these > that are biger need the file cache and if these file cache don´t exists or > is unwritable..... > Redis can store object of any size. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-653869325>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABNJRH6MOWKN4XKS4ZWDKLTR2BHFBANCNFSM4MTB4TGA> > . > ---------------------------------------------------------------- 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
