Jump to content

Buffering/Playback issues


Recommended Posts

Posted
On 5/21/2024 at 2:32 PM, MXYetvzxd4jkc said:

@LessajSorry for the long delay, this device is Wifi, its not an ideal connection, but thats a pretty wild swing. I can try get some logs on a wired client also!

Hi, that would be great. Thanks.

Lessaj
Posted

I'm not sure why Emby Theater wouldn't be able to play anything but I can see a similar trend of good response times for the TS segments and then not only are the times really high but they're actually 500 responses, it seems like the server isn't even able to get the segments to respond to the client. What folder do you have configured for transcoding-temp?

Also I have no experience with running the server with docker but at the top of the log file when it's trying to figure out the local network addresses there are a lot more than I would expect to see for a docker container. Is that correct, or were you running it directly within the Ubuntu environment? I don't think it's necessarily related but it struck me as odd.

Quote

2024-05-24 07:18:53.517 Info Server: http/1.1 Response 200 to host1. Time: 423ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/0.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:18:53.817 Info Server: http/1.1 Response 200 to host1. Time: 181ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/1.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:18:54.138 Info Server: http/1.1 Response 200 to host1. Time: 215ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/2.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:18:54.368 Info Server: http/1.1 Response 200 to host1. Time: 111ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/3.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:18:54.458 Info Server: http/1.1 Response 200 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/4.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:18:54.471 Info Server: http/1.1 Response 200 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/5.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:18:59.639 Info Server: http/1.1 Response 200 to host1. Time: 17ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/6.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:05.698 Info Server: http/1.1 Response 200 to host1. Time: 49ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/7.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:11.831 Info Server: http/1.1 Response 200 to host1. Time: 116ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/8.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:17.783 Info Server: http/1.1 Response 200 to host1. Time: 153ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/9.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:23.677 Info Server: http/1.1 Response 200 to host1. Time: 6ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/10.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:29.731 Info Server: http/1.1 Response 200 to host1. Time: 3ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/11.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:35.664 Info Server: http/1.1 Response 200 to host1. Time: 3ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/12.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:41.612 Info Server: http/1.1 Response 200 to host1. Time: 3ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/13.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:47.634 Info Server: http/1.1 Response 200 to host1. Time: 4ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/14.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:53.779 Info Server: http/1.1 Response 200 to host1. Time: 113ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/15.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:19:59.895 Info Server: http/1.1 Response 200 to host1. Time: 221ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/16.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:05.847 Info Server: http/1.1 Response 200 to host1. Time: 224ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/17.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:11.898 Info Server: http/1.1 Response 200 to host1. Time: 219ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/18.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:17.837 Info Server: http/1.1 Response 200 to host1. Time: 207ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/19.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:23.901 Info Server: http/1.1 Response 200 to host1. Time: 227ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/20.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:24.088 Info Server: http/1.1 Response 304 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/19.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:24.298 Info Server: http/1.1 Response 304 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/19.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:24.401 Info Server: http/1.1 Response 304 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/19.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:24.505 Info Server: http/1.1 Response 304 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/19.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:34.950 Info Server: http/1.1 Response 304 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/19.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:35.089 Info Server: http/1.1 Response 304 to host1. Time: 0ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/20.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:41.095 Info Server: http/1.1 Response 200 to host1. Time: 214ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/21.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:50.297 Info Server: http/1.1 Response 304 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/20.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:20:50.447 Info Server: http/1.1 Response 304 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/21.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:21:16.653 Info Server: http/1.1 Response 200 to host1. Time: 20386ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/22.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:21:48.000 Info Server: http/1.1 Response 200 to host1. Time: 31218ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/23.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:21:48.342 Info Server: http/1.1 Response 200 to host1. Time: 195ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/24.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:22:42.118 Info Server: http/1.1 Response 304 to host1. Time: 1ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/24.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:22:50.460 Info Server: http/1.1 Response 500 to host1. Time: 39668ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/25.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:22:50.460 Info Server: http/1.1 Response 500 to host1. Time: 29664ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/25.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:22:50.460 Info Server: http/1.1 Response 500 to host1. Time: 49673ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/25.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:22:50.460 Info Server: http/1.1 Response 500 to host1. Time: 59678ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/25.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:22:50.460 Info Server: http/1.1 Response 500 to host1. Time: 18351ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/25.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:23:21.207 Info Server: http/1.1 Response 200 to host1. Time: 38925ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/25.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:23:21.511 Info Server: http/1.1 Response 200 to host1. Time: 195ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/26.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:24:23.410 Info Server: http/1.1 Response 200 to host1. Time: 59295ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/27.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:24:23.758 Info Server: http/1.1 Response 200 to host1. Time: 214ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/28.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:24:26.557 Info Server: http/1.1 Response 200 to host1. Time: 215ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/29.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97
2024-05-24 07:24:32.535 Info Server: http/1.1 Response 200 to host1. Time: 220ms. GET http://192.168.3.100:8096/emby/videos/651/hls1/main/30.ts?PlaySessionId=29382075a6c14bb3b3b0f473e3f29a97

Quote

2024-05-24 07:17:13.786 Info NetworkManager: Detecting local network addresses
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet eno1, Speed: 1000000000, Description: eno1
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 192.168.2.1
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 192.168.2.100,fe80::127c:61ff:fe23:485d%2
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet enp8s0f0, Speed: 1000000000, Description: enp8s0f0
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 192.168.3.1
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 192.168.3.100,fdb3:5a89:a896:d24a:a236:9fff:fe4d:abc6,fe80::a236:9fff:fe4d:abc6%4
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet enp8s0f1, Speed: 1000000000, Description: enp8s0f1
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: fdb3:5a89:a896:d24a:a236:9fff:fe4d:abc7,fe80::a236:9fff:fe4d:abc7%5
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet macvtap0, Speed: 1000000000, Description: macvtap0
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: fe80::5054:ff:fe4a:4fdb%7
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet docker0, Speed: 10000000000, Description: docker0
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 172.17.0.1,fe80::42:71ff:fe10:d971%8
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet br-870e9ab28a87, Speed: 10000000000, Description: br-870e9ab28a87
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 172.25.0.1,fe80::42:6eff:fede:e275%9
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet br-a377828666b6, Speed: 10000000000, Description: br-a377828666b6
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 172.19.0.1,fe80::42:f2ff:fe7b:9e20%10
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet br-bc192de7876a, Speed: 10000000000, Description: br-bc192de7876a
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 172.20.0.1,fe80::42:e5ff:fe1d:fed4%11
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet br-ff32d66055c2, Speed: 10000000000, Description: br-ff32d66055c2
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 192.168.192.1,fe80::42:5aff:fec2:a09d%12
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet br-05ac89cd10c3, Speed: 10000000000, Description: br-05ac89cd10c3
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 172.21.0.1,fe80::42:d2ff:feff:5425%13
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet br-6148f888b56b, Speed: 10000000000, Description: br-6148f888b56b
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 172.23.0.1,fe80::42:22ff:fe3c:35b7%14
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet br-6d731be0938a, Speed: 10000000000, Description: br-6d731be0938a
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: 172.24.0.1,fe80::42:ccff:febd:f7fb%15
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet veth2593f27, Speed: 10000000000, Description: veth2593f27
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: fe80::7835:d8ff:fe2a:78b3%17
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet veth1b0e675, Speed: 10000000000, Description: veth1b0e675
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: fe80::84c8:7fff:fe82:8866%19
2024-05-24 07:17:13.786 Info NetworkManager: networkInterface: Ethernet veth5013911, Speed: 10000000000, Description: veth5013911
2024-05-24 07:17:13.786 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.786 Info NetworkManager: UnicastAddresses: fe80::bc9b:72ff:fe18:fe1%27
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Ethernet vethde813fc, Speed: 10000000000, Description: vethde813fc
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: fe80::f0de:bdff:fe64:1c84%29
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Ethernet vethce505c5, Speed: 10000000000, Description: vethce505c5
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: fe80::908e:c6ff:fee4:bd2b%127
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Ethernet vetha67e4bb, Speed: 10000000000, Description: vetha67e4bb
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: fe80::1823:4cff:feae:9c6b%129
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Ethernet vethb3351b1, Speed: 10000000000, Description: vethb3351b1
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: fe80::bcbf:1fff:fea0:12a3%131
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Ethernet vethfc5c7a0, Speed: 10000000000, Description: vethfc5c7a0
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: fe80::3c1a:74ff:fe4f:4fb%135
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Ethernet vethfb848fb, Speed: 10000000000, Description: vethfb848fb
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: fe80::68:60ff:fe18:afdd%151
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Ethernet veth1e46490, Speed: 10000000000, Description: veth1e46490
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: fe80::e8ad:14ff:fed5:d83a%153
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Ethernet veth59ac8e1, Speed: 10000000000, Description: veth59ac8e1
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: fe80::f8b0:95ff:fea2:8340%165
2024-05-24 07:17:13.787 Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo
2024-05-24 07:17:13.787 Info NetworkManager: GatewayAddresses: 
2024-05-24 07:17:13.787 Info NetworkManager: UnicastAddresses: 127.0.0.1,::1
2024-05-24 07:17:13.804 Info NetworkManager: Detected local ip addresses: [{"IPAddress":"192.168.2.100","HasGateWayAddress":true,"PrefixLength":24,"IPv4Mask":"255.255.255.0"},{"IPAddress":"192.168.3.100","HasGateWayAddress":true,"PrefixLength":24,"IPv4Mask":"255.255.255.0"},{"IPAddress":"fe80::127c:61ff:fe23:485d%2","HasGateWayAddress":true,"PrefixLength":64},{"IPAddress":"fdb3:5a89:a896:d24a:a236:9fff:fe4d:abc6","HasGateWayAddress":true,"PrefixLength":64},{"IPAddress":"fe80::a236:9fff:fe4d:abc6%4","HasGateWayAddress":true,"PrefixLength":64},{"IPAddress":"172.17.0.1","HasGateWayAddress":false,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"172.25.0.1","HasGateWayAddress":false,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"172.19.0.1","HasGateWayAddress":false,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"172.20.0.1","HasGateWayAddress":false,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"192.168.192.1","HasGateWayAddress":false,"PrefixLength":20,"IPv4Mask":"255.255.240.0"},{"IPAddress":"172.21.0.1","HasGateWayAddress":false,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"172.23.0.1","HasGateWayAddress":false,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"172.24.0.1","HasGateWayAddress":false,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"},{"IPAddress":"fdb3:5a89:a896:d24a:a236:9fff:fe4d:abc7","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::a236:9fff:fe4d:abc7%5","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::5054:ff:fe4a:4fdb%7","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::42:71ff:fe10:d971%8","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::42:6eff:fede:e275%9","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::42:f2ff:fe7b:9e20%10","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::42:e5ff:fe1d:fed4%11","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::42:5aff:fec2:a09d%12","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::42:d2ff:feff:5425%13","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::42:22ff:fe3c:35b7%14","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::42:ccff:febd:f7fb%15","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::7835:d8ff:fe2a:78b3%17","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::84c8:7fff:fe82:8866%19","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::bc9b:72ff:fe18:fe1%27","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::f0de:bdff:fe64:1c84%29","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::908e:c6ff:fee4:bd2b%127","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::1823:4cff:feae:9c6b%129","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::bcbf:1fff:fea0:12a3%131","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::3c1a:74ff:fe4f:4fb%135","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::68:60ff:fe18:afdd%151","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::e8ad:14ff:fed5:d83a%153","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"fe80::f8b0:95ff:fea2:8340%165","HasGateWayAddress":false,"PrefixLength":64},{"IPAddress":"::1","HasGateWayAddress":false,"PrefixLength":128}]

 

MXYetvzxd4jkc
Posted

@LessajThanks again for all the speedy responses, you rock! I left transcoding temp blank, but the filesystem its assigned in docker is on an SSD. I also tried this outside of docker and ran emby native, had the same issue. You are correct that currently its in docker on Ubuntu Sever 24.04.

That is an oddly high number of addresses, im not really sure why its getting so many local Ipv6 addresses, that is indeed weird. Let me see what I can do to fix that, if its even fixable!

Lessaj
Posted

Oh yes I see it in the log it's /config/transcoding-temp. So this is backed by the BTRFS raid 1 array? Any particular reason to be using BTRFS here? I haven't used it in a number of years so I'm not sure the performance implications of it, my understanding is it's not particularly well recommended but I think that's mostly around raid 5.

MXYetvzxd4jkc
Posted

@LessajNot any particular reason, I'm actually upgrading my storage array, this is a smaller SSD array. So I will copy everything off onto the larger MergerFS + snapraid config and move away from BTRFS and back to ext4 raid1. This will probably take 2-3 weeks (I hope!!). But I will report back once its done and moved, and I can see if that improves things.

Lessaj
Posted

2-3 weeks to move a couple TB doesn't seem right. :P But yes I am wondering about the underlying storage because I've seen through my own use cases where I was hammering both my HDD (reading) and SSD (writing) arrays to remux media that when the SSD array would slow down under very heavy writes, which I can see crawling well under 100 MB/s in those conditions with 4 drives in raid 0, that response times of TS files also being read/written to that array would increase by 1-2 seconds, but nowhere near what you're seeing under what I would assume are essentially otherwise idle conditions. I'm using ZFS for both of my arrays and I would have been running up to 10-15 mkvmerge commands at the same time when I noted the increase in response times for the TS segments being delivered. TS segments are generally pretty small, maybe a few MB at most unless it's a 4K remux transcode, in which case I've seen those go up to 50 or 60 MB but in the grand scheme that's still really small, especially for a local client at gigabit speeds that's 0.5 sec to transfer. Your hardware is more than capable of what you're asking it to do, just need to find out what the bottleneck is.

I'm still perplexed that Theater wouldn't play anything but honestly direct play is a little harder to figure out since you can't see the response time of chunks, you either need to be looking at the buffers with netstat, reviewing traffic graphs, or packet captures to understand the behaviour.

Neminem
Posted

I use a single scrap SSD drive for transcoding.

If you have a scrap drive laying around, then put transcode temp on that, and see if it's better.

MXYetvzxd4jkc
Posted

@LessajMy apologies, I have to wait for some hardware, then have to wait for life to get out of the way :) Indeed, the SSD array should be perfectly fine to deal with the load! Hopefully the transfer over to ext4 will make the errors go away. I thought about ZFS, but to be honest, I'm not particularly worried about losing data, as I don't store anything on here that isn't backed up offsite, so was just going to use mergerfs and keep things fairly simple.

The theater error is actually new, it has worked in the past! Our of curiosity, I just tried now and it seems to work again. So no idea why it would just refuse (I even restarted to be sure last time!)

@jaycedkI can give that a whirl once my new hardware arrives! :)

Lessaj
Posted

Not too familiar with mergerfs either... In the past I just used mdadm to create an array and I think I was using XFS on top since that's what RHEL uses by default and it has good performance. I mostly went with ZFS for the extended capabilities, IE datasets with different recordsizes, snapshots, things like that. I backup the array to another ZFS array so being able to send/receive in the event that I need to restore the array is WAY more efficient than trying to use something like rsync, especially when you have lots of little files, since it's block level copies. At the end of the day, use whatever you're familiar with using and try to test the performance with a tool like fio, rand read and write are probably the hardest things to do.

My SSD array is essentially a big scratch drive. I used to use a single NVME but I reconfigured my hypervisor from 2x SATA in raid 1 to 2x NVME in raid 1 and the motherboard only has 2 NVME slots on it so I didn't have the free slot to give to my VM anymore. It's probably not necessary but I tried to build the server to be redundant where I could if a drive failed.

MXYetvzxd4jkc
Posted

@LessajMy OS is on an mdadm array also, so im more familiar with that than BTRFS, just thought id give it a try to see what its like, seems maybe that was a mistake 😂 ZFS is pretty badass, I just don't have a need for the overhead. I think if I was more serious about my data id use it. Indeed, whatever you are familiar with and fits your needs, its all good! 

Ahh yeah, I use raid1 a lot with smaller/cheaper SSD drives, fairly handy!!

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...