Transmission disconnections on OSMC

#1

I’ve got the Vero 4k.

I have transmission enabled and it’s been working well. Today however, I can’t seem to connect to the transmission service (neither on the phone app or the web interface) like I usually do. Internet access is avaiable, and I’m able to connect to OSMC using the mobile app (Kore), so I think it’s an OSMC-transmission issue. I tried restarting the service via:

sudo systemctl stop transmission; sudo systemctl start transmission

The first time I ran the command, the web interface/mobile app was able to connect for only a minute, and then it disconnected again. Subsequent restarts failed to even connect again. Can anyone help? Thanks.

#2

When it fails, what’s systemctl status transmission say?

#3
  • transmission.service - Transmission BitTorrent Daemon
    Loaded: loaded (/lib/systemd/system/transmission.service; enabled; vendor preset: enabled)
    Active: active (running) since Tue 2019-10-08 18:39:58 +03; 6min ago
    Process: 27789 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
    Main PID: 27790 (transmission-da)
    Status: “Idle.”
    CGroup: /system.slice/transmission.service
    `-27790 /usr/bin/transmission-daemon -f --log-error --allowed ...

Oct 08 18:39:48 osmc systemd[1]: Starting Transmission BitTorrent Daemon…
Oct 08 18:39:58 osmc systemd[1]: Started Transmission BitTorrent Daemon.
Oct 08 18:39:59 osmc transmission-daemon[27790]: [2019-10-08 18:39:59.623] Couldn’t bind port 51413 on 0.0.0.0: Address already in use (Is another copy of Transmission already running?) (net.c:380)
Oct 08 18:39:59 osmc transmission-daemon[27790]: [2019-10-08 18:39:59.623] Couldn’t bind port 51413 on ::: Address already in use (Is another copy of Transmission already running?) (net.c:380)
Oct 08 18:39:59 osmc transmission-daemon[27790]: [2019-10-08 18:39:59.623] UDP Couldn’t bind IPv4 socket (tr-udp.c:271)
Oct 08 18:41:48 osmc transmission-daemon[27790]: [2019-10-08 18:41:48.623] RPC Server Unable to bind to 0.0.0.0:9091 after 10 attempts, giving up (rpc-server.c:846)

#4

I don’t understand why it would think another instance of transmission would be running, I haven’t done anything new to my setup so this just happened out of the blue.

#5

Now it’s going from worse to worst. I checked for updates for OSMC and it needed to restart. It did the update and whilst getting ready to reboot, it failed to unmount my HDD. Now, it’s stuck showing the following for a while:

"Remounting /hdd/directory' read-only with options 'data=ordered'. "

I really do not want to force reboot this so I don’t do any damage on the HDD. This is really frustrating.

#6

If it has remounted read only then I’m not sure what “damage” you suspect could possibly happen?

#7

It’s stuck on that command. I actually didn’t have it mounted read-only, it initially tried to unmount and then failed. Afterwards, it said it was sending sigterm to remaining processes, then “unmounting file systems” which then showed the above “remounting” command which is weird.

#8

Here’s exactly what it shows. I fear there will be data-loss and/or damage if I force turn off the device. It’s been stuck on this command for a long time now. This is some poor fault tolerance from this system :|.

#10

You have no option. Just restart. Provide logs to further seek some issue in your system.