-
Notifications
You must be signed in to change notification settings - Fork 186
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
PROPFIND
for personal space is flaky
#4597
Labels
Comments
This is basically a duplicate of #3134 Happens when multiple ocis instances (all using the mdns registry) are running in the same network. This results in both instance "seeing" each others service registrations -> 💣 💥 |
closing because of duplicate. |
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Sep 21, 2022
This avoids various issues of the old "mdns" default. At least for the simple single process setup (owncloud#3258, owncloud#4597). When starting the services individually we still default to "mdns".
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Sep 21, 2022
This avoids various issues of the old "mdns" default. At least for the simple single process setup (owncloud#3258, owncloud#4597). When starting the services individually we still default to "mdns".
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Sep 21, 2022
This avoids various issues of the old "mdns" default. At least for the simple single process setup (owncloud#3134, owncloud#4597). When starting the services individually we still default to "mdns".
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Sep 23, 2022
This avoids various issues of the old "mdns" default. At least for the simple single process setup (owncloud#3134, owncloud#4597). When starting the services individually we still default to "mdns".
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Sep 23, 2022
This avoids various issues of the old "mdns" default. At least for the simple single process setup (owncloud#3134, owncloud#4597). When starting the services individually we still default to "mdns".
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Sep 26, 2022
This avoids various issues of the old "mdns" default. At least for the simple single process setup (owncloud#3134, owncloud#4597). When starting the services individually we still default to "mdns".
ownclouders
pushed a commit
that referenced
this issue
Sep 26, 2022
Author: Ralf Haferkamp <[email protected]> Date: Wed Sep 21 17:50:06 2022 +0200 Default to in-memory registry in single-binary mode This avoids various issues of the old "mdns" default. At least for the simple single process setup (#3134, #4597). When starting the services individually we still default to "mdns".
ownclouders
pushed a commit
that referenced
this issue
Sep 27, 2022
Author: Ralf Haferkamp <[email protected]> Date: Wed Sep 21 17:50:06 2022 +0200 Default to in-memory registry in single-binary mode This avoids various issues of the old "mdns" default. At least for the simple single process setup (#3134, #4597). When starting the services individually we still default to "mdns".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We noticed that the
PROPFIND
for the personal space is flaky on current master.Steps to reproduce
curl -X PROPFIND https://localhost:9200/remote.php/dav/spaces/1284d238-aa92-42ce-bdc4-0b0000009157%2412a30d44-3145-4659-9a86-b4cfdc4e3d19 -k -u admin:admin -i
Expected behavior
A consistent
207
response.Actual behavior
From time to time, oCIS returns a
502: Bad gateway
The text was updated successfully, but these errors were encountered: