Logs
- Thread starter ef1970
- Start date
what's the magento.cron.log for? For cron? https://devdocs.magento.com/guides/v2.3/config-guide/cli/config-cli-subcommands-cron.html
It is not a litemage log file, did you define it yourself?
similar to update.cron.log?
It seems a general question to Magento, not LiteMage.
It is not a litemage log file, did you define it yourself?
similar to update.cron.log?
It seems a general question to Magento, not LiteMage.
"LiteMage purged tags cat_p_4784" like log lines should be generated by LiteMage. but your question seems to be "why Magento cron logging doesn't work?", is it(if so, Magento cron logging doesn't control by LiteMage)? or you want to see more logs from LiteMage? If not for both, can you clarify your question and your situation a little more?
What is the "anything else" you really want to see?
What is the "anything else" you really want to see?
I'll try to rephrase:
From my understanding, magento.cron.log is supposed to contain errors from the cron runs and errors only - in other words, no output from successful runs. The output from the LiteMage appears to be a regular output message and should therefore not end up in the error log.
My questions are:
1) Since it still ends up there, is the module logging what it interprets as an error, or is it just a regular output message.
2) If the module logging an error, how can we see what the error is when it's logging a regular output message instead of the error.
3) If it's not an error, is it "overwriting" errors from other modules by forcing regular output to the error log?
From my understanding, magento.cron.log is supposed to contain errors from the cron runs and errors only - in other words, no output from successful runs. The output from the LiteMage appears to be a regular output message and should therefore not end up in the error log.
My questions are:
1) Since it still ends up there, is the module logging what it interprets as an error, or is it just a regular output message.
2) If the module logging an error, how can we see what the error is when it's logging a regular output message instead of the error.
3) If it's not an error, is it "overwriting" errors from other modules by forcing regular output to the error log?
As described on the page you linked to earlier, the cron job is:
* * * * * /usr/bin/php /var/www/html/magento2/bin/magento cron:run 2>&1 | grep -v "Ran jobs by schedule" >> /var/www/html/magento2/var/log/magento.cron.log
As I'm sure you know, the -v means invert match, so any other output than "Ran jobs by schedule" will be logged. From what I understand, this is so that the log file will contain error messages from modules if something went wrong. What is the point of filling up the log with successful runs? If there were no errors, the run was successful - there's no need to output this.
But please reply to my questions above if you can.
* * * * * /usr/bin/php /var/www/html/magento2/bin/magento cron:run 2>&1 | grep -v "Ran jobs by schedule" >> /var/www/html/magento2/var/log/magento.cron.log
As I'm sure you know, the -v means invert match, so any other output than "Ran jobs by schedule" will be logged. From what I understand, this is so that the log file will contain error messages from modules if something went wrong. What is the point of filling up the log with successful runs? If there were no errors, the run was successful - there's no need to output this.
But please reply to my questions above if you can.
Hello! If you can confirm that this is the only line that needs to be removed from module-litemage/Controller/Shell/Purge.php to fix the issue, we can do it ourselves:
$this->getResponse()->setBody(sprintf("LiteMage purged tags %s \n", implode(',', $this->_tags)));
But wouldn't be a bad thing if you would consider addressing as well it in future updates.
$this->getResponse()->setBody(sprintf("LiteMage purged tags %s \n", implode(',', $this->_tags)));
But wouldn't be a bad thing if you would consider addressing as well it in future updates.
