Open acashley opened 3 years ago
@acashley thanks for the report. I think this is a result of Magento's native cache.log. I've long wanted to remove it (it is incredibly annoying). I'll see if I can figure out docs on how to disable this log.
I don't think disabling it automatically is in the scope of this particular repo, but it's obnoxious enough that I think most people want to know how to disable it.
@acashley see https://devdocs.magento.com/guides/v2.4/config-guide/cli/logging.html#to-disable-debug-logging
bin/magento setup:config:set --enable-debug-logging=false
Let me know if this works for you. In a production environment, this should be off anyways.
But, locally, this is what I use to disable the cache logs.
@damienwebdev thanks for your quick reply!
Interesting, I see in the docs referenced that the debugging should be disabled by default in production mode, but I am still seeing this output in both developer and production modes.
By default, Magento writes to the debug log (<install_directory>/var/log/debug.log) when it is in default or develop mode, but not when it is in production mode.
:bug: Bug report
Current Behavior
When clearing the cache, the following
cache_invalidate
debug output is observed in build logs:Expected Behavior
Expect not to see these debug output/errors.
Minimal reproduction of the problem with instructions
magento2-stdlogging module
/bin/php magento cache:clean
What is the motivation / use case for changing the behavior?
Not sure why this output is logged now? Looks like the URL mentioned is malformed:
GET","url":"http:/"
This output was not logged before installation of magento2-stdlogging module and disappears upon removal of the module.Environment