Network errors Linux/Mythtv backend

Help and support with third-party TV software.
Windows Media Center, J River Media Center, Next PVR, MythTV, InstaTV, etc.
Post Reply
llamont
Posts: 1
Joined: Tue Jul 02, 2019 8:25 am

Network errors Linux/Mythtv backend

Post by llamont » Thu Jul 04, 2019 3:06 pm

I don't know where to begin. Since 24JUN19 Every one of my recordings are being flagged as damaged. The files play back fine with the exception there are no commercial flags and because they are damaged. When I use hdhomerun_config to store a stream, I get thousands of network errors within 4-5 minutes of record time:

Code: Select all

- Video statistics --
670106 packets received, 0 overflow errors, 3878 network errors, 0 transport errors, 0 sequence errors
I have run speed tests and file system analysis on the NAS and all check OK. The SMART info indicates all four drives are working well.
When I test with hdhomerun_config from my Windows 10 machine, the results are clean with no errors.

Mythtv backend runs in a Linux Station container on a QNAP TS-453A, with 16GB RAM and about 7TB of available RAID 5 storage.
This arrangement has been working for at least 3 years with no trouble at all. The only changes have been updates/upgrades as they have been released. We record everything except sports that we want to see live. I'm using OSMC on a pi3 for a front end. All the interesting network connections are over an Ethernet gigabit LAN. My tuners are HDHomeruns, one Prime and one Duo.
  • Prime Firmware Version 20190621
    Duo Firmware: 20170930
    Other versions:
    My versions are:
    "Linux Station" Data:
    Linux hms-server2 4.14.24-qnap #1 SMP Wed Jun 26 09:57:22 CST 2019 x86_64 x86_64 x86_64 GNU/Linux
    Description: Ubuntu 16.04.6 LTS
    MythTV Version : v29.1
    Network Protocol : 91
    Library API : 29.20180316-1
    QT Version : 5.5.1
    QNAP Firmware: 4.4.1.0978
Any Ideas would be most appreciated.

jasonl
Silicondust
Posts: 13777
Joined: Sun Oct 28, 2007 9:23 pm

Re: Network errors Linux/Mythtv backend

Post by jasonl » Mon Jul 08, 2019 12:06 pm

Network packet loss would point to either a hardware issue like a bad cable or switch or insufficient network buffer on the NAS (it's not processing incoming data quickly enough and some is getting lost as a result).

What is the output of:

Code: Select all

sysctl net.core.rmem_max

Post Reply