Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Collabora is not available #8474

Closed
ScharfViktor opened this issue Feb 16, 2024 · 5 comments · Fixed by #8483 or #8984
Closed

Collabora is not available #8474

ScharfViktor opened this issue Feb 16, 2024 · 5 comments · Fixed by #8483 or #8984
Labels
Type:Bug

Comments

@ScharfViktor
Copy link
Contributor

ScharfViktor commented Feb 16, 2024 •
edited

Step:

Actual:
Screenshot 2024-02-16 at 10 16 50

image

app-provider-collabora log:

2024-02-15 21:44:08 {"level":"fatal","service":"app-provider-collabora","error":"Failed to connect to NATS Server: nats: no servers available for connection","time":"2024-02-15T20:44:08Z","message":"Registration error for external service com.owncloud.api.app-provider-collabora"}
2024-02-15 21:44:09 {"level":"error","service":"app-provider-collabora","error":"unable to register services: rgrpc: grpc service appprovider could not be started,: Application server at https://collabora.owncloud.test does not match this AppProvider for Collabora","time":"2024-02-15T20:44:09Z","message":"error starting the grpc server"}

cc @2403905
@2403905
Copy link
Contributor

2403905 commented Feb 16, 2024

The collabora discovery endpoint is not reachable from the ocis-appprovider-collabora docker container

~ $ curl --show-error --fail http://collabora/hosting/discovery -vk
* Host collabora:80 was resolved.
* IPv6: (none)
* IPv4: 172.26.0.5
*   Trying 172.26.0.5:80...
* connect to 172.26.0.5 port 80 from 172.26.0.7 port 49054 failed: Connection refused
* Failed to connect to collabora port 80 after 3 ms: Couldn't connect to server
* Closing connection
curl: (7) Failed to connect to collabora port 80 after 3 ms: Couldn't connect to server

But on the host machine is works well curl -vk https://collabora.owncloud.test/hosting/discovery

@2403905
Copy link
Contributor

2403905 commented Feb 16, 2024

This is a race condition when the app provider can't talk to nats and can't restart properly.

This was referenced Feb 19, 2024
Merged
Merged
@DeepDiver1975 DeepDiver1975 mentioned this issue Apr 4, 2024
Merged
8 tasks
@DeepDiver1975
Copy link
Member

In case the app provider cannot read the discovery endpoint the process will terminate and restart - see this log:

ocis-appprovider-collabora-1  | {"level":"error","service":"app-provider-collabora","error":"unable to register services: rgrpc: grpc service appprovider could not be started,: Application server at https://collabora.owncloud.test does not match this AppProvider for Collabora","time":"2024-04-25T13:29:21Z","line":"github.com/cs3org/reva/v2@v2.19.2-0.20240422150349-51ab7655f858/cmd/revad/runtime/runtime.go:206","message":"error starting the grpc server"}
ocis-appprovider-collabora-1  | {"level":"info","service":"app-provider-collabora","pkg":"grace","time":"2024-04-25T13:29:21Z","line":"github.com/cs3org/reva/v2@v2.19.2-0.20240422150349-51ab7655f858/cmd/revad/internal/grace/grace.go:95","message":"pid file \"/tmp/revad-app-provider-collabora-26355e27-df5a-49d7-b168-8d2ecfa794ac.pid\" got removed"}
ocis-appprovider-collabora-1  | {"level":"info","service":"app-provider-collabora","time":"2024-04-25T13:29:23Z","line":"github.com/owncloud/ocis/v2/ocis-pkg/registry/register.go:17","message":"registering external service com.owncloud.api.app-provider-collabora-53f5fb34-0dda-409c-98a9-7de0181c74e5@172.28.0.11:9164"}
ocis-appprovider-collabora-1  | {"level":"info","service":"app-provider-collabora","time":"2024-04-25T13:29:23Z","line":"github.com/cs3org/reva/v2@v2.19.2-0.20240422150349-51ab7655f858/cmd/revad/runtime/runtime.go:85","message":"host info: 6a4ed02f5627"}
ocis-appprovider-collabora-1  | {"level":"info","service":"app-provider-collabora","time":"2024-04-25T13:29:23Z","line":"github.com/cs3org/reva/v2@v2.19.2-0.20240422150349-51ab7655f858/cmd/revad/runtime/runtime.go:178","message":"running on 4 cpus"}

Unless I miss anything in the next startup cycle reading the discovery url is successful and everything should work as design - but it doesn't .... why?

@DeepDiver1975 DeepDiver1975 mentioned this issue Apr 25, 2024
Open
@micbar micbar reopened this Apr 26, 2024
@micbar
Copy link
Contributor

micbar commented Apr 26, 2024

Please keep open, the mentioned PR should be reverted, we cannot use user:0 in any ocis container.

@DeepDiver1975
Copy link
Member

DeepDiver1975 commented Apr 26, 2024 •
edited

I tried to play around with a wait-for-it container - but this did not yet work out ...
https://github.com/owncloud/ocis/compare/feat/docker-wait-for?expand=1

@DeepDiver1975 DeepDiver1975 mentioned this issue Apr 26, 2024
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type:Bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix the docker-compose wopi 2403905/ocis
fix: use docker healthcheck owncloud/ocis
4 participants
@DeepDiver1975 @micbar @2403905 @ScharfViktor