Reputation: 3349

Laravel 5 show ErrorException file_put_contents failed to open stream: No such file or directory

I have a project on Laravel 5 and I work with it at the office and at home too. It works fine, but recently at home it stopped working. Laravel show me two ErrorException

file_put_contents(G:\project\storage\framework\views/751d8a0fd8a7d4138c09ceb6a34bb377aa2d6265.php):
failed to open stream: No such file or directory

and

file_put_contents(G:\project\storage\framework/sessions/aIXycR4LIAUBVIqZu0T590paOMIpV8vfZGIroEp0):
failed to open stream: No such file or directory

I'm searching problem decision with Google and find information about correct rights. All advice is about Linux, but I'am work in Windows at the office and at home too.

When I try to clear application cache and view cache, artisan talk to me - ...cleared. But cache data and views are present in storage.

How can I fix this problem?

Upvotes: 135

Answers (28)

Zahid

Reputation: 614

In my case delete cache folder from storage/framework/ and solved the issue.

Upvotes: 0

Rachael MacKeigan

Reputation: 49

Maybe there is an issue with your composer file. You could try:

composer install installs the vendor packages according to composer.lock (or creates composer.lock if not present),

composer update always regenerates composer.lock and installs the lastest versions of available packages based on composer.json

composer dump-autoload won’t download a thing. It just regenerates the list of all classes that need to be included in the project (autoload_classmap.php). Ideal for when you have a new class inside your project. Ideally, you execute composer dump-autoload -o , for a faster load of your webpages. The only reason it is not default, is because it takes a bit longer to generate (but is only slightly noticeable)

Above content originally quoted from Robin Brackez, What does ‘composer dump-autoload’ do in Laravel?

Upvotes: 1

Hashim Aziz

Reputation: 6165

For failing tests

I got this error when I made the mistake of deleting the tests/console folder along with the tests/source folder - specifically I was getting the following error from the Dusk tests running on my CI/CD environment (GitHub Actions):

ErrorException: file_put_contents(/home/runner/work/mysite/mysite/tests/Browser/console/Tests_Browser_MyDuskTest1_test_payments_are_working-0.log): Failed to open stream: No such file or directory

tests/source is an optional folder whereas apparently the tests/console is not and needs to exist in order for Dusk integrated tests to run.

I'm not sure why Dusk doesn't just create the folder dynamically when writing the console logs to disk, but either way, restoring the deleted console folder in the tests directory fixes the issue. If you can no longer restore the deleted folder, just creating the console folder with an empty .gitignore file in it should have the same effect.

Upvotes: 0

Yasir

Reputation: 1070

I solved this problem via creating storage\framework\sessions folder.

Upvotes: 16

Luis Rodriguez

Reputation: 493

I solved it clearing the content of:

/laravel/storage/framework/views

Then all the views were created again in that folder.

In my case these commands didn't fix it:

php artisan view:cache
php artisan route:cache
php artisan config:cache

I'm using Laravel 8 and in my case it seems that it was an issue with the permissions.

Upvotes: 1

Amit Verma

Reputation: 2547

The best way to solve this problem is, go to directory laravel/bootstrap/cache and delete config.php file. or you can rename it as well like config.php.old And your problem will be fixed.

Upvotes: 227

asghar

Reputation: 447

I went all the way, but I did not get the answer.
I just rename cache folder in storage/framework/ to cache1 and solved my problem.

Upvotes: -1

Peter Karsai

Reputation: 99

Clearing the contents of storage/framework/cache did the trick for me.

Upvotes: 1

Infomaster

Reputation: 871

I used Laravel 8, This is my solution:

Goto:
storage/framework/cache/data
set permission directory data is 777

Upvotes: 0

Clarance Liberiste Ntwari

Reputation: 4067

The solution that worked for me is to just serve the app as admin if you are

On mac or linux use sudo php artisan serve
On Windows try to open CMD as an adminstrator and then go to project directory and run php artisan serve

Upvotes: 0

Richathon

Reputation: 101

The reason is related to cache or permission.

Firstly, go to directory laravel/bootstrap/cache and delete all files from cache.

php artisan cache:clear
php artisan config:clear
php artisan config:cache

If the errors still happen. It may relates to permission Let's try command below (In my case user&group of laravel is nginx)

sudo chgrp -R nginx storage bootstrap/cache
sudo chmod -R ug+rwx storage bootstrap/cache

Upvotes: 3

Roshan Aravinda

Reputation: 21

The reason for this problem is the cache files in localhost. According to that I've tried several things as follows to clear the cache on my project, but every time I've failed.

Tried to clear cahe commands by changing web.php file (with artisan codes)
Tried to clear cache by connecting SSH (via PUTTY)
Tried to host my project in Sub domain within create a new Public directory

So I've found a solution for this problem after each and every above steps failed and it worked for me perfectly. I deleted the cache.php file in host_route/bootstrap/cache directory.

Upvotes: 2

hidroquino

Reputation: 81

Changing name of /bootstrap/cache/config.php to config.php.old doesn't work for me neither clearing cache with the commands artisan

php artisan config:clear
php artisan cache:clear
php artisan config:cache

And for some weird reason I can't change permission for the owner on the directories, so my solution was running my IDE (Visual Studio Code) as admin, and everything works.

My project is in an F:/ path of another disk.

Upvotes: 2

Prem Sagar

Reputation: 165

This happens when you shift your website from local to live server or vice versa.
Simply go to bootstrap/cache and delete config.php.

Upvotes: 3

Dibyendu Mitra Roy

Reputation: 1665

In case of shared hosting when you do not have command line access simply navigate to laravel/bootstrap/cache folder and delete (or rename) config.php.

Upvotes: 4

Arafat

Reputation: 368

I deleted the file /public_html/bootstrap/cache/config.php

Then I ran php artisan config:cache

Upvotes: 4

Elisha Senoo

Reputation: 3594

You should typically run the php artisan config:cache command as part of your production deployment routine. As a solution to your problem, I suggest you recreate the cache file, for faster configuration loading.

To do this, run the following Artisan commands on your command line

php artisan cache:clear
php artisan config:cache

You can programmatically execute the command by adding the following to your routes:

Route::get('/clear-cache', function() {
    $exitCode = Artisan::call('cache:clear');
    $exitCode = Artisan::call('config:cache');
    return 'DONE'; //Return anything
});

And then call the clear-cache route from your browser.

Upvotes: 85

aphoe

Reputation: 2726

In my case, I set APP_DEBUG=false since it is a production server, I decided to set it back to true and then it showed Missing BC Math or GMP extension

That is how I solved my own issue, setting APP_DEBUG=true might not work for everybody.

Upvotes: -1

Moh Alaraabi

Reputation: 213

If nothing work try the following in the production environment

composer install --optimize-autoloader --no-dev

php artisan cache:clear

php artisan config:clear

php artisan view:clear

php artisan config:cache

php artisan route:cache

Works for me

Upvotes: 2

Unique

Reputation: 9

This did the magic for me. chmod -Rf 0777 storage

Upvotes: -1

Bimal

Reputation: 911

If you are running laravel inside docker then access its filesystem

$ docker exec -it name-of-laravel-container /bin/bash

Next navigate to your laravel projects root directory. Make sure that you have inside storage/framework folder:

cache
sessions
testing
views

And they should be both readable and writable.

Upvotes: 3

Peter Drinnan

Reputation: 4533

In my case it was not anything that could be fixed with php artisan commands. The issue was folder permissions for the /storage folder. The error did not make that clear.

Upvotes: 0

shivanisdev

Reputation: 685

Actually I faced this issue when I moved my project from server to local.

storage/framework

four basic folders are required cache, sessions, testing, views

In My case sessions was missing might be in gitignore.

So I manually created session folder and refreshed browser and it was working.

So any of the missing folder if we delete this problem can be solved.

Upvotes: 24

Azeirah

Reputation: 6338

Apache + WSL on windows

This is a silly mistake, and a different answer compared to the others, but I'll add it because it happened to me.

If you use WSL (linux bash on windows) to manage your laravel application, while using your windows apache to run your server, then running any caching commands in the wsl will store the linux path rather than the windows path to the sessions and other folders.

Solution

Simply run the cache clearing commands in the powershell, rather than in WSL.

$ php artisan optimize

Was enough for me.

Upvotes: 11

Evgeniy

Reputation: 3349

After some research I understand - I have very similar, but different root project locations and its cached in /bootstrap/cache. After cache clearing project started.

Upvotes: 69

Carlos Avalos

Reputation: 247

Try with these commands that have been useful with those errors

path\project\storage\framework\views...

php artisan view:clear

path\project\storage\framework/sessions...

php artisan config:cache

Upvotes: 6

Bijaya Kumar Oli

Reputation: 2193

This type of issue generally occurs while migrating one server to another, one folder to another. Laravel keeps the cache and configuration (file name ) when the folder is different then this problem occurs.

Solution Run Following command:

php artisan config:cache

https://laravel.com/docs/5.6/configuration#configuration-caching

Upvotes: 7

Sergey Khmelevskoy

Reputation: 2544

I had similar problems because of .gitignore for the /storage folder on first machine, then cloned repository on second machine and laravel was revision to write down sessions cache

So, manually creating folder /storage/sessions might be an solution..

Upvotes: -1

Laravel 5 show ErrorException file_put_contents failed to open stream: No such file or directory

Answers (28)

For failing tests

Apache + WSL on windows

Solution

Related Questions