Opened 2 years ago
Closed 2 years ago
#3490 closed bug (Invalid)
Deluge cannot start - No JSON object could be decoded
Reported by: | hazikimert | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | needs verified |
Component: | Unknown | Version: | 1.3.15 |
Keywords: | Cc: |
Description
Hello.
My case is very similar to https://dev.deluge-torrent.org/ticket/3197#no1 I tried workaround described there, it is not working.
I see error message when start deluge demon:
pi@<name>:~ $ deluged pi@<name>:~ $ [ERROR ] 09:58:46 config:390 No JSON object could be decoded Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/deluge/config.py", line 388, in load
self.config.update(json.loads(data[start:end]))
File "/usr/lib/python2.7/json/init.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
raise ValueError?("No JSON object could be decoded")
ValueError?: No JSON object could be decoded
I am using Raspberry pi 4 with SW version(s): deluged: 1.3.15 libtorrent: 1.1.11.0
OS: PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
Notes:
- deluge-web is working (but forgets path setting, it is different story).
- I configured deluge based on page https://pimylifeup.com/raspberry-pi-deluge/
Change History (2)
comment:1 Changed 2 years ago by hazikimert
- Summary changed from Deluge cannot start to Deluge cannot start - No JSON object could be decoded
comment:2 Changed 2 years ago by Cas
- Resolution set to Invalid
- Status changed from new to closed
I think I saw you had a post in the forum that I meant to reply that it's a corrupted config that results in that error.
Glad you figured it out!
I found the source of the issue, the ticket can be closed. core.conf line ""allow_remote": True," caused the issue, "true" shall be lower case and deluged starts perfectly and remembers configuration.