Call to undefined method Monolog\Logger::listen()

[ultimateBusiness]

Fresh project at L5.6 @ Homestead on a Mac - Package autodiscovery - no other configuration - open the site and the above error appears.

If I change in ".env" the entry:
LOG_CHANNEL=stack
to
LOG_CHANNEL=stac (yes - this is not valid)

Result => the Debugbar is working - any suggestions?

[ultimateBusiness]

If I delete the hole entry "LOG_CHANNEL=stack" from .env will bring the same result.

[bilfeldt]

@ultimateBusiness did you manage to solve your issue?

[kylescousin]

This has nothing to do with debugbar.

From the 5.6 upgrade guide https://laravel.com/docs/5.6/upgrade:

"All logging configuration is now housed in its own config/logging.php configuration file. You should place a copy of the default configuration file in your own application and tweak the settings based on your application's needs."

You need to copy that file in your config folder so you can use the default log channel: stack.

[bilfeldt]

I was able to locate the error to some incompatibility with debugbar and the package antonioribeiro/countries-laravel. See this issue for more details: antonioribeiro/countries-laravel#6

I don't know if the issue relies on debugbar or antonioribeiro/countries-laravel but would assume the latter.

[corazzi]

For anyone still having this issue, set 'log' => false in the collectors array in config/debugbar.php (logs is fine, note the 's').

The non-existent ::listen() method is being called here (LaravelDebugbar.php:244).

I'll try to get around to a PR at some point.

[zareismail]

laravel are using the Monolog\Logmanager for all loging drivers. monolog not have listene method. and debugbar has not updated for this log storing. so the debugbar is causing error.
solution:
\Config::set('debugbar.collectors.log', false);

[iz-ben]

Using the comment by @bilfeldt I was able to narrow down the problem. Removing antonioribeiro/countries-laravel sorted out the problem

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If this issue is still present on the latest version of this library on supported Laravel versions, please let us know by replying to this issue so we can investigate further.
Thank you for your contribution! Apologies for any delayed response on our side.