&quot;Class LogManager not found in LogServiceProvider&quot; After upgrade to PHP8.1

https://github.com/laravel/framework/blob/8.x/src/Illuminate/Log/LogManager.php

Level 102

Can you check one of the servers if the file exists?

Level 1

@Sinnbeck Yes, I've verified on a couple of the servers that the file actually exists. The LogManager that is "not found" is even in the same directory as the LogServiceProvider.php file.

Level 1

This gets curiouser and curiouser. As mentioned, MOST logging is actually working, but I was able to find a specific case where it failed each time and started experimenting. Essentially the error is being thrown when attempting to resolve the logger from the app service container. Here's what I'm working with (Its inside of a UserEventListener):

    public function onLoggedOut($event)
    {
        logger('User Logged Out: '.$event->user->full_name);
    }

    public function onLoggedIn($event)
    {
//logger('1');
        $ip_address = request()->getClientIp();
//logger('2 ');
        // Update the logging in users time & IP
        $event->user->fill([
            'last_login_at' => now()->toDateTimeString(),
            'last_login_ip' => $ip_address,
        ]);
//logger('3');
        // Update the timezone via IP address
        $geoip = geoip($ip_address);
logger('4');
        if ($event->user->timezone !== $geoip['timezone']) {
            // Update the users timezone
            $event->user->fill([
                'timezone' => $geoip['timezone'],
            ]);
        }
logger('5');
        $event->user->save();
logger('6');
        logger('User Logged In: '.$event->user->full_name);
    }

Here's what I've found:

For some reason, the call to logger() within the onLoggedOut method ALWAYS fails with the original error provided.
The original call to logger within onLoggedIn() function works.
HOWEVER, I added other logger calls within that same method (logger(1) - logger(6)) and only some of them work. The logger 1, logger 2, and logger 3 lines fail with the original error. But, logger 4, logger 5, logger 6 and the final/original logger lines all work. WHY would resolving the logger work on some of the lines within a function but not others?? And, more generally, how is the logger being resolved without error in some cases, but not in others??

Level 1

I should mention that logger() is just a helper method to resolve the log service, like: return app('log')->debug($message, $context);

I can swap out logger() for a call to \Log::debug() or any other context (ex \Log::info()) and get the exact same results.

Level 102

This thread has somewhat the same issue on forge https://laracasts.com/discuss/channels/laravel/logmanager-not-found

https://github.com/laravel/sail/issues/286

Level 102

Best Answer

Level 102

Seems to be php 8.1 related somehow

Level 1

@Sinnbeck A HUGE thank you for digging up that thread. I just swapped all of my servers/sites to PHP8.0. The errors are magically gone and logging is working in all cases now. Always fun monkeying around with production servers in the middle of the day. :|

It doesn't seem to be strictly caused by PHP8.1 since I didn't have these issues on my local environment running 8.1. Maybe something with config swapping, or a setting that Forge defaults to? Either way, things are now working. Cheers, mate.

Level 102

@wreckless happy to help. I am quite unsure what the cause is as well. Never seen a bug like that before. Might try recreating it with sail