Frequent Application Crashes Due to record_node_usages Job Skipping (Max Instances Reached)

[aminmr]

Describe the bug
The application crashes every few hours with the following log message:

Execution of job "record_node_usages (trigger: interval[0:00:10], next run at: 2024-12-29 19:22:39 UTC)" skipped: maximum number of running instances reached (1)

Attempts to resolve the issue, including increasing the job interval and enabling debugging, have not worked.

To Reproduce
This issue occurs on my instance, but I don’t have any additional information or logs to provide clear steps to reproduce it.

Expected behavior
The application should not crash, and the record_node_usages job should execute as intended without exceeding the maximum number of running instances.

Machine details (please complete the following information):

• OS: official marzban docker image
• Python version: 3.10.16
• Nodejs version: v18.19.0.
• Browser: -
• Database: SQLite
• Users: 120
• Nodes: 1 (just the master)
  marzban_version: v0.7.0
  xray_version: test on version v24.12.18(also tested with default xray of v0.7.0, same result)

Additional context
I attempted to increase the job interval to 120 seconds using the following variable:

JOB_RECORD_NODE_USAGES_INTERVAL=120

I enabled‍ DEBUG=True to gather more detailed logs, but no additional helpful information was provided after the crash.

Related issues:

#1199
#1333
#928
#892
#791

[aminmr]

do you have any suggestion to fix this temporarily until the refactor you mentioned? @M03ED

[miadabdi]

I'm experiencing the exact same issue.
If I don't check regularly the vpn service would go down and I would not know