allanp81

Likewise, I got one the other week and flashed it to IT mode. Cost me about £30 total and works great

How does that compare to a Dell H310 sas that you can pick up from ebay for about £25?

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.

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.

How did you create the script and edit it? Edit it via bash using nano and confirm there's no funny characters etc.

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.

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.

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.

Ok, that's not great, I'm almost too scared to reboot in case it doesn't come back!

Thanks, I meant to do that but only posted the syslog downloadbox-diagnostics-20180629-0913.zip

I just noticed that my syslog has been showing the following for the last week: Jun 22 04:52:28 downloadbox kernel: blk_partition_remap: fail for partition 1 Jun 22 04:52:28 downloadbox kernel: XFS (sda1): metadata I/O error: block 0x75513e80 ("xfs_trans_read_buf_map") error 5 numblks 32 Jun 22 04:52:28 downloadbox kernel: XFS (sda1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. My server seems ok although around midnight last night I did get a few emails claiming that my cache disk was nearly full that seems to be fine once I got up this morning and apart from the email notifications I can't see any errors relating to this in the syslog. I also can't find any references to what sda1 thinks it is, as there is no sda1 listed under system devices. downloadbox-syslog-20180629-0845.zip