No log being generated

[Crimsonfox89]

Debug mode

• [X] I have enabled debug mode
• [X] I have read checked the Common Issues page

Describe the bug

I have set APP_DEBUG=true in my .env file and the laravel.log file is not being created. I can see log output in Docker Desktop but when I navigate to storage/logs/ there is nothing there. The output in Docker Desktop also does not look like it is outputting debug level logs.

Reproduction steps

1. Change APP_DEBUG=true
2. Stop, destroy and recreate the container
3. Check logs directory

Expected behavior

Laravel.log file to be created and written to

Screenshots

No response

Snipe-IT Version

Latest-Docker

Operating System

Windows/Docker

Web Server

Apache

PHP Version

7.4.3

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

2023-04-11 16:54:46 Module ssl already disabled
2023-04-11 16:54:49 Changing upload limit to 100
2023-04-11 16:55:04 Nothing to migrate.
2023-04-11 16:55:05 Configuration cache cleared!
2023-04-11 16:55:06 Configuration cache cleared!
2023-04-11 16:55:06 Configuration cached successfully!
2023-04-11 16:55:06 2023-04-11 15:55:06,817 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.
2023-04-11 16:55:06 2023-04-11 15:55:06,821 INFO supervisord started with pid 1
2023-04-11 16:55:07 2023-04-11 15:55:07,825 INFO spawned: 'exit_on_any_fatal' with pid 46
2023-04-11 16:55:07 2023-04-11 15:55:07,828 INFO spawned: 'apache' with pid 47
2023-04-11 16:55:07 2023-04-11 15:55:07,840 INFO spawned: 'run_schedule' with pid 48
2023-04-11 16:55:08 No scheduled commands are ready to run.
2023-04-11 16:55:08 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.3. Set the 'ServerName' directive globally to suppress this message
2023-04-11 16:55:08 2023-04-11 15:55:08,876 INFO success: exit_on_any_fatal entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-11 16:55:08 2023-04-11 15:55:08,876 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-11 16:55:08 2023-04-11 15:55:08,876 INFO success: run_schedule entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-11 16:55:08 httpd (pid 48) already running
2023-04-11 16:55:08 2023-04-11 15:55:08,895 INFO exited: apache (exit status 0; expected)

Additional context

No response

[welcome[bot]]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[snipe]

I have set APP_DEBUG=true in my .env file and the laravel.log file is not being created.

APP_DEBUG doesn't create the laravel.log file, it just determines whether or not the debug bar is shown.

This seems like a duplicate of #12725.

[Crimsonfox89]

I have set APP_DEBUG=true in my .env file and the laravel.log file is not being created.

APP_DEBUG doesn't create the laravel.log file, it just determines whether or not the debug bar is shown.

This seems like a duplicate of #12725.

@snipe

Just checked #12725 and I'm not getting the error mentioned nor do I have a log file to change the owner of

[Crimsonfox89]

In case anyone finds this in the future, I deleted the volumes and containers and started from scratch but with the debug set to true from the start and that seems to be working now. If I get a chance, I'll do some more testing to see if I can replicate it more reliably.