-
Notifications
You must be signed in to change notification settings - Fork 29
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
Error while "Join audio as a listener" #29
Comments
Hi @pedrobmarin, Thanks |
Maybe it's a locale mismatch issue. Could you confirm your bot is accessing a bigbluebutton room with english default locale? You can set browser's headless mode to Line 34 in 0e27c5e
|
Yes, bigbluebutton room is using english as default locale. |
Hi @06dilipg I just made a quick test using v2.0.0 against a bigbluebutton development server and had no problem on joining the listen only audio. So, unless you manage to provide more details over your problem (bot's/media server debug logs) there's no much I can do to help. |
Hi @pedrobmarin, Please find below additional information: after running run.js below are the logs from begining with debug mode enabled: ubuntu@ip-0-0-0-0:~/bigbluebot$ node run.js Thanks |
Hi @06dilipg , thanks for the logs. Looks like one of your bots could not join the session:
and 60 seconds after that it timed out
I would expect both bots to have the same problem if this was a bot issue. Did you notice that while testing out of browser |
Hi @pedrobmarin, Observation while testing out in browser using headless mode:
FYI:
Thanks for looking at the issue at earliest. |
Hi @06dilipg This 401 message you got might be related with something that is going wrong at your BigBlueButton deploy or even a problem regarding BigBlueButton itself. Do you face similar problems while joining a large number of regular users in a small time interval? Can you reproduce this problem increasing bot's wait time? Lines 22 to 23 in 744ee63
|
Problem can be reproduced by increasing bot's wait time, BIGBLUEBOT_WAIT= 5000. I believe, BigBlueButton deployment is configured in right way because we're able to use BigBlueButton as expected. So it might not be an issue from BigBlueButton deployment When BIGBLUEBOT_BOTS=10, 6 are able to join and rest 4 bots are failing with below error:
Same issue is faced when joining a large number of regular users in a small time interval. Thanks |
Hmmm, another guess would be high CPU consumption at the machine that is triggering the bots (although 6 bots seems a really low number). Maybe that's the bottleneck you are facing. When we run our load tests we have to place sets of bots in multiple machines (normally big ones). |
Hi,
Setup of bigbluebutton and bigbluebot is done and while performing testing, i'm facing issue as mentioned below. Please have a look.
Bigbluebutton version used: 2.3
bigbluebot version used: 2.0
Join via video and chat are working as expected.
But "Join audio as a listener" snippet is not working as expected after running run.js file.
run.js file:
const bigbluebot = require('bigbluebot'); const actions = async page => { await bigbluebot.audio.modal.listen(page); }; bigbluebot.run(actions);
For your referrence, error screenshot is attached below:
Awaiting for the response.
Thanks
The text was updated successfully, but these errors were encountered: