Remove "Cleaned up N expired locks" log messages

But "Ultimate Cron Launcher Serial cleanup" logs on every run "Cleaned up 21 expired locks"

Yes. This message is to be expected. I should probably change the wording though. The explanation is, that the locking system is a 2-step cleanup process. When a lock is released, it is not removed from the database, but rather its state is changed. The cron job in question then removes them from the database with the mentioned message. A more proper message would be "Removed 21 old locks from the DB" or something. (The technical reasoning behind the 2-step cleanup is to mitigate potential gap-locks).
21 locks should be the result of you having exactly 21 cron jobs.

I don't understand the difference between the green checkbox and the blue info status

The icons reflect the max severity level that has been logged during the jobs run.

• INFO, DEBUG = Green tick
• NOTICE = Blue info
• WARNING = Yellow warning
• ERROR, CRITICAL, ALERT, EMERGENCY = Red cross

When i kept running "drush core-cron" all jobs were run every time, until i changed that to "drush cron-run". Maybe a message is useful like "Last cron was run from core. To benefit from ultimatecron run drush cron-run instead of drush core-cron"

When using Drush < 6, Ultimate Cron cannot hook into the core-cron drush command. In this case, the core cron jobs will be executed by Drupal core, but Ultimate Cron will still catch the log messages. However, it will catch all messages for all the jobs and log them for each job. When this happens, the init-message in the job log should state "Launched by Drupal core".

This message is to be expected. I should probably change the wording though.

Maybe if this hadn't been closed, but just reworded I wouldn't be here searching from Google what this message means.

I propose a wording change like the following, which reads and feels less like an error and more like a status:

Unlocked N completed cron tasks.

This proposed change does essentially two things:

1. State what is happening: i,e. removing/releasing the lock, instead of "cleaning up".
2. State more accurately what underlying object is affected, in a positive way, i.e "completed cron tasks" instead of "expired locks".

Are these messages worth logging if they do not make much sense in terms of "everything is OK" or "please pay attention"? I suggest to disable this logging to reduce garbage volume in logs.

I'm closing this since Drupal 7 is now unsupported and there will be no more development on the Drupal 7 branch of Ultimate Cron either.

Thank you for taking the time and effort in reporting this issue, even though it never got resolved.

This is still a valid issue on the current version of Ultimate cron, our logs are littered with this garbage everytime cron runs (15 mins for our production site)

There should at least be an option to turn this off.

Added configurable settings to disable lock cleanup logging or change its log level (debug/info/notice). Settings available at /admin/config/system/cron/settings under "Lock cleanup logging".

Includes 7 new tests (3 kernel + 4 functional).

Most of those tests add no value, I'm going to assume they were generated. We don't need to test the config API. A single test to save the UI would be sufficient. There also don't seem to be tests for the harder and more useful part of the actual logic where the config is used.

Configurable loglevel also seems overkill and if done, should use the log() method with level argument.

I'm open to just removing this without any setting, since there's no value in this information. That would also allow to simplify the code, we don't know the know the count, I'm also not sure why this does an update plus a looping select and a delete.

Hi @berdir let me correct according your comments.

I can confirm that it's a good change. We really don't need this data on watchdog.
Used a patch on my project (attached it in the comment).
I'm sure it can be merged.

Thanks

Patch with simple removal of count (from MR)

Merging.