Inactivity timeout (--ping-restart), restarting - happening when not running Transmission as root

[tasirith]

Hey guys,

My container stopped working around a week ago, haven't changed anything with the container but may have coincided with a system wide update so not sure. Running latest version on a raspberry pi (diet-pi), hooking up to PIA.

What was happening is it appears to load 90% of the way fine, then just before it looks like it was to finish, exits due to a ping timeout error - "Inactivity timeout (--ping-restart), restarting".

STARTING TRANSMISSION
Provider PIA has a script for automatic port forwarding. Will run it now.
If you want to disable this, set environment variable DISABLE_PORT_UPDATER=true
Transmission startup script complete.
2023-09-08 22:53:33 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2023-09-08 22:53:33 Initialization Sequence Completed
2023-09-08 22:53:33 [melbourne430] Inactivity timeout (--ping-restart), restarting
2023-09-08 22:53:33 /etc/openvpn/tunnelDown.sh tun0 1500 1553 10.25.112.99 255.255.255.0 init
resolv.conf was restored
Sending kill signal to transmission-daemon
Terminated
Successfuly closed transmission-daemon
2023-09-08 22:53:34 net_route_v4_del: 154.6.151.94/32 via 172.17.0.1 dev [NULL] table 0 metric -1
2023-09-08 22:53:34 net_route_v4_del: 0.0.0.0/1 via 10.25.112.1 dev [NULL] table 0 metric -1
2023-09-08 22:53:34 net_route_v4_del: 128.0.0.0/1 via 10.25.112.1 dev [NULL] table 0 metric -1
2023-09-08 22:53:34 Closing TUN/TAP interface
2023-09-08 22:53:34 net_addr_v4_del: 10.25.112.99 dev tun0
2023-09-08 22:53:34 SIGTERM[soft,ping-restart] received, process exiting

Tried all sorts of things to try and fix the issue with my existing config (longer ping times, change of servers, new ovpn files, different openvpn configs) but nothing would work. Eventually spun up another fresh container and it worked straight away.

Tracked down the difference to if transmission is either run as root (uid:0, gid:0) vs a standard user (uid:1000, gid:1000). Seems to run fine as root and not sure if it matters if it does, but anyone hazard a guess as to why this config stopped working and any solutions ?

edit: this temporary fix also seems to fix the issue - #2532
seems to be related to the timing out due to how long it takes to apply owner and permissions to all the files, which does take quite a while on my system - NFS network mount. Takes no time at all when running as root.

second edit: So think I may have found the problem. Had a folder on the network share that had thousands of little files. Setting permissions on those files was causing it to take ages to complete, and led to the timeout error. Was going to delete this question but will leave it here for others in case they run into the same issue.

thanks
T

[pkishino]

Thanks for the update