port preferences ignored on upgrade until daemon restarted

clarknova · Post by **clarknova** » Fri Dec 12, 2008 2:03 pm

I just upgraded from 1.0.6 to 1.0.7 and after restarting deluged (1.0.7) my active port has changed to something random, even though my preferences still show the correct port. After restarting deluged (1.0.7) a second it's listening on the correct port. I'm pretty sure I've seen the same thing happen on past upgrades. I believe the correct behaviour would be to have deluged preserve (or observe?) the port preferences from older versions when running the first time in a new version.

db

clarknova · Post by **clarknova** » Wed Jan 07, 2009 12:36 am

Just upgraded to 1.1.0-RC2 and again found the daemon listening on the wrong port, even though I have the correct port set in the preferences.

Post by **andar** » Wed Jan 07, 2009 8:36 am

Deluge will sometimes pick a random port if the selected port is not available. It could be that another program has binded the port for listening..

clarknova · Post by **clarknova** » Fri Jan 09, 2009 12:33 pm

andar wrote:Deluge will sometimes pick a random port if the selected port is not available. It could be that another program has binded the port for listening..

While that's true, it seems an unlikely coincidence that this would occur on something like 3 out of my last 4 upgrades. I could be wrong.

After I upgrade I usually restart the daemon thus:

Code: Select all

killall deluged && deluged

Is it possible the old daemon isn't releasing the port quickly enough for the new daemon to claim it?

yawie · Post by **yawie** » Fri Jan 09, 2009 2:03 pm

wouldn't it be a timeout on the open tcp connection on the system?
It seems to me that open connection cannot be released and reused immediately.

clarknova · Post by **clarknova** » Fri Jan 09, 2009 7:10 pm

yawie wrote:It seems to me that open connection cannot be released and reused immediately.

Perhaps, but then why doesn't it have a problem regrabbing the port when I do the same thing without upgrading? Does the system recognize the process asking for the same port and permit it, but doesn't recognize the process after an upgrade, and refuses to release the port to it?

laupan · Post by **laupan** » Sat Jan 10, 2009 12:54 am

Re: port preferences ignored on upgrade until daemon restarted

Postby clarknova on Wed Jan 07, 2009 12:36 am
Just upgraded to 1.1.0-RC2 and again found the daemon listening on the wrong port, even though I have the correct port set in the preferences.

My OS is XP, I have TCP-port forwarded for DHT but do we need to do the same for Daemon port as well? appreciate any advise on the matter, thanks.

Post by **johnnyg** » Sat Jan 10, 2009 3:22 am

laupan wrote:
Re: port preferences ignored on upgrade until daemon restarted

Postby clarknova on Wed Jan 07, 2009 12:36 am
Just upgraded to 1.1.0-RC2 and again found the daemon listening on the wrong port, even though I have the correct port set in the preferences.
My OS is XP, I have TCP-port forwarded for DHT but do we need to do the same for Daemon port as well? appreciate any advise on the matter, thanks.

you need to port forward the listening port (Preferences->Network->Active Port).
DHT uses UDP not TCP.
you don't need to port forward the daemon port.

clarknova · Post by **clarknova** » Thu Jan 15, 2009 3:58 am

I just upgraded to 1.1.0 on the ubuntu client and server and did not observe this behaviour, i.e., my port preference was observed.