Closed aerni closed 3 years ago
I know it's not a permanent fix but you can replace the stache clear command with php artisan cache:clear
. It'll clear the Laravel cache (and the Stache) without the stache error.
Ah sweet. Will try that. Did you run into this as well?
Yeah, I've ran into it in the past.
Your quick fix did it. php artisan cache:clear
instead of php please stache:refresh
.
This issue has not had recent activity and has been marked as stale β by me, a robot. Simply reply to keep it open and send me away. If you do nothing, I will close it in a week. I have no feelings, so whatever you do is fine by me.
Even though I'm using php artisan cache:clear
as well, this occasionally happens to me as well. I cannot even clear the cache manually from within Statamic. The only "fix" is to re-deploy the same code again. Really annoying and I fear going live with this bug in a few weeks.
Using Envoyer here with latest Laravel, Statamic and PHP 8.0.9 as of today.
Having the same issue here. Only re-deploy will fix it. Any ideas what causes this?
We also faced this same issue. What I noticed is that the webserver sometimes uses the old release-path of the previous release. This can be fixed by restarting Apache. I'm still investigating if it's the webserver or the PHP process itself.
But maybe this helps some of you.
@timkley Had the same problem, sometimes the old release-path was still used for some parts of the application.
Reloading php7.4-fpm
after clearing the cache but before the cache warmup did the trick for me now.
Thanks, @helloiamlukas for your insight. We restart the Apache now after every deployment and didn't have the issue again. Our hoster doesn't provide an easy way to only reload PHP at this time through our CD pipeline so this will have to do the trick for now.
We might have found the root cause and a solution here https://github.com/statamic/cms/issues/4628
Also check this solution with composer https://github.com/statamic/cms/issues/3832
Bug Description
I'm running into this error on every deploy. I always have to manually SSH into the server,
php please stache:clear
, and run the deployment again. No idea why this is happening.I'm using Ploi to deploy. It's very similar to Forge. This is the deploy script:
This is the stacktrace:
Environment
Statamic 3.0.21 Pro Laravel 8.11.2 PHP 7.4.11 aerni/zipper 1.2.0