question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WebSocket connection warnings

See original GitHub issue

Hello. I have the latest dockerized Serum Vial running on a 6 CPU and 16Gb RAM machine that works with a dedicated Solana RPC node querying for 143 markets data. There is a lot of WebSocket connection warning messages as mentioned below. I see they usually appear in 5-10 minutes after an instance starts. Is it a problem and what side I should tune to fix it (Solana RPC, Serum Vial, or connectivity between them)? Let me know if the full log may help. Thank you!

warn: WS send error: write ECONNRESET
warn: WS send error: write EPIPE
warn: WS send error: WebSocket is not open: readyState 2
warn: WS send error: WebSocket is not open: readyState 3 (CLOSED)
warn: Out of order notification for PUBLISHED event: current slot 77095564, update slot: 77095564, resetting... {"market":"SRM/SOL"}

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
thaaddeuscommented, May 7, 2021

Hi, I had issues running on smaller machines as Solana RPC requires quite a lot of resources (memory as well) - right now I’m running on https://www.hetzner.com/dedicated-rootserver/ax101 (AMD Ryzen™ 9 5950X 16-Core, 128GB of RAM) and it’s very stable. WS send logs can be ignored I think (it’s client that connects to serum-vial dropped connection) Out of order notification could suggest you’re running out of resources, what’s your CPU usage?

0reactions
khssnvcommented, May 10, 2021

Thank you for these clarifications 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

WebSocket: error event - Web APIs | MDN
The error event is fired when a connection with a WebSocket has been closed due to an error (some data couldn't be sent...
Read more >
Troubleshooting connection issues | Socket.IO
You are trying to reach a plain WebSocket server; The server is not reachable; The client is not compatible with the version of...
Read more >
"Ignoring unrecognized message" warning while listening for ...
Trying to listen for a websocket event on frontend using the following code var socket = new WebSocket(`wss://${window.location.host}`); ...
Read more >
Allowing insecure WebSocket connections | Damir's Corner
SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS. Chrome also ...
Read more >
[WARNING] data websocket error, restarting connection: no ...
[WARNING] data websocket error, restarting connection: no close frame received or sent · [WARNING] data websocket error, restarting connection: ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found