I got the same error a few times in the last week as well. Would like to know why its happening.
I found that there is a new config in /app/config/session.php
/*
I have 'expire_on_close' => false,
set in /app/config/session.php
and the error still occurs. Anyone know what's going on?
I'm having same problem, my guess it has to do something with Laravel code itself?
"SplFileInfo::getMTime(): stat failed" stands for not checking if file_exists before reading it's last edit time.
Maybe Laravel somehows skips that check and tries to read "old" session anyway?
I'm having same problem and I would love to hear some explanation. My error reporting system (via mailing) is reporting those errors for unlogged in users, in some totally irrational routes like /administrator/index.php, /wp-login.php (when I'm not even having that routes).
I'm still getting this error once or twice a week. Anyone have a solution?
It's still irritating me, occurs in my log file sometimes few times per day...
[2014-08-28 10:10:01] production.ERROR: exception 'RuntimeException' with message 'SplFileInfo::getMTime(): stat failed for /app/storage/sessions/6fdad1a6699af10486c04c1f581d18500ecd9433' in /vendor/symfony/finder/Symfony/Component/Finder/Iterator/DateRangeFilterIterator.php:47
Stack trace:
#0 /vendor/symfony/finder/Symfony/Component/Finder/Iterator/DateRangeFilterIterator.php(47): SplFileInfo->getMTime()
#1 [internal function]: Symfony\Component\Finder\Iterator\DateRangeFilterIterator->accept()
#2 [internal function]: FilterIterator->next()
#3 /vendor/symfony/finder/Symfony/Component/Finder/Iterator/FilterIterator.php(47): FilterIterator->rewind()
#4 /vendor/laravel/framework/src/Illuminate/Session/FileSessionHandler.php(93): Symfony\Component\Finder\Iterator\FilterIterator->rewind()
#5 /vendor/laravel/framework/src/Illuminate/Session/Middleware.php(159): Illuminate\Session\FileSessionHandler->gc(7200)
#6 /vendor/laravel/framework/src/Illuminate/Session/Middleware.php(128): Illuminate\Session\Middleware->collectGarbage(Object(Illuminate\Session\Store))
#7 /vendor/laravel/framework/src/Illuminate/Session/Middleware.php(79): Illuminate\Session\Middleware->closeSession(Object(Illuminate\Session\Store))
#8 /vendor/laravel/framework/src/Illuminate/Cookie/Queue.php(47): Illuminate\Session\Middleware->handle(Object(Illuminate\Http\Request), 1, true)
#9 /vendor/laravel/framework/src/Illuminate/Cookie/Guard.php(51): Illuminate\Cookie\Queue->handle(Object(Illuminate\Http\Request), 1, true)
#10 /vendor/stack/builder/src/Stack/StackedHttpKernel.php(23): Illuminate\Cookie\Guard->handle(Object(Illuminate\Http\Request), 1, true)
#11 /vendor/laravel/framework/src/Illuminate/Foundation/Application.php(642): Stack\StackedHttpKernel->handle(Object(Illuminate\Http\Request))
#12 /public_html/index.php(49): Illuminate\Foundation\Application->run()
#13 {main} [] []
Yeah, this occurs often.
Someone with the time should notify Taylor about it. Or someone that cares.
it's not a laravel framework issue.>CedNet said:
Yeah, this occurs often.
Someone with the time should notify Taylor about it. Or someone that cares.
Taylor said: it's not a laravel framework issue. https://github.com/laravel/framework/issues/5221
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community