id summary reporter owner description type status priority milestone component version resolution keywords cc 2339 logging is incomplete and inconsistent in the web UI back-end tmetro "When adding a torrent from a URL, you might see an error logged like: {{{ [ERROR ] 16:56:57 json_api:661 Error occured downloading torrent from https://btguard.com/broken-test.torrent [ERROR ] 16:56:57 json_api:662 Reason: 404 Not Found }}} or like: {{{ [WARNING ] 16:06:52 common:72 Unable to open /tmp/delugeweb-s3EDsB/bad-url.torrent: not a valid bencoded string [ERROR ] 16:06:52 json_api:700 not a valid bencoded string Traceback (most recent call last): File ""/usr/lib/python2.7/dist-packages/deluge/ui/web/json_api.py"", line 697, in get_torrent_info torrent_info = uicommon.TorrentInfo(filename.strip(), 2) File ""/usr/lib/python2.7/dist-packages/deluge/ui/common.py"", line 73, in __init__ raise e Exception: not a valid bencoded string }}} In the first case, it appears the failure occurs during the download_torrent_from_url() API call, while in the latter case the failure occurs in the add_torrents() call (when the contents of the previously retrieved file are discovered to not be a torrent). In neither case is the relevant failing API logged. In neither case are successful API calls logged, despite the service running with INFO logging level (-L info). This makes it difficult to troubleshoot failures." bug new minor 2.x Web UI 1.3.6