To stop you from the start, there is NO permission issue. /storage is recursively chmodded 777 and whole project folder is chowned by apache:apache
I even renamed the log file to ...-old and apache created a new one... if it didn't have actual write permissions it would not had been allowed to create it.
Running under CentOS release 6.6 (Final)
Deployed the project from git, the homestead works for my colleague.
Full error:
[Mon May 18 10:17:58 2015] [error] [client 86.124.208.14] PHP Fatal error: Uncaught exception 'UnexpectedValueException' with message 'The stream or file "/var/www/vhosts/mapper.pavementlayers.com/storage/logs/laravel-2015-05-18.log" could not be opened: failed to open stream: Permission denied' in /var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:84\nStack trace:\n#0 /var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Handler/RotatingFileHandler.php(88): Monolog\Handler\StreamHandler->write(Array)\n#1 /var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(37): Monolog\Handler\RotatingFileHandler->write(Array)\n#2 /var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Logger.php(265): Monolog\Handler\AbstractProcessingHandler->handle(Array)\n#3 /var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Logger.php(543): Monolog\Logger->addRecord(400, 'exception 'Symf...', Array)\n#4 /var/www/vhosts/mapper.pavementl in /var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php on line 84
It could be that SElinux is preventing Apache to create this file.
To test this you could disable SElinux temporally with the following command:
setenforce 0
This will place SElinux in permissive mode. This means that you still receive an error message in your SElinux log file but SElinux will not block the command.
To activate SElinux again you can type:
setenforce 1
Or reboot your CentOS server.
Unfortunately I had also problems with Laravel 5 on CentOS and the cause was SElinux. I ended up with disabeling SElinux and I know it is not the right thing to do but I didn't had time to get the two working together yet!
Update
So I finally had sometime to investigate this further and I got SELinux working together with Laravel 5. I just update this post for people that might run into this issue cause disabling SELinux is not the best strategy as mentioned above.
Three things need to be done:
The folders Storage and Bootstrap/Cache need to have the right SELinux context. This can be achieved via the following commands.
semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/<Laravel Site>/storage(/.*)?" semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/<Laravel Site>/bootstrap/cache(/.*)?"The SELinux context needs to be applied on the directories.
restorecon -Rv "/var/www/<Laravel Site>/storage" restorecon -Rv "/var/www/<Laravel Site>/bootstrap/cache"The Apache user needs to have the rights to create files in both directories. This can be achieved via a ACL in CentOS 7.
setfacl -R -m u:apache:rwX storage/ setfacl -R -m u:apache:rwX bootstrap/cache/
The last thing you need to do is enabling SELinux again.
Try those commands for laravel 5
$ php artisan cache:clear
$ sudo chmod -R 777 app/storage
$ composer.phar dump-autoload
This happens because laravel do not have the permissions to write to the log file, at least for my case.
This worked for me, Laravel 5.4 and above
$ sudo chmod -R 755 storage/
$ sudo chown -R www-data storage/
$ sudo chgrp -R www-data storage/
$ php artisan cache:clear
$ php artisan config:cache
$ composer dumpautoload
Not all steps necessary.
You have to make sure the storage folder exists. If you're deploying from git, make sure the storage folder itself is tracked and created automatically.
ON Laravel 5.7
$ cd /var/www/html/ $ php artisan cache:clear Application cache cleared!
for centos 7
# ausearch -c 'httpd' --raw | audit2allow -M my-httpd
# semodule -i my-httpd.pp
来源：https://stackoverflow.com/questions/30306315/laravel-5-laravel-log-could-not-be-opened-permission-denied