Jump to content

allanp81

Members
  • Content Count

    240
  • Joined

  • Last visited

Everything posted by allanp81

  1. So strangely this now seems to be working... No idea why as I tried starting afresh and same issue so reverted back to my previous advancedsettings.xml and sources.xml and now it's seemingly working!
  2. I've tried trashing my appdata entirely and same issue. Either sonarr/lidarr/radarr are sending something weird (which can't be the case as my other clients all respond to a test) or the headless docker has an issue somewhere.
  3. Unfortunately nothing in that link seems relevant to my issue. The webserver on my headless docker is working and shows new items that other full clients have added.
  4. OK, enabled debug logging and I get this when sending a test from sonarr/radarr/lidarr etc: 2019-05-25 16:15:11.607 T:22479361640192 DEBUG: CWebServer[8080]: request received for /jsonrpc 2019-05-25 16:15:11.621 T:22479361640192 DEBUG: Previous line repeats 1 times. 2019-05-25 16:15:11.621 T:22479361640192 DEBUG: JSONRPC: Value does not match any of the enum values in type
  5. Yep, they both claim they were able to successfully talk to it, if I change a port etc. then they say they've failed. Worked fine with the krypton tag. Unfortunately I can't find many logs on the docker etc. to see where it's failing. There may be a way to enable verbose logging on the docker to get more of a clue.
  6. Nevermind, opening on a mobile shows the page differently. I have added the leia tag to the run command already and I know it's working as the headless web interface shows updates that I've added via other clients.
  7. Oh, the link just seems to take me to the root of the github page
  8. What am I supposed to be looking for on that link?
  9. I've updated all of my clients and docker to leia but it looks like the headless docker is not longer receiving updates from either sonarr or radarr and from the kodi.log it looks like nothing happens when they attempt to connect to it for update the library.
  10. I'm having this same issue and haven't changed anything other than upgrade Unraid. It used to show me load usage etc. but now only shows me battery charge level and estimated time remaining. I'm using an APC Back-UPS ES 700G
  11. Yes it seems to be working fine but obviously not reporting a version number anymore.
  12. Anyone else seeing this: I'm on "linuxserver/tvheadend:release-4.2" and the last time the docker updated was last night.
  13. Likewise, I got one the other week and flashed it to IT mode. Cost me about £30 total and works great
  14. How does that compare to a Dell H310 sas that you can pick up from ebay for about £25?
  15. So I fixed my issue, looks like the update to mysql screwed stuff up. I followed the suggestion here: https://help.nextcloud.com/t/nextcloud-13-php-7-1-mysql-8-error-500/34443/2 and it solved it. The solution was setting [mysqld] default_authentication_plugin=mysql_native_password in my.cnf seems to help.
  16. So since a few days ago my nextcloud has stopped working and I just see the following errors in the log: Stack trace: #0 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(125): OC\AppFramework\Utility\SimpleContainer->resolve('defaultTokenPro...') #1 /config/www/nextcloud/lib/private/ServerContainer.php(132): OC\AppFramework\Utility\SimpleContainer->query('defaultTokenPro...') #2 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(81): OC\ServerContainer->query('defaultTokenPro...') #3 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(104): OC\AppFramework\Utility\SimpleContainer->buildClass(Object(ReflectionClass)) #4 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(125): OC\AppFramework\Utility\SimpleContainer->resolve('OC\\Authenticati...') #5 /config/www/nextcloud/lib/private/ServerContainer.php(132): OC\AppF in /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php on line 110 PHP Fatal error: Uncaught OCP\AppFramework\QueryException: Could not resolve defaultTokenProvider! Class defaultTokenProvider does not exist in /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php:110 Stack trace: #0 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(125): OC\AppFramework\Utility\SimpleContainer->resolve('defaultTokenPro...') #1 /config/www/nextcloud/lib/private/ServerContainer.php(132): OC\AppFramework\Utility\SimpleContainer->query('defaultTokenPro...') #2 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(81): OC\ServerContainer->query('defaultTokenPro...') #3 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(104): OC\AppFramework\Utility\SimpleContainer->buildClass(Object(ReflectionClass)) #4 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(125): OC\AppFramework\Utility\SimpleContainer->resolve('OC\\Authenticati...') #5 /config/www/nextcloud/lib/private/ServerContainer.php(132): OC\AppF in /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php on line 110 Nothing I try works, any occ command etc. always just returns the same rubbish. I'm using mysql as my db server and that updated the other day so I'm assuming the 2 are related but I'm blowed if I can work out how to resolve this.
  17. How did you create the script and edit it? Edit it via bash using nano and confirm there's no funny characters etc.
  18. 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.
  19. 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.
  20. 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
  21. 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?
  22. That's hot for idle, you'll probably find you'll get temp warnings during a parity check.
  23. You would use new config if you don't plan on replacing the drive that is failing. Otherwise you would just replace that drive with a new one.
  24. I've rebooted and so far no errors in the log at all. Will keep an eye on it and post the full diagnostics if it errors again. Thanks for your help.