{"id":4745,"date":"2021-04-10T14:21:43","date_gmt":"2021-04-10T02:21:43","guid":{"rendered":"https:\/\/www.zoyinc.com\/?p=4745"},"modified":"2024-01-04T19:30:50","modified_gmt":"2024-01-04T06:30:50","slug":"mythtv-add-on-for-kodi-hangs-at-0","status":"publish","type":"post","link":"http:\/\/www.zoyinc.com\/?p=4745","title":{"rendered":"MythTV add-on for Kodi hangs at 0%"},"content":{"rendered":"\n

Around about the 26\/3\/2021 the Windows 10 MythTV add-on for Kodi stopped working. I had seen similar problem before, Kodi MythTV addon fails to load<\/a> except this time it didn’t load at all whereas previously it was stuck loading at around 40%.<\/p>\n\n\n\n

This time around it didn’t seem to connect to the MythTV server at all. When I tried to look at recordings, channels or recordings it just showed “PVR manager is starting up: 0%” with the spinning wheel to the right. It didn’t matter how long you waited it didn’t change.<\/p>\n\n\n\n

Looking in the Kodi log, with extra add-on debugging, there was no indication of what was wrong.<\/p>\n\n\n\n

This whole time MythTV server worked fine. It recorded programs fine, I could watch recordings from MythWeb. I could connect fine from Kodi on my Android phone, I could even run Myth front end, from the MythTV server, without any problems.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

My MythTV setup<\/h1>\n\n\n\n

My setup is described in MythTV on CentOS 7<\/a> with the infrastructure looking like:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Problem dates<\/h1>\n\n\n\n

24\/10\/2022<\/p>\n\n\n\n

First noticed when Shortland street latest episodes were missing. Did a restart and then MythTV didn’t even connect or at least TV didn’t show<\/p>\n\n\n\n

25\/03\/2022<\/p>\n\n\n\n

First noticed issues in the evening. I know it wasn’t a problem the night before. I did a restart of the backend MythTV server and the error persisted and I restarted the managed network switch and again the error persisted. I note that daylight savings is on 3\/4\/2022 at 3am. The recordings showing in listings ends on 1\/4\/2022 so not sure that matters – but worth noting. The fun begins …<\/p>\n\n\n\n

Diagnostics<\/h1>\n\n\n\n

I looked at my notes from the previous similar error and tried the ideas from it, but it didn’t make any difference. <\/p>\n\n\n\n

I have a daily backup of MythTV, including the database and file system. However because of my workload at work I didn’t get to look at the issue until over a week after the problem occurred so I didn’t have a backup just prior to the problem happening so I had to go back to my next most recent backup on 7\/6\/2020 – nearly a year old.<\/p>\n\n\n\n

Rolling back the DB nearly a year resolved the problem – fantastic. <\/p>\n\n\n\n

Next I went to a backup just prior to the problems, this was dated 30\/March\/2021. This also worked correctly. So clearly something happened in the DB between the 30th and now.<\/p>\n\n\n\n

It was great the earlier backups worked, but it didn’t explain the problem and didn’t give me any clues about what to do if it came up again or what to do to prevent it. Not to mention I would have lost a years recordings.<\/p>\n\n\n\n

I tried the following, individually, but none of them made any difference:<\/p>\n\n\n\n