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:00pkg=rgrpc service=storage-system traceid=00000000000000000000000000000000
2023-07-05 08:05:28.097202+00:002023-07-05T08:05:28Z ERR unary code=Internal end="05/Jul/2023:08:05:28 +0000" from=tcp://127.0.0.1:40236 pkg=rgrpc service=storage-system start="05/Jul/2023:08:05:28 +0000" time_ns=2650725 traceid=00000000000000000000000000000000 uri=/cs3.storage.provider.v1beta1.ProviderAPI/Stat user-agent=grpc-go/1.51.0
2023-07-05 08:05:28.097238+00:002023-07-05T08:05:28Z ERR error initializing metadata client error="rpc error: code = Internal desc = runtime error: invalid memory address or nil pointer dereference" service=ocis
2023-07-05 08:05:28.097265+00:002023-07-05T08:05:28Z ERR Could not load roles error="{\"id\":\"go.micro.server\",\"code\":500,\"detail\":\"panic recovered: runtime error: invalid memory address or nil pointer dereference\",\"status\":\"Internal Server Error\"}" service=proxy
2023-07-05 08:05:28.097387+00:002023-07-05T08:05:28Z ERR Could not get user by claim error="{\"id\":\"go.micro.server\",\"code\":500,\"detail\":\"panic recovered: runtime error: invalid memory address or nil pointer dereference\",\"status\":\"Internal Server Error\"}" service=proxy
2023-07-05 08:05:28.784435+00:002023-07-05T08:05:28Z ERR Could not load roles error="{\"id\":\"com.owncloud.api.settings\",\"code\":502,\"detail\":\"circuit breaker is open\",\"status\":\"Bad Gateway\"}" service=proxy
2023-07-05 08:05:28.784754+00:002023-07-05T08:05:28Z ERR Could not get user by claim error="{\"id\":\"com.owncloud.api.settings\",\"code\":502,\"detail\":\"circuit breaker is open\",\"status\":\"Bad Gateway\"}" service=proxy
2023-07-05 08:05:29.133182+00:002023-07-05T08:05:29Z ERR Could not load roles error="{\"id\":\"com.owncloud.api.settings\",\"code\":502,\"detail\":\"circuit breaker is open\",\"status\":\"Bad Gateway\"}" service=proxy
2023-07-05 08:05:29.133278+00:002023-07-05T08:05:29Z ERR Could not get user by claim error="{\"id\":\"com.owncloud.api.settings\",\"code\":502,\"detail\":\"circuit breaker is open\",\"status\":\"Bad Gateway\"}" service=proxy
failed to create fsnotify watcher: too many open files

Steps to reproduce

Steps to reproduce the behavior:

  1. open login page
  2. 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)

Most upvoted comments

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.

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. I understand the need of a custom FS, and performance is indeed great when using the DecomposesdFS. Though it would be great to see SMB support in the future

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

Yes, I used the heavy script to copy the files out of the PVC, but unfortunately owncloud has their own filesystem - basically, they obfuscate all the file names 😭 .

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