ocis: Infinite loop when trying to login
Describe the bug
Hello, I host Owncloud OCIS app in TrueNas Scale. Recently, maybe after some upgrade of the app, I cannot login to Owncloud anymore. I get into an infinite loop when I try to login.
The earliest error is runtime error: invalid memory address or nil pointer dereference…
Here is the log:
2023-07-05 08:05:28.097167+00:00[36mpkg=[0mrgrpc [36mservice=[0mstorage-system [36mtraceid=[0m00000000000000000000000000000000
2023-07-05 08:05:28.097202+00:00[90m2023-07-05T08:05:28Z[0m [1m[31mERR[0m[0m unary [36mcode=[0mInternal [36mend=[0m"05/Jul/2023:08:05:28 +0000" [36mfrom=[0mtcp://127.0.0.1:40236 [36mpkg=[0mrgrpc [36mservice=[0mstorage-system [36mstart=[0m"05/Jul/2023:08:05:28 +0000" [36mtime_ns=[0m2650725 [36mtraceid=[0m00000000000000000000000000000000 [36muri=[0m/cs3.storage.provider.v1beta1.ProviderAPI/Stat [36muser-agent=[0mgrpc-go/1.51.0
2023-07-05 08:05:28.097238+00:00[90m2023-07-05T08:05:28Z[0m [1m[31mERR[0m[0m error initializing metadata client [36merror=[0m[31m"rpc error: code = Internal desc = runtime error: invalid memory address or nil pointer dereference"[0m [36mservice=[0mocis
2023-07-05 08:05:28.097265+00:00[90m2023-07-05T08:05:28Z[0m [1m[31mERR[0m[0m Could not load roles [36merror=[0m[31m"{\"id\":\"go.micro.server\",\"code\":500,\"detail\":\"panic recovered: runtime error: invalid memory address or nil pointer dereference\",\"status\":\"Internal Server Error\"}"[0m [36mservice=[0mproxy
2023-07-05 08:05:28.097387+00:00[90m2023-07-05T08:05:28Z[0m [1m[31mERR[0m[0m Could not get user by claim [36merror=[0m[31m"{\"id\":\"go.micro.server\",\"code\":500,\"detail\":\"panic recovered: runtime error: invalid memory address or nil pointer dereference\",\"status\":\"Internal Server Error\"}"[0m [36mservice=[0mproxy
2023-07-05 08:05:28.784435+00:00[90m2023-07-05T08:05:28Z[0m [1m[31mERR[0m[0m Could not load roles [36merror=[0m[31m"{\"id\":\"com.owncloud.api.settings\",\"code\":502,\"detail\":\"circuit breaker is open\",\"status\":\"Bad Gateway\"}"[0m [36mservice=[0mproxy
2023-07-05 08:05:28.784754+00:00[90m2023-07-05T08:05:28Z[0m [1m[31mERR[0m[0m Could not get user by claim [36merror=[0m[31m"{\"id\":\"com.owncloud.api.settings\",\"code\":502,\"detail\":\"circuit breaker is open\",\"status\":\"Bad Gateway\"}"[0m [36mservice=[0mproxy
2023-07-05 08:05:29.133182+00:00[90m2023-07-05T08:05:29Z[0m [1m[31mERR[0m[0m Could not load roles [36merror=[0m[31m"{\"id\":\"com.owncloud.api.settings\",\"code\":502,\"detail\":\"circuit breaker is open\",\"status\":\"Bad Gateway\"}"[0m [36mservice=[0mproxy
2023-07-05 08:05:29.133278+00:00[90m2023-07-05T08:05:29Z[0m [1m[31mERR[0m[0m Could not get user by claim [36merror=[0m[31m"{\"id\":\"com.owncloud.api.settings\",\"code\":502,\"detail\":\"circuit breaker is open\",\"status\":\"Bad Gateway\"}"[0m [36mservice=[0mproxy
failed to create fsnotify watcher: too many open files
Steps to reproduce
Steps to reproduce the behavior:
- open login page
- enter login and password
Expected behavior
The user should be signed in
Actual behavior
Loop loop loop
Setup
TrueNas Scale Bluefin
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 15 (7 by maintainers)
Thank you for reopening the issue. I agree that migration is very well described, I followed the steps and had no errors during the migration. I’ll be happy to assist to drill down to the issue.
@dragonchaser @nZeus @v3DJG6GL I am re opening that thread. Seems that there is no solution so far.
IMO the problem here is, that maybe multiple errors are overlapping each other and we cannot get down to the real problem.
I am running some ocis instances (docker compose) since version 1.0.0 with real data and had not such an experience.
The 2.0 -> 3.0 migration is very simple and straightforward. IMO if it doesn’t succeed, we need a way to “re-trigger”.
@butonic @aduffeck please provide guidance in this case.
This is why it is called the “DecomposedFS”. That means heavy performance optimization which could not be provided by a classical tree layout. There are alternatives, EOS cluster storage (community effort) and in the future SMB.
@mmattel can you mention in the docs that migration from to message pack is a one-way ticket atm?
Manually run a setup of ocis 3.0.0 on a local machine with your data mounted and hope for the best…
BTW, regarding the upgrade from 2.0.0 to 3.0.0 make sure to read: https://doc.owncloud.com/ocis/next/migration/upgrading-ocis.html#version-2-0-0-to-3-0-0