Reoccurring CRITCAL error ... deluge.log :90 twisted.internet.base

[Charlweed]

This error is posted every 1/2 second or so, after I started downloading a torrent. When the queue was empty, there were no errors. The log file is now getting huge. But from the web-GUI, everything seems fine, and torrents seem to work as expected. I tried searching this forum, but nothing shows up for disk.num_blocks_cache_hits nor update_session_cache_hit_ratio. I suspect that this started after some system-wide update, but that could have been weeks or more ago.
Ubuntu 22.04.5 LTS
Python 3.10.12
Deluge2.0.3 installed via apt, deluge/jammy,now 2.0.3-3.1

Error message:

Code: Select all

13:14:09 [CRITICAL][deluge.log                    :90  ] twisted.internet.base
[Failure instance: Traceback: <class 'KeyError'>: 'disk.num_blocks_cache_hits'
/usr/lib/python3/dist-packages/deluge/core/daemon_entry.py:122:run_daemon
/usr/lib/python3/dist-packages/deluge/core/daemon.py:164:start
/usr/local/lib/python3.10/dist-packages/twisted/internet/base.py:701:run
/usr/local/lib/python3.10/dist-packages/twisted/internet/base.py:709:mainLoop
--- <exception caught here> ---
/usr/local/lib/python3.10/dist-packages/twisted/internet/base.py:1099:runUntilCurrent
/usr/lib/python3/dist-packages/deluge/core/core.py:345:_on_alert_session_stats
/usr/lib/python3/dist-packages/deluge/core/core.py:361:_update_session_cache_hit_ratio

]

[ambipro]

The immediate thought I have is that it may be related to libtorrent v2 being used on 2.0.3 which may rely on libtorrent v1. I don't remember when we first offered libtorrent v2 packaged, but the caching features are reliant on v1 in the traditional implementation.

I would suggest checking which libtorrent package you have installed first and foremost perhaps.

Also, Deluge 2.0.3 installed via apt is outdated, we are on 2.1.1 now and there are instructions for options to install the latest stable release on the Downloads page for a variety of OSs and methods. Would highly recommend you also (and primarily) update to the latest versioned release and see if you are still affected.