C5-8.1.0 - a lot of cache errors "failed to open stream: No such file or directory"
Permalink
Hi,
All Optimization options are disabled.
Every time I add or remove a block or package in the dashboard and then click any link, it throws a cache error, e.g. "include(/var/www/*****/application/files/cache/0fea6a13c52b4d47/25368f24b045ca84/38a865804f8fdcb6/57cd99682e939275/2ddb27c5cdf0b672/745d4c64665be841/f18947d67b32332d/722fd307fdb64ecf.php): failed to open stream: No such file or directory"
I have to physically delete cache file from the server (through Filezilla) and then refresh the page 10 times, otherwise the site is simply stuck with the error. Or the issue goes away by itself after about 5-10 min.
This behavior has started in the latest 5.7 version, but it wasn't that bad as it is in 8.1. Is this a problem with C5 or hosting server? Can it be fixed?
All Optimization options are disabled.
Every time I add or remove a block or package in the dashboard and then click any link, it throws a cache error, e.g. "include(/var/www/*****/application/files/cache/0fea6a13c52b4d47/25368f24b045ca84/38a865804f8fdcb6/57cd99682e939275/2ddb27c5cdf0b672/745d4c64665be841/f18947d67b32332d/722fd307fdb64ecf.php): failed to open stream: No such file or directory"
I have to physically delete cache file from the server (through Filezilla) and then refresh the page 10 times, otherwise the site is simply stuck with the error. Or the issue goes away by itself after about 5-10 min.
This behavior has started in the latest 5.7 version, but it wasn't that bad as it is in 8.1. Is this a problem with C5 or hosting server? Can it be fixed?
Looking at that directory name, I'd be wondering if it's a permission limitation, possibly introduced by a recent upgrade of CPanel.
I would be checking the host server to see if they are running something like 'Varnish Cache' in the background.
If they have Varnish Cache in Control Panel, you should be able to turn it off.
I have done this for all my C5 sites..
If they have Varnish Cache in Control Panel, you should be able to turn it off.
I have done this for all my C5 sites..
Could it be something to do with PHP, eAccelerator, OPcache or Xcache? Does C5 caching rely on any of these? Or I can turn them off?
I have PHP-7.0. Does it matter? Is PHP-7 better than 5.6? CPanel has also got 7.1.
And how come the error goes away after 5 min?
I have PHP-7.0. Does it matter? Is PHP-7 better than 5.6? CPanel has also got 7.1.
And how come the error goes away after 5 min?
I'm having the exact same issue, my server doesn't even have the varnish installed. Whatever I save any change to the dashboard. Can't even save any changes to the whole site.
any idea?
any idea?
ah! i figured it out...
Just change all the files ownership under the concrete5 directory to www-data or whatever user you are running:
sudo chown -R www-data:www-data concrete5
Just change all the files ownership under the concrete5 directory to www-data or whatever user you are running:
sudo chown -R www-data:www-data concrete5
Why should I do that myself in general? Shouldn't it be done by the engine? Or it's something to do with the host settings? I have these problems with every site.
In my case the issue was related to folder permission .. just make sure below folders are writable by the web server process :
Application/files/
Application/config/
Packages/
Updates/
Hope it works for you as well
> On Oct 23, 2017, at 7:48 AM, concrete5 Community <discussions@concretecms.com> wrote:
Application/files/
Application/config/
Packages/
Updates/
Hope it works for you as well
> On Oct 23, 2017, at 7:48 AM, concrete5 Community <discussions@concretecms.com> wrote:
I've checked, all folders are 0755. Hosting provider said 0777 should not be used as it's unsafe.
>
> Can you make them 777 as recommended here ?https://documentation.concrete5.org/developers/installation/installation
> Can you make them 777 as recommended here ?https://documentation.concrete5.org/developers/installation/installation
but then the whole world will write to the folders
> Well I enabled the 777 briefly just to confirm the root cause. Once it worked I put it back to 755 since then no issues ..
My host has changed PHP version from 7.1 to 5.6 and all cache problems disappeared!
Why is then v7+ recommended?
Why is then v7+ recommended?
php7 is in by itself much faster for concrete5 v7+..
This error is for sure because the cache files are not readable / writable to the server.
make: to apply recursive ownership of everthing beneath application/files to the webserver and it should work.
If you only apply the rights to /application/files, then the application/files/cache directory and the files in it will not be included and it will not work.
This error is for sure because the cache files are not readable / writable to the server.
make:
chown -R www-data:www-data application/files
If you only apply the rights to /application/files, then the application/files/cache directory and the files in it will not be included and it will not work.
It gives me:
chown: invalid user: `www-data:www-data'
What permissions should I give to the 'files' folder? They're all 755 now. I can set recursive permissions in Filezilla.
chown: invalid user: `www-data:www-data'
What permissions should I give to the 'files' folder? They're all 755 now. I can set recursive permissions in Filezilla.
