-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
settings & storage-system: runtime error: invalid memory address or nil pointer dereference #4961
Comments
@NexZhu I added an error check to prevent the panic in cs3org/reva#3430. It seems we get an error from the os when trying to read the node. It might be a different ERRNO from the internal stat or getxatr call. Maybe the filesystem does not support xattrs? we will know more when trying with that PR. |
Yeah, I think you guessed right. I'm using Alibaba Cloud NAS and I think it doesn't support xattrs. Is there a way to workaround this limitation in the software layer? |
Unfortunately with the current ocis storage interface we need xattrs to store file metadata and access permissions. |
I tested with volumes witch support
The only log is:
|
To me this look like an error of your underlying infrastructure. Kubernetes fails to schedule the pod because of some issue with the volumes. I don't think there is much we can do about that. You might be able to find some more detail about what failed by taking a look at the volumes and pvc (using kubectl), or by looking at the lower level kubernetes logs (if you have access to that). |
Describe the bug
I deployed the latest version
owncloud/ocis:2.0.0-beta.8
with the official Helm chart and configured it to authenticate users with an OIDC provider Authelia instance, here's what happens:Accept
in the OAuth2 consent page.https://owncloud.example.com/oidc-callback.html?code=a0j4L6_ZuH2QbH5mPFJJbCVLH-OO9jIJg5mscuxPSiw.oqHE9PYJP1SnVboJth46PyRES17YKo9FT2WyONQhSTg&scope=openid+profile+email&state=9d6a21e638474d40bdaab11ebfb27088
https://owncloud.example.com/ocs/v1.php/cloud/user
with header:authorization: Bearer p9UAAo2wIMfb8RLlN_f7dW9u5mpxUl76IfUH3jAMEos.4b8WcEj1mLZOen34w719wsjoJa5tpq_ArXvub4M6NrY
, resulted in500
status code.Error logs
settings
pod:storage-system
pod:The text was updated successfully, but these errors were encountered: