Page 1 of 1

FreeBSD daemon Win Thin Client not Seeing

Posted: Fri Dec 02, 2011 12:05 am
by MasterCATZ
Unsure what is going on here

Code: Select all

echo "username:password:level" >> ~/.config/deluge/auth
echo "bob:letMEin:10" >> ~/.config/deluge/auth

deluged -u console 
config -s allow_remote True
config allow_remote

deluged ( no webui access or thinclient access )

deluge-web
I can use the webui


The deluge connection manager running on windows is just not seeing the deluged daemon running on FreeBSD
the same if I try and use Windows webui connection manager to see if it can find the FreeBSD webui
( tried IP address internal / external and machine name )

or is their some FreeBSD firewall option I am over looking ?

*edit* ok I solved it

Code: Select all

deluged -d 
showed that somehow

Code: Select all

FreeBSD# pkill deluged
FreeBSD# pkill deluge
did not kill the process so it was never actually starting a new daemon

Code: Select all

FreeBSD# deluged -d
[ERROR   ] 10:27:48 main:221 There is a deluge daemon running with this config directory!
[ERROR   ] 10:27:48 main:222 You cannot run multiple daemons with the same config directory set.
[ERROR   ] 10:27:48 main:223 If you believe this is an error, you can force a start by deleting /root/.config/deluge/deluged.pid.

FreeBSD# rm /root/.config/deluge/deluged.pid
FreeBSD# deluged -d
[ERROR   ] 10:28:17 init:50 Unable to enable plugin!
[ERROR   ] 10:28:17 init:51 string indices must be integers
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/deluge-1.3.3-py2.7.egg/deluge/plugins/init.py", line 48, in enable
    self.plugin.enable()
  File "build/bdist.freebsd-9.0-RC2-amd64/egg/autoadd/core.py", line 108, in enable
    if os.path.abspath(self.core_cfg['autoadd_location']) == watchdir['abspath']:
TypeError: string indices must be integers

Re: FreeBSD daemon Win Thin Client not Seeing

Posted: Fri Dec 02, 2011 10:48 am
by Cas
I am unsure what you are asking, is this question resolved?

Re: FreeBSD daemon Win Thin Client not Seeing

Posted: Sun Dec 11, 2011 10:41 am
by MasterCATZ
yes that particular problem is solved it was just because deluged was actually still running

but now discovered another , similar issue again

I run deluged as root on boot

my windows pc with its thin client and webgui will connect to it just fine , also if i start kde4 up as the root user the thin client works on the host pc

how ever I just discovered if I start the thin client up logged in as another user it does not seem to see any daemons running
( and will want to start another one instead )
also the webgui failed to let me in saying invalid password ( does not request a username )

any idea's on this ??

the user is in the wheel group running FreeBSD 9

*edit*

solved it in around about way

~/.config/deluge/auth

I replaced it with roots file then it would connect to the local daemon

it seems this was different

what the new user ran as
localclient:b7ff9461627a574d5cae2f78ad254a92f9494638:10

what root runs as
localclient:04583057b1d0e5478e5db175591da85c4cd2ee97:10