FreeSWITCH timeout for a short period

101 views
Skip to first unread message

Alexandros Diamantidis

unread,
May 26, 2020, 4:39:11 AM5/26/20
to bigblueb...@googlegroups.com
Hello all,

We are running some BigBlueButton servers without any trouble for a few
months now, but yesterday one of them exhibited a strange problem for a
short while: For about an hour, users were getting the "1002: Could not
make a WebSocket connection" while the nginx error log contained lines
of the form:

upstream timed out (110: Connection timed out) while connecting to
upstream, client: <client IP>, server: <server hostname>,
request: "GET /ws HTTP/1.1", upstream: "https://<server IP>:7443/ws"

I didn't restart BBB immediately, because I wanted to make sure there
were no sessions in progress using this server, but I checked
"systemctl status freeswitch.service" which indicated that it was "active
(running)". "journalctl -xe -u freeswitch.service" didn't contain any
errors, either. Just as soon as I started checking the logs, the errors
disappeared, and users were able to connect normally (without any
sysadmin action).

CPU, RAM and networking graphs didn't display anything out of the
ordinary, and the number of users connected to the server before the
problem started wasn't especially high (a few hours before, the server
handled more than twice the users).

Any ideas about the cause of the disruption, or where I might look to
determine it?

Thanks!

--
Alexandros Diamantidis * ad...@hellug.gr

Kim-Alexander Brodowski

unread,
May 26, 2020, 5:58:48 AM5/26/20
to BigBlueButton-dev
Hello Alexandros,

this sounds a lot like what we're discussing in this thread: https://groups.google.com/forum/#!topic/bigbluebutton-dev/u7C3o0q3IJo

Unfortunately we haven't found a solution yet that works for us.

Best regards,
Kim-A. Brodowski

Alexandros Diamantidis

unread,
May 27, 2020, 5:32:46 AM5/27/20
to bigblueb...@googlegroups.com
Thanks Kim,

Indeed, this seems similar to what we experienced, and the affected
server did have a somewhat older BBB release (not sure if it was 2.2.11
or something older, since it's been upgraded since) and also 16 cores
(you mention high core counts in your message). At the time, it was
running bbb-freeswitch-core 2.2.0-97 and it's now upgraded to 2.2.0-112.

I'll follow the thread and contact the devs with the requested info if
it happens again - hopefully the new FS version helps.

Cheers,
Alexandros

* Kim-Alexander Brodowski [2020-05-26 02:58]:
Reply all
Reply to author
Forward
0 new messages