You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"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
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)
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?
The text was updated successfully, but these errors were encountered:
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?
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?
The text was updated successfully, but these errors were encountered: