i am upgrading my test site from 2.1 to 2.2 (latest) and found that the cache is broken. the site ran fine on my local machine (installed fresh, not an upgrade). After performing the various necessary steps on my test server, i see this in the logs and the CSS/JS files don't load in the browser:
#6 [internal fu" while reading response header from upstream, client: xx.xx.xx.xx, server: test.ureka.org, request: "GET /cache/0/default/lightbox/elgg-colorbox-theme/colorbox.css HTTP/2.0", upstream: "fastcgi://unix:/socket/php-fpm.sock:", host: mysite.org", referrer: "https://mysite.org/admin/dashboard"
2017/03/28 09:48:16 [error] 30056#0: *490331 FastCGI sent in stderr: "PHP message: Exception at time 1490694496: Stash\Exception\InvalidArgumentException: Cache path is not writable. in /mysite/vendor/tedivm/stash/src/Stash/Utilities.php:231
i have checked all the steps i am aware of, but haven't resolved this yet.
the config file, database and data folder paths have not changed since the upgrade.
i tested this with and without the symlink for caching.
anyone know what i am missing?
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Nikolai Shcherbin@rivervanrain
Nikolai Shcherbin - 0 likes
- ura soul@tunist
ura soul - 0 likes
- ura soul@tunist
ura soul - 0 likes
- ura soul@tunist
ura soul - 0 likes
- ura soul@tunist
ura soul - 0 likes
- iionly@iionly
iionly - 0 likes
- Steve Clay@steve_clay
Steve Clay - 0 likes
- ura soul@tunist
ura soul - 0 likes
- Steve Clay@steve_clay
Steve Clay - 0 likes
You must log in to post replies.1 - Try to disable all Elgg caching (simple and system)
2 - Run Flush the caches and Upgrade both
3 - Deactivate temporary and purge all caches via 3rd services aka CloudFlare etc
4 - Clean the existing caches on your server e.g. tmp/nginx/cache etc
thanks for the suggestions.
i already did 1, 2 and 3 (as far as i can tell).
i am not aware of any caches i can clean on the server. tmp/nginx/cache doesn't exist and i don't recall setting a path for the nginx cache. when i disable any reference to caching for the nginx config for the site it makes no difference
the 'views_simplecache' folder for the site is empty
the permissions for that folder are the same as for my working, live site
so i have found that the cause of this was that i had the boot cache enabled in the settings.php file. when i disable the boot cache, everything works ok. however, when i re-enable it the problem returns. anyone know why?
Try with upgrading to latest Elgg 2.3 release. If it still doesn't work then it's likely a bug somewhere. If it works on 2.3, the bug has been fixed in the meantime (and won't get fixed in the 2.2 branch anymore anyway).
Does your settings.php set ->dataroot and/or ->cacheroot?
i will upgrade to 2.3 soon yes. @steve - i do have dataroot set in settings.php but not cacheroot
Hmm, well in the meantime I suppose you could set both and see if that lets you use the boot cache.