*OLD-THREAD - SEE NEW* [Unofficial] Deluge 2.0.x installer

[mhertz]

Glad to hear the workaround worked for you Also, thanks for reporting back, and you're very welcome!

[Labbz0re]

Glad to hear the workaround worked for you Also, thanks for reporting back, and you're very welcome!

Today 2 or 3 reboots later login info is gone again

*edit* restarted deluge and then it found login info again

[mhertz]

So it's seemingly a matter of deluge failing to read the hostlist.conf at times, and not a problem with writing to it, or clearing it. Unfortunetly I have no constructive feedback other than try run deluge multiple times with debug-logging enabled to see if you can catch a log of such scenario where connection-manager shows up blank and then see if any issues logged or post it here for us to see, either as attached file, uploaded to some file-hosting-site first, or posted here in code-tags.

Edit: To enable debug-logging for deluge, then copy the following and press: win+r > ctrl+v > return. The log(deluge.log) is saved to your desktop when quiting deluge again and is overwritten on each run also.

Code: Select all

"%programfiles%\Deluge\deluge.exe" -L debug -l "%userprofile%\Desktop\deluge.log"

(Change path if needed.)

[mhertz]

Doadin, when having fixed your remaining few issues(hopefully), then if there still possibly is gonna be some time before an official windows installer emerges by Cas(#3201 ticket I see is targeted for v2.1.x), and you'd like to release unofficial installers in mean time, then please give me a holler and I'll gladly shut down my links and instead link to your thread from mine Well, I'm sure i'd notice anyway if a new thread by you comes up, but was just thinking out loud here alittle, or whatever have you Thanks again for your community service

[mhertz]

Libtorrent had 3 commits added today in RC_1_2 branch, so I rebuilt libtorrent 1.2.x and installers.

[mhertz]

2 more commits to libtorrent 1.2.x - my script soon finished building.

Note, for feature, to not become to repetitive I'm not gonna continue make updates to this thread just because I rebuilded because a few libtorrent commits, so please yourself check date of installer and compare with last libtorrent commit date to see if updated yet or not, if interested.

https://github.com/arvidn/libtorrent/co ... 3...RC_1_2
https://github.com/arvidn/libtorrent/co ... 4...RC_1_1

(Currently libtorrent 1.2.x(default in installers) is 59 commits ahead of last release, and libtorrent 1.1.x is 2 commits ahead of last release.)

Edit: Script finished building now.

[mhertz]

Btw, I've not changed my mind about quitting developing these installers, as am not improving anything, or researching how to, but just simply update if libtorrent or deluge updates comes up, might as well when building-scripts already made, so no real effort on my part needed.

Im myself really glad to have made a new shell-script which starts windows VM in background(headless), runs building script in VM and displays output/progress in my own linux terminal and quits VM again. Then the rebuilding/upload from now on is made by running a single command in my linux terminal so don't even have to interact with windows no more and can stay in linux terminal and still follow along with the progress or verify no errors occured Looks exactly like running a linux shell-script this way.

Sorry, off-topic, but am just so impressed with this - not much needed to impress me seemingly, lol Have a nice weekend y'all!

[hitnrun30]

I am having the worst time with it being mean on Windows, you have done such a great job, I'm hoping you could help. First is that I can not add any plugins. maybe it is me or I'm doing something wrong but below is the command line I use with nssm to run it.

C:\HTPC\Deluge2\deluged.exe -c "C:\HTPC\Deluge2\Configuration" -L warning -l c:\HTPC\Deluge2\deluged.log

And when I do try to add a plugin I get this: (Folder definitely exists)

11:13:36 [ERROR ][deluge.ui.web.json_api :79 ] Error calling method `web.upload_plugin`: [Errno 2] No such file or directory: 'C:\\HTPC\\Deluge2\\Configuration\\plugins\\'
11:13:36 [ERROR ][deluge.ui.web.json_api :79 ] [Errno 2] No such file or directory: 'C:\\HTPC\\Deluge2\\Configuration\\plugins\\'
Traceback (most recent call last):
File "C:\HTPC\Deluge2\lib\site-packages\deluge\ui\web\json_api.py", line 160, in _handle_request
result = self._exec_local(method, params, request)
File "C:\HTPC\Deluge2\lib\site-packages\deluge\ui\web\json_api.py", line 122, in _exec_local
return meth(*params)
File "C:\HTPC\Deluge2\lib\site-packages\deluge\ui\web\json_api.py", line 953, in upload_plugin
shutil.copyfile(path, os.path.join(get_config_dir(), 'plugins', filename))
File "C:\HTPC\Deluge2\lib\shutil.py", line 121, in copyfile
with open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\HTPC\\Deluge2\\Configuration\\plugins\\'

[Vander]

After reinstalling with the newest installers I'm starting to see a massive amount of "Tracker Errors".

Deluge says Tracker Status is "Error: The system cannot open the device or file specified".

I'm not sure what the issue is exactly. I have been tinkering with the libtorrent settings using ltConfig - for example, I tried reducing the frequency of announces in case it was causing too many I/O requests on the drives.

I'm wondering if you still have an installer that was built using the "official stable release" of libtorrent 1.2.3 from back in December. If you do, then I could rule this issue out as a libtorrent problem. Even if you just have the libtorrent.pyd file, I could just pop that in the folder and see what happens.

[Montaigne]

After reinstalling with the newest installers I'm starting to see a massive amount of "Tracker Errors".

Deluge says Tracker Status is "Error: The system cannot open the device or file specified".

I'm not sure what the issue is exactly. I have been tinkering with the libtorrent settings using ltConfig - for example, I tried reducing the frequency of announces in case it was causing too many I/O requests on the drives.

I'm wondering if you still have an installer that was built using the "official stable release" of libtorrent 1.2.3 from back in December. If you do, then I could rule this issue out as a libtorrent problem. Even if you just have the libtorrent.pyd file, I could just pop that in the folder and see what happens.

I experienced the same thing today with a libtorrent 1.2 install. After restarting Deluge, the first announce goes through fine, but after a short while it starts failing with that error.

Reinstalling with libtorrent 1.1 seems to have fixed it.