mhertz wrote:Yeah sadly not very helpful indeed, as you stated. Is it all torrents or just that one, since it worked fine in my two tests. Maybe also run the deluged daemon with debug-logging and see if anything on that end. Sorry can not help you with this unfortunetly.
Yes, deluge-console works in my build.
Ok - so...and forgive me if any of this sounds antagonistic...not meaning it to be and I appreciate all your help.
Firstly, are you/have you done these tests on a windows system? Right now I am using your latest dev build and installed in portable mode just on my laptop. All tests (including daemons) done from my laptop, so the box I was currently running my server on is out of the picture.
1) I figured out the deluge-console - however there is a pathing issue with it:
Code: Select all
C:\Users\me\Desktop\Deluge>deluge-console.exe "add C:\test\test.torrent"
C:\Users\Ben\Desktop\Deluge\testtest.torrent does not exist!
C:\Users\me\Desktop\Deluge>deluge-console.exe "add C:/test/test.torrent"
Attempting to add torrent: C:\test\test.torrent
Torrent added!
So I don't think (?) your batch option will work because windows will supply the path in the former format which will fail (as %1).
2) As far as the upload file issue - it still exists. Using just the portable install I started up a deluged-debug and deluge-web-debug with a fresh config. Again, this is not on the 2016 server I have been using, but simply my laptop - Windows 10 (instead of Server 2016) and just a second box to prove it isn't isolated to just one. And, in case I didn't mention I tried from Chrome and IE.
Anyway, I attached to the web over 8112 and attempted to upload a torrent and got the same invalid torrent and logs that I showed above.
deluged-debug with debug logs doesn't seem to show any additional info, but I will test one more time.
3) As far as the problems launching the GUI client..so weird:
I was able to get a launch of just deluge.exe using your portable build (although I first ran deluge-debug.exe and it seemed to just stop after a few lines of logging the first time or two. once I caught it said it didn't have config files, but that shouldn't matter because it should create them). Anyway after a run or two it seemed to launch consistently. What's interesting is after it seemed to work, I went back to launching my installed version and is seemed to be opening consistently.
However, as I was typing this I tried to run it again and got the old behavior. When this happens deluge shows in the task manager and literally my typing slows down to one character on the screen per second...slows down my whole system. This might last for 30 seconds or a couple of minutes.
If I kill the process tree from task manager it doesn't kill deluge.exe immediately. In fact it takes about another minute and if you try to kill it again during that time you get an error from task manager. I did similar runs from the command line and when it fails to run I CTRL-C out of it, but it doesn't totally die. It stays running for up to 5 minutes or so and gives me the continue error if I try to stop it with another CTRL-C:
Code: Select all
11:37:11 [DEBUG ][deluge.ui.gtk3.gtkui :65 ] OS signal "die" caught with args: (0,)
ConsoleCtrlHandler function failedTraceback (most recent call last):
File "C:\Program Files\Deluge\lib\site-packages\deluge\ui\gtk3\gtkui.py", line 150, in on_die
reactor.stop()
File "C:\Program Files\Deluge\lib\site-packages\twisted\internet\base.py", line 646, in stop
raise error.ReactorNotRunning(
twisted.internet.error.ReactorNotRunning: Can't stop reactor that isn't running.
I then wiped out the appdata location to allow a totally fresh run with your portable install and continue to get the same issue.
I took a debug log which is here:
https://pastebin.com/7N1rpkCt
If you take a look there is about a 2 minute hang between 13:01:09 and 13:03:35. On previous runs this delay was like 15 minutes at the exact same point. Then as you look down there are more large delays...7 minutes...then 4 until 13:14 when it says it is showing the window.
So basically it seems to just sit there, not doing or logging anything for minutes at a time.
I have no event log errors, my disks are good, don't seem to have issues with anything else so I have no idea what is going on here. The problem is this happens on my 2016 box too, although with much less frequency (I also rarely use it on that box, but when I do use the GUI client I would say maybe 25% of the time I have this issue vs 90% of the time on my laptop).
So, in short, I am recreating these issues using a clean portable install of your version on two different Windows OS systems.
What are my next steps?
thanks