Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).

cant run woogeen basic example correctly

Frank_Z_
Beginner
572 Views

hi,

I just installed the MCU server (v3.1) under CentOS 7.2, and run init.sh, seems correct  as follows:

--------

Initializing mongodb...
MongoDB already running
Initializing nuve configuration...
superServiceId: 5721a1a35357109a5cd6d739
superServiceKey: eFDDADvYQxXvxq3WqJM1e3u4WQmOKGgKuki5fNCc4C9uINJhLT93I+oq6E0hjNv4e1TwnxAKUITQEZRWFTxJHu+Rgp0Wg2wLnbhArdC5+EpOpzPOI7YenW6Dum0bp82nYo7gVrnojGnt3G1pDrW3SJnxmYmdLoOHmyfDT9Y/nMU=
sampleServiceId: 5721a1a45357109a5cd6d73a
sampleServiceKey: zfiJ//bDn6H/HSq5EU2QwwnCrt3ZTVm1WqcfGUkUbudZRG0zpbF/BXLpbJPRtNn7KaC4zvqiKZQmfCW80OLzAhfUvfOovqAODbh0kA9GfrDvCGS5xJvPWoFgHaMEJuIuxsJMEcVlclJvI6tW+B6IJTpx/fXUpEx5Qx4XzL8IjfQ=
Initializing agent configuration...
Initializing agent configuration...

----------

then, when executing start-all.sh ,  it started normally except some strange info come out :

---------

2016-05-03 20:34:42.771  - INFO: AMQPER - Exchange rpcExchange is open
2016-05-03 20:34:42.777  - INFO: AMQPER - Exchange broadcastExchange is open
2016-05-03 20:34:42.783  - INFO: AMQPER - ClientQueue amq.gen-TDR5fbPQmUcAChMbQ3YKGA is open
2016-05-03 20:34:42.788  - INFO: ErizoAgent - Adding agent to cloudhandler, purpose: webrtc
2016-05-03 20:34:42.801  - INFO: LoadCollector - To stop load collector.
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn nload ENOENT
starting rtsp-agent, stdout -> /root/Release-v3.1/logs/woogeen-rtsp-agent.stdout
2016-05-03 20:34:43.790  - INFO: AMQPER - Exchange rpcExchange is open
2016-05-03 20:34:43.795  - INFO: AMQPER - Exchange broadcastExchange is open
2016-05-03 20:34:43.799  - INFO: AMQPER - ClientQueue amq.gen-9wyAlfPCNHz4dx3A6FmSig is open
2016-05-03 20:34:43.803  - INFO: ErizoAgent - Adding agent to cloudhandler, purpose: rtsp
2016-05-03 20:34:43.815  - INFO: LoadCollector - To stop load collector.
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn nload ENOENT
starting recording-agent, stdout -> /root/Release-v3.1/logs/woogeen-recording-agent.stdout

--------------

I dont know if it affect the example

when i input http://192.168.33.48:3001/ in chrome browser, i can get "my camera" correctly, but no  conference stream shows below. the console shows:

------------

This appears to be Chrome
woogeen.sdk.js:8 INFO: user in conference: Object {name: "user", role: "presenter", id: "/#PtV2vIfxPYBvOl9JAAAG", permissions: Object}
woogeen.sdk.js:8 INFO: stream added: 57280e49a2a0f7bb272f5b11
woogeen.sdk.js:8 INFO: subscribing: 57280e49a2a0f7bb272f5b11
woogeen.sdk.js:8 ERROR: 57280e49a2a0f7bb272f5b11 subscribe failed: Failed to get accessing agent.
woogeen.sdk.js:8 INFO: ICE Connection Failed
woogeen.sdk.js:8 ERROR: publish failed: Failed to get accessing agent.

---------------------

what should  I do next?  any ideas?  

Thanks!

 

 

0 Kudos
6 Replies
Frank_Z_
Beginner
572 Views

solved! thanks anyway. 

0 Kudos
saravanan_l_
Beginner
572 Views

Hi,

I frank,

am also facing the same problem ,will be greatful if u provide solution here....

Thank you.

0 Kudos
aakin
Beginner
572 Views

Hello, me too. I mean, I get different message but still, I cant star conference. I get message ERROR: timeout to make rpc to erizoJS

0 Kudos
Chunbo_H_Intel1
Employee
572 Views

Hi Frank,

Could you share your experience here to help others out?

Thanks!

0 Kudos
Frank_Z_
Beginner
572 Views

sorry, just back here

use init.sh -deps instead of  init.sh only.

btw, the reference material related to this product is not enough, especially technology related. if want it popular, just let it open source

0 Kudos
Chunbo_H_Intel1
Employee
572 Views

Thanks, Frank, for your advice.

0 Kudos
Reply