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.

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

"jaeger-1 | {"level":"info","ts":1736772200.8857656,"caller":"transport/controlbuf.go:577","msg":"[transport] [server-transport 0xc000134000] loopyWriter exiting with error: transport closed by client"}" #7

Open
Amelia-00 opened this issue Jan 15, 2025 · 1 comment

Comments

@Amelia-00
Copy link

After entering make all-services, I got the following logs:
jaeger-1 | {"level":"info","ts":1736770404.7419152,"caller":"[email protected]/clientconn.go:544","msg":"[core] [Channel #1]Channel Connectivity change to READY"}

Translation: The gRPC channel has changed to READY state (indicating successful connection establishment)

jaeger-1 | {"level":"info","ts":1736772200.8856678,"caller":"transport/http2_server.go:662","msg":"[transport] [server-transport 0xc000134000] Closing: EOF"}

Translation: The HTTP/2 server transport connection is closing due to EOF (End Of File)

jaeger-1 | {"level":"info","ts":1736772200.885668,"caller":"transport/http2_server.go:662","msg":"[transport] [server-transport 0xc000482ea0] Closing: EOF"}

Translation: Another HTTP/2 server transport connection is closing due to EOF

jaeger-1 | {"level":"info","ts":1736772200.8857656,"caller":"transport/controlbuf.go:577","msg":"[transport] [server-transport 0xc000134000] loopyWriter exiting with error: transport closed by client"}

Translation: The transport writer is exiting because the client closed the connection

And then it got stuck. Can you help me look at this issue?

@FTi130
Copy link

FTi130 commented Jan 17, 2025

Not sure if it's towards the same issue. Have this trace after make all-services:

celery-worker-1  | [2025-01-17 20:40:42,969: INFO/MainProcess] celery@72853565e797 ready.
jaeger-1         | {"level":"info","ts":1737148396.2070267,"caller":"transport/http2_server.go:662","msg":"[transport] [server-transport 0xc0000c6820] Closing: EOF"}
jaeger-1         | {"level":"info","ts":1737148396.2078836,"caller":"transport/controlbuf.go:577","msg":"[transport] [server-transport 0xc0000c6820] loopyWriter exiting with error: transport closed by client"}
jaeger-1         | {"level":"info","ts":1737148396.5968702,"caller":"transport/http2_server.go:662","msg":"[transport] [server-transport 0xc0000c6ea0] Closing: EOF"}
jaeger-1         | {"level":"info","ts":1737148396.5970154,"caller":"transport/controlbuf.go:577","msg":"[transport] [server-transport 0xc0000c6ea0] loopyWriter exiting with error: transport closed by client"}

Manual launch with venv got this:

raise Exception(f"{header}\n{body}") from None
Exception: [402] Payment Required
Account 'BP0gGcIA11AKRauiWgontHzA_ICUwRKZlwP9hS7tg4I': Cloud credits expired - Please contact NVIDIA representatives

I had to insert a key taken from ngc directly and placed in test_nvidia_api_key()
(initially it is generated in the process and stored in Personal Keys with autogenerated key name)

Try to understand, I messed a setup or it is the Cloud Credits issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants