Class log does not exist

I have a similar problem. My tests all work fine on Vagrant, but when they are run on Scrutinizer as part of a pull request, they fail because they can't find Log::info();

I found out that this exception get thrown very early when starting the framework. I put an echo in Container.php to find out what is being resolved. On my mac php artisan returns

App\Console\Kernel
Illuminate\Foundation\Bootstrap\DetectEnvironment
Illuminate\Foundation\Bootstrap\LoadConfiguration
App\Exceptions\Handler
log
PHP Fatal error:  Uncaught exception 'ReflectionException' with message 'Class log does not exist' in /Users/freek/dev/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php:778

On homestead everything works fine. These classes are displayed:

App\Console\Kernel
Illuminate\Foundation\Bootstrap\DetectEnvironment
Illuminate\Foundation\Bootstrap\LoadConfiguration
Illuminate\Foundation\Bootstrap\ConfigureLogging
Illuminate\Foundation\Bootstrap\HandleExceptions
Illuminate\Foundation\Bootstrap\RegisterFacades
Illuminate\Foundation\Bootstrap\SetRequestForConsole
Illuminate\Foundation\Bootstrap\RegisterProviders
Illuminate\Foundation\Bootstrap\BootProviders
DaveJamesMiller\Breadcrumbs\Manager
DaveJamesMiller\Breadcrumbs\CurrentRoute
DaveJamesMiller\Breadcrumbs\Generator
DaveJamesMiller\Breadcrumbs\View
Laracasts\Generators\Commands\SeedMakeCommand
Laracasts\Generators\Commands\MigrationMakeCommand
Illuminate\Foundation\Composer
Laracasts\Generators\Commands\PivotMigrationMakeCommand
Illuminate\Console\Scheduling\ScheduleRunCommand
App\Console\Commands\ScheduledBackupCommand
App\Services\ModuleGenerator\Command\GenerateModuleCommand
App\Console\Commands\DeleteOldDraftsCommand
App\Console\Commands\SlackCommand

I'm still puzzled by what causes the error on my mac.

Found the error. I got a custom config file with this contents

return [
    'version' => '5.0.2',
    'installDate' => (new DateTime('20150514')),
];

When removing usage of the DateTime-class php artisan runs without problems on my mac. I'm glad I found the source of the problem but I'm puzzled why use DateTime is causing an error.

@freekmurze which file is it? This morning it started to give me the same error and I don't know why!

sorry for resurrecting this thread @freekmurze how do you echo the stack?

I struggled with this error today, after upgrading to L5.2, and found it came down to my .env file. The error was thrown because one of the values in this file had spaces. To fix, I just enclosed these values in double quotes.

Thank you @tomturton , save me a night long debugging :P

@tomturton Had same issue, your comment helped me to fix it. Problem occurs starting from Laravel 5.2.6

@tomturton , could you point out how you debug and came to that conclusion?

@tomturton Thank you sir! That saved me a LOT of time.

These errors might occure early during Laravel startup because a Facade is used (in our case Log) before it has been loaded in the application Container through its service Provider.... It seems that Laravel 5.2 tries to Log some error beffore the Log class has been initilized yet...

@tomturton thx, had same problem with .env file

The same, so much time wasted on debugging, thanks a lot. :)

Removing space character from environment variable value fixed my problem.

For me it was a error in custom config.

I had the same error . I had a space in the .env file. Surrounding it with quotes fixed the problem. Thanks a lot!

Thank you @tomturton That was indeed the issue!

@tomturton yes this was the problem for me too. Thanks for the solution - can you shed any light on to why this was happening. Anyone know why this was happening though!?

@tomturton thanks so much.. I spent 2 days debugging and if it would've been for your solution, I would've been still lacking

Solution, how to find problem:

1. make a backup copy of config folder.
2. try to delete one config at a time and try to run composer/artisan command that failed.
3. When you find file that failed - search for a row that can possible fail. Reason why it is failed is:
4. You use class constant that is not loaded yet.
5. You use class/function that is not loaded yet. etc

Double quotes! Made my day. Thxs

@tomturton : Arigato !!

Accidentally pasting some garbage into config/app.php will also result in this error, as I just discovered the hard way...

how can we use trans() helper in a custom config file?

I had a missing ; in a custom config file...

This also happens if you have a space without quotes around words in the .env file; for example:

Error: WEBSITE_TITLE=Website title - Good: WEBSITE_TITLE="Website title"

my .env has no spaces but I get this error. am using 5.2 and php 7

@tomturton you hero! :)

@tomturton thanks, the issue with value had space in .env file

@tomturton Bangarang! Tanks!