Deluged service not starting

General Discussion
1 
Oct 20 01:27:32 DietPi deluged[5646]: getattr(LoggingLoggerClass, event_dict['log_level'].name)(
Oct 20 01:27:32 DietPi deluged[5646]: File "/usr/lib/python3.9/logging/__init__.py", line 1489, in critical
Oct 20 01:27:32 DietPi deluged[5646]: self._log(CRITICAL, msg, args, **kwargs)
Oct 20 01:27:32 DietPi deluged[5646]: File "/usr/lib/python3.9/logging/__init__.py", line 1573, in _log
Oct 20 01:27:32 DietPi deluged[5646]: fn, lno, func, sinfo = self.findCaller(stack_info, stacklevel)
Oct 20 01:27:32 DietPi deluged[5646]: builtins.TypeError: findCaller() takes from 1 to 2 positional arguments but 3 were given
Oct 20 01:27:33 DietPi systemd[1]: deluged.service: Main process exited, code=exited, status=1/FAILURE
Oct 20 01:27:33 DietPi systemd[1]: deluged.service: Failed with result 'exit-code'.
Oct 20 01:27:33 DietPi systemd[1]: deluged.service: Consumed 2.296s CPU time.

 ─────────────────────────────────────────────────────
 DietPi v8.9.2 : 1 APT updates available
 ─────────────────────────────────────────────────────
 - Device model : RPi 4 Model B (aarch64)
 - CPU temp : 38 °C / 100 °F : Cool runnings
2

can you reboot your system and share the entire log pls

journalctl -u deluged
3 
root@DietPi:~# journalctl -u deluged
-- Journal begins at Thu 2022-10-20 18:30:48 BST, ends at Thu 2022-10-20 19:15:43 BST. --
Oct 20 18:30:58 DietPi systemd[1]: Started Deluge Daemon (DietPi).
Oct 20 18:31:07 DietPi deluged[757]: Unhandled error in Deferred:
Oct 20 18:31:07 DietPi deluged[757]: 18:31:07 [CRITICAL][twisted                       :154 ] Unhandled error in Deferred:
Oct 20 18:31:07 DietPi deluged[757]: Traceback (most recent call last):
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/deluge/common.py", line 1344, in run_profiled
Oct 20 18:31:07 DietPi deluged[757]:     return func(*args)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/deluge/core/daemon_entry.py", line 124, in run_daemon
Oct 20 18:31:07 DietPi deluged[757]:     log.error(
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1613, in unwindGenerator
Oct 20 18:31:07 DietPi deluged[757]:     return _cancellableInlineCallbacks(gen)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1529, in _cancellableInlineCallbacks
Oct 20 18:31:07 DietPi deluged[757]:     _inlineCallbacks(None, g, status)
Oct 20 18:31:07 DietPi deluged[757]: --- <exception caught here> ---
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1418, in _inlineCallbacks
Oct 20 18:31:07 DietPi deluged[757]:     result = g.send(result)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/deluge/log.py", line 79, in error
Oct 20 18:31:07 DietPi deluged[757]:     yield LoggingLoggerClass.error(self, msg, *args, **kwargs)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3.9/logging/__init__.py", line 1471, in error
Oct 20 18:31:07 DietPi deluged[757]:     self._log(ERROR, msg, args, **kwargs)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3.9/logging/__init__.py", line 1573, in _log
Oct 20 18:31:07 DietPi deluged[757]:     fn, lno, func, sinfo = self.findCaller(stack_info, stacklevel)
Oct 20 18:31:07 DietPi deluged[757]: builtins.TypeError: findCaller() takes from 1 to 2 positional arguments but 3 were given
Oct 20 18:31:07 DietPi deluged[757]: Temporarily disabling observer LegacyLogObserverWrapper(<bound method TwistedLoggingObserver.emit of <deluge.log.TwistedLoggingObserver object
 at 0x7f84578e80>>) due to exception: [Failure instance: Traceback: <class 'TypeError'>: findCaller() takes from 1 to 2 positional arguments but 3 were given
Oct 20 18:31:07 DietPi deluged[757]: /usr/lib/python3/dist-packages/twisted/internet/defer.py:962:__del__
Oct 20 18:31:07 DietPi deluged[757]: /usr/lib/python3/dist-packages/twisted/logger/_logger.py:190:failure
Oct 20 18:31:07 DietPi deluged[757]: /usr/lib/python3/dist-packages/twisted/logger/_logger.py:144:emit
Oct 20 18:31:07 DietPi deluged[757]: --- <exception caught here> ---
Oct 20 18:31:07 DietPi deluged[757]: /usr/lib/python3/dist-packages/twisted/logger/_observer.py:131:__call__
Oct 20 18:31:07 DietPi deluged[757]: /usr/lib/python3/dist-packages/twisted/logger/_legacy.py:93:__call__
Oct 20 18:31:07 DietPi deluged[757]: /usr/lib/python3/dist-packages/deluge/log.py:204:emit
Oct 20 18:31:07 DietPi deluged[757]: /usr/lib/python3.9/logging/__init__.py:1489:critical
Oct 20 18:31:07 DietPi deluged[757]: /usr/lib/python3.9/logging/__init__.py:1573:_log
Oct 20 18:31:07 DietPi deluged[757]: ]
Oct 20 18:31:07 DietPi deluged[757]: Traceback (most recent call last):
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 962, in __del__
Oct 20 18:31:07 DietPi deluged[757]:     log.failure(format,
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/twisted/logger/_logger.py", line 190, in failure
Oct 20 18:31:07 DietPi deluged[757]:     self.emit(level, format, log_failure=failure, **kwargs)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/twisted/logger/_logger.py", line 144, in emit
Oct 20 18:31:07 DietPi deluged[757]:     self.observer(event)
Oct 20 18:31:07 DietPi deluged[757]: --- <exception caught here> ---
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/twisted/logger/_observer.py", line 131, in __call__
Oct 20 18:31:07 DietPi deluged[757]:     observer(event)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/twisted/logger/_legacy.py", line 93, in __call__
Oct 20 18:31:07 DietPi deluged[757]:     self.legacyObserver(event)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3/dist-packages/deluge/log.py", line 204, in emit
Oct 20 18:31:07 DietPi deluged[757]:     getattr(LoggingLoggerClass, event_dict['log_level'].name)(
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3.9/logging/__init__.py", line 1489, in critical
Oct 20 18:31:07 DietPi deluged[757]:     self._log(CRITICAL, msg, args, **kwargs)
Oct 20 18:31:07 DietPi deluged[757]:   File "/usr/lib/python3.9/logging/__init__.py", line 1573, in _log
Oct 20 18:31:07 DietPi deluged[757]:     fn, lno, func, sinfo = self.findCaller(stack_info, stacklevel)
Oct 20 18:31:07 DietPi deluged[757]: builtins.TypeError: findCaller() takes from 1 to 2 positional arguments but 3 were given
Oct 20 18:31:08 DietPi systemd[1]: deluged.service: Main process exited, code=exited, status=1/FAILURE
Oct 20 18:31:08 DietPi systemd[1]: deluged.service: Failed with result 'exit-code'.
Oct 20 18:31:08 DietPi systemd[1]: deluged.service: Consumed 2.092s CPU time.
4

hmm not sure on the issue, let’s try to reinstall the package deluged

apt install --reinstall deluged
5

Still not starting.

Oct 20 23:45:55 DietPi deluged[55554]: getattr(LoggingLoggerClass, event_dict['log_level'].name)(
Oct 20 23:45:55 DietPi deluged[55554]: File "/usr/lib/python3.9/logging/__init__.py", line 1489, in critical
Oct 20 23:45:55 DietPi deluged[55554]: self._log(CRITICAL, msg, args, **kwargs)
Oct 20 23:45:55 DietPi deluged[55554]: File "/usr/lib/python3.9/logging/__init__.py", line 1573, in _log
Oct 20 23:45:55 DietPi deluged[55554]: fn, lno, func, sinfo = self.findCaller(stack_info, stacklevel)
Oct 20 23:45:55 DietPi deluged[55554]: builtins.TypeError: findCaller() takes from 1 to 2 positional arguments but 3 were given
Oct 20 23:45:56 DietPi systemd[1]: deluged.service: Main process exited, code=exited, status=1/FAILURE
Oct 20 23:45:56 DietPi systemd[1]: deluged.service: Failed with result 'exit-code'.
Oct 20 23:45:56 DietPi systemd[1]: deluged.service: Consumed 1.514s CPU time.```
6

maybe you can ask in parallel with Deluge forum on what the issue could be.

7

Maybe you can check out this thread:
https://forum.deluge-torrent.org/viewtopic.php?f=7&t=56160&p=234708&hilit=builtins.TypeError%3A+3+were+given#p234708
There was a problem when using an external drive with a samba share in combination with deluged. In this particular thread the external drive was faulty, if I understand correctly.
You could check with sudo dmesg -T after reboot for some erros that give maybe a hint if this is also maybe the problem in your case.