Ubuntu 16 Server "page isn't working" (solved)

[rccypher]

So I installed Deluged via this guide:
http://dev.deluge-torrent.org/wiki/User ... ce/systemd

I was very careful to follow each step in the chain. I stopped at the section about only starting if mount exists as the disks I am using are internal.

I can start each service, however it fails almost immediately with exit code 1.

Code: Select all

MediaVault:/var/log$ systemctl status deluged.service
● deluged.service - Deluge Bittorrent Client Daemon
   Loaded: loaded (/etc/systemd/system/deluged.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Tue 2016-06-14 13:23:28 CDT; 7min ago
  Process: 5515 ExecStart=/usr/bin/deluged -d -l /var/log/deluge/daemon.log -L warning (code=exited, status=1/FAILURE)
 Main PID: 5515 (code=exited, status=1/FAILURE)

Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Unit entered failed state.
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Failed with result 'exit-code'.
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Service hold-off time over, scheduling restart.
Jun 14 13:23:28 MediaVault systemd[1]: Stopped Deluge Bittorrent Client Daemon.
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Start request repeated too quickly.
Jun 14 13:23:28 MediaVault systemd[1]: Failed to start Deluge Bittorrent Client Daemon.

Code: Select all

MediaVault:/var/log$ systemctl status deluge-web.service
● deluge-web.service - Deluge Bittorrent Client Web Interface
   Loaded: loaded (/etc/systemd/system/deluge-web.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Tue 2016-06-14 13:14:55 CDT; 16min ago
  Process: 5417 ExecStart=/usr/bin/deluge-web -l /var/log/deluve/web.log -L warning (code=exited, status=1/FAILURE)
 Main PID: 5417 (code=exited, status=1/FAILURE)

Jun 14 13:14:55 MediaVault systemd[1]: deluge-web.service: Unit entered failed state.
Jun 14 13:14:55 MediaVault systemd[1]: deluge-web.service: Failed with result 'exit-code'.
Jun 14 13:14:55 MediaVault systemd[1]: deluge-web.service: Service hold-off time over, scheduling restart.
Jun 14 13:14:55 MediaVault systemd[1]: Stopped Deluge Bittorrent Client Web Interface.
Jun 14 13:14:55 MediaVault systemd[1]: deluge-web.service: Start request repeated too quickly.
Jun 14 13:14:55 MediaVault systemd[1]: Failed to start Deluge Bittorrent Client Web Interface.
Warning: deluge-web.service changed on disk. Run 'systemctl daemon-reload' to reload units.

I enabled logging however the data in the log files is pretty meaningless to me:

Code: Select all

MediaVault:/var/log/deluge# cat daemon.log
[ERROR   ] 13:23:28 main:232 There is a deluge daemon running with this config directory!
[ERROR   ] 13:23:28 main:233 You cannot run multiple daemons with the same config directory set.
[ERROR   ] 13:23:28 main:234 If you believe this is an error, you can force a start by deleting /var/lib/deluge/.config/deluge/deluged.pid.

syslog doesn't give me any useful info:
Jun 14 13:23:27 MediaVault systemd[1]: deluged.service: Failed with result 'exit-code'.
Jun 14 13:23:27 MediaVault systemd[1]: deluged.service: Service hold-off time over, scheduling restart.
Jun 14 13:23:27 MediaVault systemd[1]: deluged.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 13:23:27 MediaVault systemd[1]: deluged.service: Unit entered failed state.
Jun 14 13:23:27 MediaVault systemd[1]: deluged.service: Failed with result 'exit-code'.
Jun 14 13:23:27 MediaVault systemd[1]: deluged.service: Service hold-off time over, scheduling restart.
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Unit entered failed state.
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Failed with result 'exit-code'.
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Service hold-off time over, scheduling restart.
Jun 14 13:23:28 MediaVault systemd[1]: deluged.service: Start request repeated too quickly.


Suggestions on where to look and what to look for.
At one point I had the services both running, but I was getting a connection refused from any browser I tried.

Thanks,
Cypher

[rccypher]

Ok, so I fixed the service crashing issues. I had a rogue deluge process running that I found with ps -A | grep deluge then killed with sudo kill -9 PID. Also I had a typo in the config file for the web-service.
So now both my services are running.

Code: Select all

MediaVault:/var/log$ systemctl status deluge-web.service
● deluge-web.service - Deluge Bittorrent Client Web Interface
   Loaded: loaded (/etc/systemd/system/deluge-web.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2016-06-14 13:44:25 CDT; 7min ago
 Main PID: 5724 (deluge-web)
    Tasks: 1
   Memory: 44.1M
      CPU: 662ms
   CGroup: /system.slice/deluge-web.service
           └─5724 /usr/bin/python /usr/bin/deluge-web -l /var/log/deluge/web.log -L warning

Jun 14 13:44:25 MediaVault systemd[1]: Started Deluge Bittorrent Client Web Interface.

Code: Select all

MediaVault:/var/log$ systemctl status deluged.service
● deluged.service - Deluge Bittorrent Client Daemon
   Loaded: loaded (/etc/systemd/system/deluged.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2016-06-14 13:40:37 CDT; 11min ago
 Main PID: 5614 (deluged)
    Tasks: 4
   Memory: 42.4M
      CPU: 2.689s
   CGroup: /system.slice/deluged.service
           └─5614 /usr/bin/python /usr/bin/deluged -d -l /var/log/deluge/daemon.log -L warning

Jun 14 13:40:37 MediaVault systemd[1]: Started Deluge Bittorrent Client Daemon.

However I still cannot access the web front end.
Here are my firewall rules:

Code: Select all

MediaVault:/var/log$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
22/tcp                     ALLOW       Anywhere
2049                       ALLOW       Anywhere
80                         ALLOW       Anywhere
443                        ALLOW       Anywhere
9092                       ALLOW       Anywhere
9091                       ALLOW       Anywhere
22/tcp (v6)                ALLOW       Anywhere (v6)
2049 (v6)                  ALLOW       Anywhere (v6)
80 (v6)                    ALLOW       Anywhere (v6)
443 (v6)                   ALLOW       Anywhere (v6)
9092 (v6)                  ALLOW       Anywhere (v6)
9091 (v6)                  ALLOW       Anywhere (v6)

[rccypher]

I just had this message pop up on me:

Code: Select all

[ERROR   ] 14:01:18 rpcserver:376 Couldn't listen on localhost:58846: [Errno 98] Address already in use.

[rccypher]

Ok so now if I try to connect to port <server IP>:58846 I receive: "Page isn't working" <IP> didn't send any data.

[rccypher]

I added the 58846 port to ufw. This has not changed anything but it does eliminate one more potential issue.

[Cas]

http://dev.deluge-torrent.org/wiki/User ... ient#WebUI

In your web browser, enter the url below where <server> is the IP address of the server:

http://<server>:8112

[rccypher]

*bangs head on desk* yep, that did it. TY for your help.