Possible FreeSWITCH upgrade problem

[Martin Goik]

Hello,

we are currently running a Scalelite /  BBB cluster of 16 nodes. 15 of these are running fine.

No. 16 however had been chosen for an »apt upgrade«  regular package update. After reboot audio connections using the Web GUI  no longer worked. The »Connecting to echo test ...« window stayed forever:

# telnet 127.0.0.1 8021

Trying 127.0.0.1...

telnet: Unable to connect to remote host: Connection refused

A manual restart solved the problem reproducibly:

# bbb-conf --restart

Restarting BigBlueButton 2.2.15 ...

Stopping BigBlueButton

Starting BigBlueButton

# Potential problems described below

# Error: Found text in freeswitch.log:

#

#    Thread ended for mod_event_socket

#

# FreeSWITCH may not be responding to requests on port 8021 (event socket layer)

# and users may have errors joining audio.

#

.........

root@bbb-16:~# telnet 127.0.0.1 8021

Trying 127.0.0.1...

Connected to 127.0.0.1.

Escape character is '^]'.

Content-Type: auth/request

After system reboot however the problem persists requiring the very same manual restart. The only hint I found so far is a possible race condition being described in https://github.com/bigbluebutton/bigbluebutton/issues/1671#issuecomment-130204115 from 2015. I'm a bit reluctant regarding this to be the cause.

The Ubuntu 16.04 system so far:

bbb-apps                              1:2.2.0-44   

bbb-apps-akka                         2.2.0-86

bbb-apps-screenshare                  1:2.2.0-44  

bbb-apps-sip                          1:2.2.0-11 

bbb-apps-video                        1:2.2.0-41    

bbb-apps-video-broadcast              1:2.2.0-8   

bbb-client                            1:2.2.0-40                

bbb-config                            1:2.2.0-187          

bbb-etherpad                          1:2.2.0-50      

bbb-freeswitch-core                   2:2.2.0-112      

bbb-freeswitch-sounds                 1:1.6.7-6      

bbb-fsesl-akka                        2.2.0-64                   

bbb-html5                             1:2.2.0-933                     

bbb-mkclean                           1:0.8.7-3          

bbb-playback-presentation             1:2.2.0-30    

bbb-record-core                       1:2.2.0-66                 

bbb-red5                              1:1.0.10-16            

bbb-transcode-akka                    2.2.0-8                    

bbb-web                               1:2.2.0-128               

bbb-webrtc-sfu                        1:2.2.0-99          

bigbluebutton                         1:2.2.0-5

[Martin Thomas Schrott]

Hi Martin,

what I could imagine is, that with the apt update your bigbluebutton also was updated, if you had not been on the last version.

and as you did not update via the shell script, you would have to set bbb-conf --setip <host> again manually.

Also a restart of bbb would be necessary after the manual update.

And if there where changes in the .sh script they won't be available ...

so I rather would update bbb with the shell script and only after that do a apt update - though this already would have been done in the install.sh.

but I may fully wrong ;-)

cheers

Martin

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/2cd3fe29-f25a-4766-9623-9d75d6d59fc0%40googlegroups.com.

[Martin Goik]

Hi Martin,

Seems the IPV6 related setting was the culprit. Our network does not support IPV6. I did two consecutive full re-installs until stumbling upon https://docs.bigbluebutton.org/11install.html#freeswitch-fails-to-bind-to-port-8021 for my second time. I did the recommended IPV6 disable steps during the original install but possibly these had been superseded by the subsequent package upgrade replacing files ?. I am however not sure since I purged and cleaned everything BBB related on the host in question before starting a second and third fresh »./bbb-install.sh -v xenial-22 -s ... -d« install again. Disabling IPV6 then solved the still present »reboot« problem but since I purged the original post-update state there might had been a different cause as well.

However: Up and running now!

All the best, Martin

[Fred Dixon]

Hi Martin,

Glad to hear you got it working.  If there is any improvement you think can be made to the docs, please send us a pull request and we'll review.

  https://github.com/bigbluebutton/bigbluebutton.github.io

Regards,.. Fred

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/0610b686-5bdd-4f3f-bcc5-b332e269c157o%40googlegroups.com.

--

BigBlueButton Developer

http://bigbluebutton.org/

Like BigBlueButton?  Tweet us at @bigbluebutton

[TeachReo]

Hello

I found a solution worked  for me

in the file :

/opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml

replace the parameter

<param name="listen-ip" value="::"/>

by

<param name="listen-ip" value="127.0.0.1"/>

Regards

Fabrice