Kernel version | Linux DietPi 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
SBC model | RPi4 Model B
Power supply used | 5V 1A
SD card used | (EG: SanDisk ultra)
Additional Information (if applicable)
Software title | Transmission
Was the software title installed freshly or updated/migrated? Freshly installed
Can this issue be replicated on a fresh installation of DietPi? I dont know
ā If you sent a ādietpi-bugreportā, please paste the ID here ā
Bug report ID | echo $G_HW_UUID
Steps to reproduce
I belive I upgraded some days ago with no other problems, but since I rebooted the pi, the service transmission-daemon wont start.
Expected behaviour
Service runing as before
Actual behaviour
sytemctl status give me a timeout error, If I try to restart the service it causes a loop, with no results, I can see it under HTOP but it wont stop.
I tried killing transmission-daemon and starting it with:
sudo -u debian-transmission /usr/bin/transmission -f --log-debug whitout succes, it freezes, even cant use Ctrl+c to stop it
Thanks, for the quick response.
Sorry for the silly question, i have torrents in multiple paths, in the settings json I can see my default download folder specificied. If I keep only the json (and source material ofc) Would remember transmission all the torrents?
Ok, I am an idiot, didnt saw that two procces was holding the user from deleting. Used another ssh to kill both proccess it with sudo kill -9 $PID and retried the script, which worked instantly.
Installed again and now I am restoring the backed up torrent files.
Everything looks like is works fine.
After almost a week of working whitout problems, I have the same error again, I can restore like the previous time, but I would love to find the root problem and reverse it once for all.
What can I do to find more info about what is causing this?
I think one of the drivers is failing (running checks atm, i ll edit to add this info) but I dont belive that this is the problem, at those drives there are only the data of the torrents.
Feb 28 14:10:52 DietPi systemd[1]: Starting Transmission BitTorrent Daemon...
Feb 28 14:12:22 DietPi systemd[1]: transmission-daemon.service: start operation timed out. Terminating.
Feb 28 14:13:52 DietPi systemd[1]: transmission-daemon.service: State 'stop-sigterm' timed out. Killing.
Feb 28 14:13:52 DietPi systemd[1]: transmission-daemon.service: Killing process 1279 (transmission-da) with signal SIGKILL.
Feb 28 14:13:52 DietPi systemd[1]: transmission-daemon.service: Killing process 1349 (transmission-da) with signal SIGKILL.
Feb 28 14:13:52 DietPi systemd[1]: transmission-daemon.service: Main process exited, code=killed, status=9/KILL
Feb 28 14:13:52 DietPi systemd[1]: transmission-daemon.service: Failed with result 'timeout'.
Feb 28 14:13:52 DietPi systemd[1]: Failed to start Transmission BitTorrent Daemon.
Maybe you can see further than me, I am a total noob looking at logs
Thanks a lot @Jappe and @Joulinar , I checked dmesg (didnt used it, will read manpage for further checks, thanks a lot)
The output is these lines reapeated times:
[ 227.078151] usb usb2-port1: unable to enumerate USB device
[ 231.157574] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Could be the faulting device the problem? Usually this didnt break transmission, only torrents on those devicesā¦
I dont know why, but using same ports on the pi, but in opposite order, it works⦠Never saw transmission stop because drives failed, nice āalertā, buying some new ssd to replace the old hdd.
Thanks again, looks like it is working whitout problems.