BBB HTML5 Build 196 Video is Not Working

[Kirk Pathumanun]

Hello,

Just upgraded the release package of BBB 2 and BBB HTML5 and all seems fine, however the video on webcam HTML5 doesn't work at all and I already made show that the Kurento Media Server is loaded up in the process. Last time at least it works most of the time with the webcam but as stated it failed completely to load any webcam stream. Please advise thanks.

Regards,

Kirk

[Fred Dixon]

Hi Kirk,

Can you post the output of

  sudo bbb-conf --status

Regards,... Fred

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

--

BigBlueButton Developer

http://bigbluebutton.org/

@bigbluebutton

[Kirk Pathumanun]

Hello Fred,

Here is the output

root@QUESAY:~#  sudo bbb-conf --status
red5: active
tomcat7: active
nginx: active
freeswitch: active
redis-server.service: active
bbb-apps-akka: active
bbb-transcode-akka: active
bbb-fsesl-akka: active
mongod: active
bbb-html5: active
bbb-webrtc-sfu: inactive
kurento-media-server-6.0: active

Regards,

Kirk

On Friday, February 9, 2018 at 11:09:02 AM UTC+7, Fred Dixon wrote:

Hi Kirk,

Can you post the output of

  sudo bbb-conf --status

Regards,... Fred

On Thu, Feb 8, 2018 at 6:24 PM, Kirk Pathumanun <ki...@edknovate.com> wrote:

Hello,

Just upgraded the release package of BBB 2 and BBB HTML5 and all seems fine, however the video on webcam HTML5 doesn't work at all and I already made show that the Kurento Media Server is loaded up in the process. Last time at least it works most of the time with the webcam but as stated it failed completely to load any webcam stream. Please advise thanks.

Regards,

Kirk

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[Kirk Pathumanun]

wait a minute Oh snap this might be it
bbb-webrtc-sfu: inactive

How do I get that to start again ? since bbb-conf --restart didn't do the trick

[Fred Dixon]

Did you do a 

 sudo bbb-conf --setip IP/Hostname

after the upgrade?

Regards,... Fred

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[Kirk Pathumanun]

I did and I double did just to be sure just now. Check the bbb-conf status and still got this

root@QUESAY:~# bbb-conf --status

red5: active
tomcat7: active
nginx: active
freeswitch: active
redis-server.service: active
bbb-apps-akka: active
bbb-transcode-akka: active
bbb-fsesl-akka: active
mongod: active
bbb-html5: active
bbb-webrtc-sfu: inactive
kurento-media-server-6.0: active

Also I did systemctl and got this error

 systemctl status bbb-webrtc-sfu
● bbb-webrtc-sfu.service - BigBlueButton WebRTC SFU
   Loaded: loaded (/usr/lib/systemd/system/bbb-webrtc-sfu.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Fri 2018-02-09 04:15:57 UTC; 1min 29s ago
  Process: 7051 ExecStart=/opt/node-v8.9.0/bin/node server.js (code=exited, status=1/FAILURE)
 Main PID: 7051 (code=exited, status=1/FAILURE)

Feb 09 04:15:57 QUESAY systemd[1]: bbb-webrtc-sfu.service: Unit entered failed state.
Feb 09 04:15:57 QUESAY systemd[1]: bbb-webrtc-sfu.service: Failed with result 'exit-code'.
Feb 09 04:15:57 QUESAY systemd[1]: bbb-webrtc-sfu.service: Service hold-off time over, scheduling restart.
Feb 09 04:15:57 QUESAY systemd[1]: Stopped BigBlueButton WebRTC SFU.
Feb 09 04:15:57 QUESAY systemd[1]: bbb-webrtc-sfu.service: Start request repeated too quickly.
Feb 09 04:15:57 QUESAY systemd[1]: Failed to start BigBlueButton WebRTC SFU.

Regards,

Kirk

[Fred Dixon]

Can you check the contents of 

 /usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml

and ensure the value for <hostname> in

  kurentoUrl: wss://<hostname>/kurento

is actually a hostname, not an an IP address.  Then try

  systemctl restart  bbb-webrtc-sfu

and let us know the results.

Regards,.. Fred

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[Kirk Pathumanun]

Hello,

I did check as you instructed here is the config file parameters

kurentoUrl: wss://quesay.com/kurento
kurentoIp: 198.199.105.11
localIpAddress: 198.199.105.11
acceptSelfSignedCertificate: false
redisHost : "127.0.0.1"
redisPort : "6379"
clientPort : "3008"
minVideoPort: 30000
maxVideoPort: 33000
from-screenshare: "from-screenshare-sfu"
to-screenshare: "to-screenshare-sfu"
from-video: "from-video-sfu"
to-video: "to-video-sfu"
from-audio: "from-audio-sfu"
to-audio: "to-audio-sfu"


did the restart still got this error


root@QUESAY:~# systemctl restart  bbb-webrtc-sfu
root@QUESAY:~# systemctl status  bbb-webrtc-sfu

● bbb-webrtc-sfu.service - BigBlueButton WebRTC SFU
   Loaded: loaded (/usr/lib/systemd/system/bbb-webrtc-sfu.service; enabled; vendor preset: enabled)

   Active: inactive (dead) (Result: exit-code) since Fri 2018-02-09 04:23:49 UTC; 9s ago
  Process: 10799 ExecStart=/opt/node-v8.9.0/bin/node server.js (code=exited, status=1/FAILURE)
 Main PID: 10799 (code=exited, status=1/FAILURE)

Feb 09 04:23:49 QUESAY systemd[1]: bbb-webrtc-sfu.service: Main process exited, code=exited, status=1/FAILURE
Feb 09 04:23:49 QUESAY systemd[1]: bbb-webrtc-sfu.service: Unit entered failed state.
Feb 09 04:23:49 QUESAY systemd[1]: bbb-webrtc-sfu.service: Failed with result 'exit-code'.
Feb 09 04:23:49 QUESAY systemd[1]: bbb-webrtc-sfu.service: Service hold-off time over, scheduling restart.
Feb 09 04:23:49 QUESAY systemd[1]: Stopped BigBlueButton WebRTC SFU.
Feb 09 04:23:49 QUESAY systemd[1]: bbb-webrtc-sfu.service: Start request repeated too quickly.
Feb 09 04:23:49 QUESAY systemd[1]: Failed to start BigBlueButton WebRTC SFU.


Regards,

Kirk

[Kirk Pathumanun]

As per request for the output message here it is:


Feb 08 22:59:03 QUESAY systemd[1]: Started BigBlueButton WebRTC SFU.
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]: WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]: /usr/local/bigbluebutton/bbb-webrtc-sfu/node_modules/config/lib/config.js:181
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     throw new Error('Configuration property "' + property + '" is not defined');
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     ^
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]: Error: Configuration property "log" is not defined
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at Config.get (/usr/local/bigbluebutton/bbb-webrtc-sfu/node_modules/config/lib/config.js:181:11)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at Object.<anonymous> (/usr/local/bigbluebutton/bbb-webrtc-sfu/lib/utils/Logger.js:9:27)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at Module._compile (module.js:635:30)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at Object.Module._extensions..js (module.js:646:10)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at Module.load (module.js:554:32)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at tryModuleLoad (module.js:497:12)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at Function.Module._load (module.js:489:3)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at Module.require (module.js:579:17)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at require (internal/module.js:11:18)
Feb 08 22:59:04 QUESAY bbb-webrtc-sfu[2022]:     at Object.<anonymous> (/usr/local/bigbluebutton/bbb-webrtc-sfu/lib/bbb/pubsub/RedisWrapper.js:14:16)
Feb 08 22:59:04 QUESAY systemd[1]: bbb-webrtc-sfu.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 22:59:04 QUESAY systemd[1]: bbb-webrtc-sfu.service: Unit entered failed state.
Feb 08 22:59:04 QUESAY systemd[1]: bbb-webrtc-sfu.service: Failed with result 'exit-code'.
Feb 08 22:59:04 QUESAY systemd[1]: bbb-webrtc-sfu.service: Service hold-off time over, scheduling restart.
Feb 08 22:59:04 QUESAY systemd[1]: Stopped BigBlueButton WebRTC SFU.
Feb 08 22:59:04 QUESAY systemd[1]: Started BigBlueButton WebRTC SFU.
Feb 08 22:59:05 QUESAY bbb-webrtc-sfu[2058]: WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
Feb 08 22:59:05 QUESAY bbb-webrtc-sfu[2058]: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
Feb 08 22:59:05 QUESAY systemd[1]: bbb-webrtc-sfu.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 22:59:05 QUESAY systemd[1]: bbb-webrtc-sfu.service: Unit entered failed state.
Feb 08 22:59:05 QUESAY systemd[1]: bbb-webrtc-sfu.service: Failed with result 'exit-code'.
Feb 08 22:59:05 QUESAY systemd[1]: bbb-webrtc-sfu.service: Service hold-off time over, scheduling restart.
Feb 08 22:59:05 QUESAY systemd[1]: Stopped BigBlueButton WebRTC SFU.
Feb 08 22:59:05 QUESAY systemd[1]: Started BigBlueButton WebRTC SFU.
Feb 08 22:59:06 QUESAY bbb-webrtc-sfu[2081]: WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
Feb 08 22:59:06 QUESAY bbb-webrtc-sfu[2081]: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
Feb 08 22:59:06 QUESAY systemd[1]: bbb-webrtc-sfu.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 22:59:06 QUESAY systemd[1]: bbb-webrtc-sfu.service: Unit entered failed state.
Feb 08 22:59:06 QUESAY systemd[1]: bbb-webrtc-sfu.service: Failed with result 'exit-code'.
Feb 08 22:59:06 QUESAY systemd[1]: bbb-webrtc-sfu.service: Service hold-off time over, scheduling restart.
Feb 08 22:59:06 QUESAY systemd[1]: Stopped BigBlueButton WebRTC SFU.
Feb 08 22:59:06 QUESAY systemd[1]: Started BigBlueButton WebRTC SFU.
Feb 08 22:59:07 QUESAY bbb-webrtc-sfu[2100]: WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
Feb 08 22:59:07 QUESAY bbb-webrtc-sfu[2100]: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
Feb 08 22:59:07 QUESAY systemd[1]: bbb-webrtc-sfu.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 22:59:07 QUESAY systemd[1]: bbb-webrtc-sfu.service: Unit entered failed state.
Feb 08 22:59:07 QUESAY systemd[1]: bbb-webrtc-sfu.service: Failed with result 'exit-code'.


Regards,

Kirk

[Paulo R. Lanzarin]

Hi Kirk, the logging configuration is missing from the default.yml file. Please open default.example.yml (in the same config folder) and copy the log section to default.yml. That should fix your issue.

--

You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.

[Fred Dixon]

Hi Kirk,

If you update your BigBlueButton 2.0-beta server, the problem starting bbb-webrtc-sfu should now be fixed.

  http://docs.bigbluebutton.org/2.0/20install.html#upgrade-to-latest-build-of-bigbluebuttton-20

Try the update and let us know if it fixes your issue.

Regards,... Fred

[Kirk Pathumanun]

Hello Fred and Paolo,

Thank you kindly for your attention and assistance. Yes will definitely upgrade which is the easiest route for this issue.

Regards,

Kirk

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[Kirk Pathumanun]

Just want to report that after the suggested upgrade from Fred with the fixed default.yml the html5 interface is working great now. I have attached the picture of the test from presenter in Flash to iPad Mini and iPhone6 which of course the html5 webcam works just fine. However none of the mobile devices could see the webcam from the presenter in Flash client. I assume this is still in the work since Fred did mentioned that on the Community Call. Anyway the html5 is pretty stable since we tested over 30 minutes without any issue.

Regards,

Kirk