monsieurhannes
commented
1 year ago Can you run this in your CLI: docker exec -it nextcloudpi ncp-report? You can post the output here.
Open jiyang1018 opened 1 year ago
monsieurhannes
commented
1 year ago Can you run this in your CLI: docker exec -it nextcloudpi ncp-report? You can post the output here.
jiyang1018
commented
1 year ago Can you run this in your CLI:
docker exec -it nextcloudpi ncp-report? You can post the output here.
I removed a few lines in "tursted domain", and I hope that does not matter.
<--! Paste this in GitHub report -->
ZendaiOwl
commented
1 year ago It looks like something has happened with the redis server, the username & password doesn't match anymore. When you deleted the files in the 'appdata' directory, did you remove the volume or leave the old one?
You can also check the logs with docker logs nextcloudpi
nunq
commented
1 year ago Hi all,
I think the same thing happened to me today when I tried upgrading my ncp v1.50.1 container running nextcloud 24.0.8. (First I upgraded the container and then nextcloud within the container. This method probably isn't the proper way to do it but anyhow...)
After upgrading I tried accessing my nextcloud and it sporadically threw HTTP 500s at me, when I looked at the logs I found a bunch of these: RedisException: WRONGPASS and NOAUTH (see attached logs).
It seems Redis changed their auth scheme in v6.x and a 'default' user now exists. From what I've read when this user is not supplied the 'default' user should be implicitly used, but apparently that doesn't happen or otherwise I wouldn't be getting these auth errors.
Then I looked into the source code and it seems that nextcloud can in fact send a username, I just didn't have that parameter set in my config.php because it wasn't needed before.
working (for me) redis conf:
'redis' =>
array (
'host' => '/var/run/redis/redis.sock',
'user' => 'default',
'port' => 0,
'timeout' => 0.0,
'password' => 'PASSWORD',
)I hope this helps.
Relevant logs:
feutl
commented
1 year ago Are those two somehow releated, I do have the same issues and struggling in finding the reason, but if someone helps, perhaps I can provide some information. https://github.com/nextcloud/nextcloudpi/issues/1740#issuecomment-1466188049
feutl
commented
1 year ago Adding "default" user to the config.php redis configuration for my NCP-docker installation removed the error from the logs and for now it seems it has fixed some of the weird issues coming with a redis problem.
feutl
commented
1 year ago After a reboot of my NCP docker I have the same issue again. The docker installation changes the redis password every reboot, so I assume that this messes things up if the user is being set because even with the default user I get the error again :(
feutl
commented
1 year ago I did some more testing, and actually not the default user fixed the problem, but restarting php after the docker instance was booted. It seems that the password change, which is done on every restart for the docker installation is propagated to the redis config, but not all services are rebooted afterwards.
For now I do a restart of redis and php and the problems on my NCP docker instance disappeared.
service redis-server restart
service php8.1-fpm restart
I completed deleted the previous docker, and all the files left in appdata directory, pulled the latest, and started over. It worked for the past week until last night. This morning, all my nextcloud clients couldn't connect, and I believe the kill switch on my server got triggered; I restarted my unraid server. After all dockers were running, I got this error first
then it cycled between this and the previous one a little bit
now it gives only this:
log seems to be a repeatition of this with different "reqId" and "time"
I tried status.php, and it returned:
Please let me know what info is needed to solve this issue. Thanks in advance.