allanp81

Members
  • Posts

    333
  • Joined

  • Last visited

Everything posted by allanp81

  1. Looks like the last time my Mysql docker got updated it's been upgraded to version 8. Is there a simple way I can migrate my DBs over to this container instead?
  2. They show fine for me. What version is it showing as running for you?
  3. I always have the same issue as well, it's very annoying as it means I can't have it set to auto update the docker. Would love to know how to solve this.
  4. I couldn't get a downgrade to work, had to start again sadly.
  5. I would imagine you've got to change the base url somehow, otherwise it will assume everything is in the root.
  6. Hey, although I had to start again and clear my appdata I'm not all back and running and have used the release-4.2 build that you suggested and everything looks great so thanks for helping me earlier.
  7. Hey, although I had to start again and clear my appdata I'm not all back and running and have used the release-4.2 build that you suggested and everything looks great so thanks for helping me earlier.
  8. Well to be honest it's now working again so not sure I ever want to update ever again!
  9. OK I'm all working again after switching to the old stable release, thanks for your help. Now to work out how to reimport all of my recordings...
  10. Yes but at first it didn't make sense. We're not all experts
  11. Hmm that's odd as I thought I'd added the stable version. What's the simplest way to "downgrade"? Do I need to remove the docker container and just re-add from the apps tab in Unraid and choose the stable version?
  12. For instance: 2018-03-25 13:59:37.613 [ INFO] subscription: 0005: "192.168.7.181 [ download | Kodi Media Center ]" subscribing on channel "ITV HD", weight: 150, adapter: "HDHomeRun DVB-T Tuner #1 (192.168.7.103)", network: "UK Freeview", mux: "545.8MHz", service: "ITV HD", profile="htsp", hostname="192.168.7.181", username="download", client="Kodi Media Center" 2018-03-25 14:00:02.912 [ INFO] subscription: 0005: "192.168.7.181 [ download | Kodi Media Center ]" unsubscribing from "ITV HD", hostname="192.168.7.181", username="download", client="Kodi Media Center" 2018-03-25 14:00:02.915 [ INFO] mpegts: 545.8MHz in UK Freeview - tuning on HDHomeRun DVB-T Tuner #1 (192.168.7.103) 2018-03-25 14:00:02.915 [ INFO] tvhdhomerun: tuning to auto:545800000 2018-03-25 14:00:02.944 [ INFO] subscription: 0007: "192.168.7.181 [ download | Kodi Media Center ]" subscribing on channel "BBC ONE HD", weight: 150, adapter: "HDHomeRun DVB-T Tuner #1 (192.168.7.103)", network: "UK Freeview", mux: "545.8MHz", service: "BBC ONE HD", profile="htsp", hostname="192.168.7.181", username="download", client="Kodi Media Center" 2018-03-25 14:00:05.171 [WARNING] TS: UK Freeview/545.8MHz/BBC ONE HD: H264 @ #6601 Continuity counter error (total 1) Status page show it tuned to BBC ONE HD and receiving data with no errors.
  13. I think it was the "default" version. I can't remember and can't check what the options were again without removing the docker container and readding it. Is there another way to find out? Log shows this on launching of the docker: NOTICE] START: HTS Tvheadend version 4.3-1206~g5de70b42e started, running as PID:204 UID:99 GID:100, CWD:/run/s6/services/tvheadend CNF:/config I've also just noticed this: 2018-03-25 13:58:24.517 [ ERROR] tvhdhomerun: failed to acquire lockkey: ERROR: resource locked by 192.168.7.11 2018-03-25 13:58:24.517 [ ERROR] tvhdhomerun: failed to reset pfilter: 0 Some channels work though but most don't.
  14. This is strange: 2018-03-25 13:52:47.264 [ INFO] subscription: 005C: "HTTP" unsubscribing from "BBC ONE HD", hostname="192.168.7.158", client="Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36" 2018-03-25 13:52:47.269 [ INFO] mpegts: 545.8MHz in UK Freeview - tuning on HDHomeRun DVB-T Tuner #1 (192.168.7.103) 2018-03-25 13:52:47.269 [ INFO] tvhdhomerun: tuning to auto:545800000 2018-03-25 13:52:47.300 [ INFO] subscription: 005E: "HTTP" subscribing on channel "BBC ONE HD", weight: 100, adapter: "HDHomeRun DVB-T Tuner #1 (192.168.7.103)", network: "UK Freeview", mux: "545.8MHz", service: "BBC ONE HD", profile="matroska", hostname="192.168.7.158", client="Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36" 2018-03-25 13:52:49.543 [WARNING] TS: UK Freeview/545.833MHz/BBC ONE HD: H264 @ #6601 Continuity counter error (total 1) 2018-03-25 13:53:07.321 [WARNING] webui: Stop streaming /stream/channel/57d583f3f68058ff9b2f5629ecdd0f3e?profile=matroska, timeout waiting for packets Was working fine yesterday.
  15. This docker updated last night and now it seems the majority of my mapped channels don't work. I'm in the UK on Freeview HD and they were all working fine yesterday. It says it's tuned successfully under the status page but the channel just never loads. I'm using a hd homerun connect and the channels load fine using the hdhomerun app so I know it's not a signal issue etc. Does anyone know where the log is located?
  16. When I had similar issues it was a faulty stick of ram that strangely always passed memtest
  17. Take a copy of your VM XML and also the vdisk first?
  18. Can you make that change to an existing VM though without it mucking up the Windows side? I realise it might affect activiation but will the VM still boot?
  19. It's in the release notes, apparently it's nothing to worry about
  20. I see the same on my Windows 7 VM. It's rock solid but as soon as I start copying via the network I see massive latency spikes. I never got to the bottom of it but I saw the same issue on a virtual nic as well as a real PCI nic passed through to the VM.
  21. I'm seeing exactly the same, everything appears to be working fine though.