Search found 13 matches
- Sun Apr 29, 2018 1:04 pm
- Forum: Support
- Topic: WebUI plugin weirdness
- Replies: 2
- Views: 2033
Re: WebUI plugin weirdness
I don't think it's related to the Web UI. Any edits to core.conf while deluged are running will be lost. Make all changes to core.conf while deluged is stopped.
- Fri Mar 23, 2018 3:06 am
- Forum: Support
- Topic: Device or resource busy
- Replies: 22
- Views: 13363
Re: Device or resource busy
I got libtorrent 1.2.0 compiled, but even with Deluge 2.0b1 I still get the same error. This is running boost 1.62, and I upgraded to boost 1.66 to check as well. Same error.
- Thu Mar 22, 2018 6:46 pm
- Forum: Support
- Topic: Device or resource busy
- Replies: 22
- Views: 13363
Re: Device or resource busy
Okay... I can confirm that qBittorrent on the new stable kernel linux-image-4.9.0-6-amd64 works perfectly fine. Deluge does not. I can also confirm that Deluge 2.0b1 exhibits the same behaviour. I compiled libtorrent 1.1.6 from source and the problem still persists. I did a compile of the latest lib...
- Tue Mar 20, 2018 10:19 pm
- Forum: Support
- Topic: Device or resource busy
- Replies: 22
- Views: 13363
Re: Device or resource busy
Interesting. I have not been able to reproduce the error with qbittorent-nox all else being equal.
- Tue Mar 20, 2018 1:10 pm
- Forum: Support
- Topic: Device or resource busy
- Replies: 22
- Views: 13363
Re: Device or resource busy
I opened a bug report here. Please post any comments or research to that ticket.
- Tue Mar 20, 2018 2:39 am
- Forum: Support
- Topic: Device or resource busy
- Replies: 22
- Views: 13363
Re: Device or resource busy
I have not submitted a bug report yet. I just now concluded that the problem is unique to Deluge. I'm running Debian. I wanted to first eliminate the kernel as the source, so I installed the latest version from sid, which was linux-image-4.15.0-1-amd64. My test torrent was an 11 GB copy of SWTLJ, so...
- Sun Mar 18, 2018 4:30 am
- Forum: Support
- Topic: Unable to SSH into daemon from external network
- Replies: 1
- Views: 1330
Re: Unable to SSH into daemon from external network
The default port is 58846, but you won't be able to SSH right into the daemon. You could SSH into the server that the daemon is running on, but it would be better for you to either use the deluge web interface (deluge-web) or download the deluge client for your external PC then connect to the daemon...
- Sat Mar 17, 2018 2:54 pm
- Forum: Support
- Topic: [Solved] Deluge not running after upgrade to Jessie
- Replies: 4
- Views: 2942
Re: [Solved] Deluge not running after upgrade to Jessie
You're welcome! I'm glad you were able to adapt the solution.
- Sat Mar 17, 2018 5:20 am
- Forum: Support
- Topic: Device or resource busy
- Replies: 22
- Views: 13363
Re: Device or resource busy
******************** *** SOLUTION *** ******************** After days of searching, I think I've found the solution: rollback the Linux kernel. I have a feeling that the Spectre/Meltdown fix introduced in a recent patch slows down the box enough to cause large file operations consuming a lot of CPU...
- Sat Mar 17, 2018 2:23 am
- Forum: Support
- Topic: [Solved] Deluge not running after upgrade to Jessie
- Replies: 4
- Views: 2942
Re: Deluge not running after upgrade to Jessie
libboost was updated to 1.55.0 in Jessie. I would first make sure you have the latest version of deluge:
If that doesn't work and you need to force an older version of libboost, you can try:
Code: Select all
sudo apt-get update && sudo apt-get install deluged
Code: Select all
sudo apt-get install libboost-system1.49.0