allanp81

If you enter the docker via the console, can you confirm that the script is visible and that you can execute it? It sounds like you're using a pre-release as I think 4.2.x are the stable releases. I had issues with 4.3 and had to revert back to stable. What release is your docker configured for? Yes, I use the #!/bin/bash shebang thingy at the start of my script.

Where is the script located? Can the docker see that location? For reference, I launch my post processing script with: /recordings/cleanup.sh "%f" "%b" When I was testing mine out I added a simple "touch test.txt" to my script just to confirm it was actually processing. You may need add a path to the touch command depending on what you're trying.

Seems that nextcloud doesn't play nice with mysql 8. I fixed it by following the guide here: https://help.nextcloud.com/t/nextcloud-13-php-7-1-mysql-8-error-500/34443/3 I had to edit the my.cnf file in the mysql docker (/etc/mysql/my.cnf) and add the following line to the [mysqld] section: default_authentication_plugin=mysql_native_password

The docker for this updated last night and now nothing is working for me anymore. The logs seem to be littered with the following after the update: Anyone else seeing this and have any idea what it's going on about?

That's hot for idle, you'll probably find you'll get temp warnings during a parity check.

I'm running the linuxserver docker via CA. I'm also running mysql 8.0 I think. It used to be instant when I first started using it.

That's similar to what I'm experiencing, it just seems to take a while to show any files.

Does anyone else find nextcloud quite slow to list all of your files via the web interface? I've stored my nextcloud data folder on an SSD that's never going to sleep so it's not a spindown issue.

Yes it's using DHCP. I did think to just change the DNS on unraid to static but it means shutting everything as you have to stop all dockers and array to change the network settings. *Edit, I looked again and it's only docker and vm services that needed stopping. I've changed DNS servers to static and now it's working again. I couldn't see anything in the pihole logs to show anything being blocked though which is weird.

I've installed this docker and it seems to be working great across all devices *but* it seems to stop my unraid server from being able to check for plugin and docker updates. If I ask unraid to check for docker updates it just sits forever asking but pihole doesn't seem to suggest that it's blocked anything from being checked so I'm confused.

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?

They show fine for me. What version is it showing as running for you?

Yep, that works for me too

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.

I couldn't get a downgrade to work, had to start again sadly.

I would imagine you've got to change the base url somehow, otherwise it will assume everything is in the root.

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.

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.

Well to be honest it's now working again so not sure I ever want to update ever again!

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...

Yes but at first it didn't make sense. We're not all experts

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?

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.

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.