autoconnect to daemon on restart - raspbian

General support for problems installing or using Deluge
Post Reply
FabioPG
New User
New User
Posts: 5
Joined: Wed Oct 25, 2017 8:17 am

autoconnect to daemon on restart - raspbian

Post by FabioPG »

hello

I've replaced transmission with deluge on my raspbian raspberry pi 1 hardware.
what I do want (and actually can't get) is that when my raspberry reboots deluge will autoconnect to the deamon (127.0.0.1:58846) .

I've changed the web.conf file and the web.conf~ file too and set them with 444 permission but after a reboot if I connect to the localhost:8112 the deamon isn't started and I still have to start it manually and then connect to it.

can you please help me ? thanks!
sinaptika
Member
Member
Posts: 41
Joined: Thu Apr 27, 2017 6:23 pm

Re: autoconnect to daemon on restart - raspbian

Post by sinaptika »

What are you trying to do exactly?
Automatically connect the web interface to a running delug-daemon (deluged)?
or
Automatically start deluged on reboot?
FabioPG
New User
New User
Posts: 5
Joined: Wed Oct 25, 2017 8:17 am

Re: autoconnect to daemon on restart - raspbian

Post by FabioPG »

I made deluge automatically restart on reboot but if I connect to http://ipadreess:8112 the web interface isn't connected to the daemon and it tells me that the daemon is not running.

I want to do change it to way that when the raspberry reboot it automatically start deluged (done) and when I connect to the web interface it will be already automatically connected to the started daemon
shamael
Compulsive Poster
Compulsive Poster
Posts: 667
Joined: Sat Oct 08, 2016 9:28 am

Re: autoconnect to daemon on restart - raspbian

Post by shamael »

Is deluged and deluge-web services started at boot?
The wiki describes both systemd services to setup
sinaptika
Member
Member
Posts: 41
Joined: Thu Apr 27, 2017 6:23 pm

Re: autoconnect to daemon on restart - raspbian

Post by sinaptika »

Fabio I still have no clue what you want.
Also why are you changing permissions on web.conf? Why did you run chmod 444 on web.conf?

Anyway and this is just a guess, based on your so far:
I think you want your web interface (deluge-web) to automatically connect to a running deluge daemon (deluged) running on the same raspberry pi.
Right?

If so, here is the quote from deluge faq:
Stop the Web UI before modifying the web.conf file.
Edit web.conf in config, find "default_daemon" and set its value to the daemon id in hostlist.conf
e.g. To connect to localhost you would open hostlist.conf as see a snippet such as:

...
"123459d5a5b414159caa1323f6e0c9b240c7abcd",
"localhost",
58846,
...

Use the first entry from hostlist, which is the id and add it to web.conf:

"default_daemon": "123459d5a5b414159caa1323f6e0c9b240c7abcd",

Restart the Web UI.
And link to the faq:
http://dev.deluge-torrent.org/wiki/Faq# ... ificdaemon
FabioPG
New User
New User
Posts: 5
Joined: Wed Oct 25, 2017 8:17 am

Re: autoconnect to daemon on restart - raspbian

Post by FabioPG »

sinaptika I did what you wrote but on every reboot the web.conf returnet to the previous state without the default_daemon set like I did.
I looked for this on Google and I found that the solution was to change both file and to set the permissions to web.conf to 444.
the file after the reboot wasn't changed but if I connect to the web interface it keep says me that it is not connected to the daemon

shamael I think they both start at reboot but how to check to be sure?
shamael
Compulsive Poster
Compulsive Poster
Posts: 667
Joined: Sat Oct 08, 2016 9:28 am

Re: autoconnect to daemon on restart - raspbian

Post by shamael »

to check both services: sudo systemctl status delug*

And prior changing anything in the web.conf I personaly stop the deluge-web service but maybe not necessary I agree.
FabioPG
New User
New User
Posts: 5
Joined: Wed Oct 25, 2017 8:17 am

Re: autoconnect to daemon on restart - raspbian

Post by FabioPG »

here's the result

pi@raspytorrent:~ $ sudo systemctl status delug*
● deluged.service - LSB: Start or stop the Deluge BitTorrent daemon.
Loaded: loaded (/etc/init.d/deluged; generated; vendor preset: enabled)
Active: active (exited) since Tue 2017-10-31 09:17:30 CET; 4 days ago
Docs: man:systemd-sysv-generator(8)
CGroup: /system.slice/deluged.service

Oct 31 09:17:28 raspytorrent systemd[1]: Starting LSB: Start or stop the Deluge
Oct 31 09:17:30 raspytorrent deluged[407]: Starting Deluge BitTorrent Daemon: de
Oct 31 09:17:30 raspytorrent systemd[1]: Started LSB: Start or stop the Deluge B

and right after a reboot

pi@raspytorrent:~ $ sudo systemctl status delug*
● deluged.service - LSB: Start or stop the Deluge BitTorrent daemon.
Loaded: loaded (/etc/init.d/deluged; generated; vendor preset: enabled)
Active: active (exited) since Sat 2017-11-04 11:14:29 CET; 1min 22s ago
Docs: man:systemd-sysv-generator(8)
Process: 398 ExecStart=/etc/init.d/deluged start (code=exited, status=0/SUCCES
CGroup: /system.slice/deluged.service

Nov 04 11:14:27 raspytorrent systemd[1]: Starting LSB: Start or stop the Deluge
Nov 04 11:14:28 raspytorrent deluged[398]: Starting Deluge BitTorrent Daemon: de
Nov 04 11:14:29 raspytorrent systemd[1]: Started LSB: Start or stop the Deluge B
FabioPG
New User
New User
Posts: 5
Joined: Wed Oct 25, 2017 8:17 am

Re: autoconnect to daemon on restart - raspbian

Post by FabioPG »

nothing?
shamael
Compulsive Poster
Compulsive Poster
Posts: 667
Joined: Sat Oct 08, 2016 9:28 am

Re: autoconnect to daemon on restart - raspbian

Post by shamael »

You still use the init.d path?
http://dev.deluge-torrent.org/wiki/User ... ce/systemd

I don't see the deluge-web service running, only deluged in your output
Post Reply