-
Notifications
You must be signed in to change notification settings - Fork 49
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
broken pipe issue #36
Comments
from your log, the reason is the websocket pipe between janus proxy and your client is broken which results into exception when we send mesage to it. janus-proxy has catch this exception and ignore it. |
For some high work load case, it's possible that the low level socket may be already broken but the high level business is not yet notified about that and still send some data to this socket. So, you may get the above log. |
2. fix a config folder acquirement bug 3. publisher make use the backend_admin_key of its backend room instead of the front room
I think this log is not the real reason make you failed, please check the cpu workload of janus-proxy |
@jamken Yes, I was observing cpu load as well, but didn't saw significant load.
This happens even with 2 rooms with 20 person in each - at some point log fills with |
I think this problem may be in your front http(websocket) proxy . the ws connections from the http proxy (like 127.0.0.1:46960) to the janus-proxy(maybe 127.0.0.1:8288) broken for some reason. Please try to bypass the http proxy and test again |
maybe the file fd number limitation? please check ulimite -a also |
Hi
I have setup with 1 yanus proxy and 2 janus servers behind it. It works good for all demos and test calls with 5-10 participants.
Now I'm testing it, trying to get stable 3 rooms with 20 members in each - but this doesn't work for now.
I see such logs in janys-proxy log file:
Any idea why this happen and how to fix?
The text was updated successfully, but these errors were encountered: