Skip to content

馃悰 The extend_lock job spams the hell out of your logs#17

Description

@coredumperror

Bug Description

I want to use django-crontask, but the fact that I get these two logs every 5 seconds is infuriating. How do I make it stop?

access_admin       | SYSLOG 2026-01-09T23:57:04.016898Z [info     ] Running job "contask.utils.lock.extend (trigger: interval[0:00:05], next run at: 2026-01-09 15:57:09 PST)" (scheduled at 2026-01-09 15:57:04.010919-08:00) [apscheduler.executors.default]
access_admin       | SYSLOG 2026-01-09T23:57:04.018155Z [info     ] Job "contask.utils.lock.extend (trigger: interval[0:00:05], next run at: 2026-01-09 15:57:09 PST)" executed successfully [apscheduler.executors.default]

Also that name has a typo. Should start with "crontask", not "contask". That's defined on line 73 in the management command.

Expected Behavior

Not getting my logs spammed with useless junk every 5 seconds.

Version

1.1.1

Stack trace

No response

Steps to Reproduce

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions