You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rss |
rss | INFO The [public/storage] link has been connected to [storagepublic].
rss |
rss |
rss | INFO Nothing to migrate.
rss |
rss |
rss | INFO Configuration cached successfully.
rss |
rss |
rss | INFO Blade templates cached successfully.
rss |
rss | 2024-01-10 21:40:51,526 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
rss | 2024-01-10 21:40:51,536 INFO supervisord started with pid 28
rss | 2024-01-10 21:40:52,542 INFO spawned: 'cron' with pid 29
rss | 2024-01-10 21:40:52,549 INFO spawned: 'nginx' with pid 30
rss | 2024-01-10 21:40:52,558 INFO spawned: 'php-fpm' with pid 31
rss | 2024-01-10 21:40:52,566 INFO spawned: 'php-queue-worker' with pid 32
rss | 2024-01-10 21:40:53,763 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
rss | 2024-01-10 21:40:53,764 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
rss | 2024-01-10 21:40:53,764 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
rss | 2024-01-10 21:40:53,765 INFO success: php-queue-worker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Think the cron action running as root is the cause of root-owned
cache files appearing in the app, causing permission issues when
attempted to write into the same folder by the nginx/worker process.
This changes the cron setup to load the cron command for the www-data
user instead.
Related to #24
I think, from testing, this was due to the cron/schedule-checking process running as root.
I've now updated the cron process to run as the same user as the webserver/queue, within commit 59dbeac.
I've just pushed this out via the v1.4.5 release.
So hopefully this will be solved now, although you may need to run the manual deletion an extra time (or set permissions) to clear the old root-only folders/files.
Problem
App keeps creating some cache data directories with owner root.
As listed below,
data/
(parent) directory's owner is http.I have to manually fix this almost every day by running
rm -r framework/cache/
.Directory structure
docker-compose.yml
Log
docker log
laravel.log
The text was updated successfully, but these errors were encountered: