Home >Backend Development >PHP Tutorial >Share an example of solving the problem that Laravel cannot write logs
This article mainly introduces the solution to the problem that the log cannot be written in Laravel. The article gives detailed solutions for everyone to refer to and learn. It has certain reference value for everyone. Friends who need it can take a look below. I hope to be helpful.
Preface
Account login reported a 500 error, and no error message was returned. I had no choice but to use the original method, and now I am printing line by line. . After Log::info()
it will no longer be displayed normally, then the problem has been found.
The problem that causes the log to be unable to be written is because the file added during the code update belongs to the root user, so the log file created also has root permissions, resulting in other users' www permissions being unable to write to the log file.
So modify the user permissions of storage/logs/ to www
chown www:www storage/logs -R
Note: If the user uses the supervisord service to run the queue, if the queue If there is a log record, the running user also needs to be changed to the www user.
Problem 2
The same problem is that the log cannot be recorded. Here is the local environment usephp artisan queue:work - -sleep=3 --tries=3
Run.
The log is also written in the job, and the permissions are correct. However, the log cannot be recorded, and the task is executed normally.
Finally I thought of restarting the queue to solve this problem. I don’t know what caused it. If anyone knows, please let me know.
Restart queue command
php artisan queue:restart
Other issues not related to logs
Question 1
Recently in Using the Zizaco\Entrust permission package...
When I added the role...I reported an error...
BadMethodCallException in Repository.php line 391: This cache store does not support tagging.
It should be that there is a place in this package that uses laravel's cache, the default cache It is file
. Change CACHE_DRIVER
in .env to CACHE_DRIVER=array
Question 2
This error occurs on the page
View [.] not found.
Solution, optimization, clearing configuration cache, routing cache
php artisan optimize --force php artisan config:cache php artisan route:cache
Related recommendations:
Summary of the problem of php artisan migrate in laravel
Detailed explanation of how to install laravel 5.4 environment under iis 7
Detailed explanation of how to use Laravel event system to implement login log
The above is the detailed content of Share an example of solving the problem that Laravel cannot write logs. For more information, please follow other related articles on the PHP Chinese website!