- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi,
I am facing following error after installing Intel CS for WebRTC 3.3 on CentOS Linux release 7.3.1611 (Core)
$ bin/start-all.sh
starting nuve, stdout -> /home/bipin/Release-v3.3/logs/woogeen-nuve.stdout
starting cluster-manager, stdout -> /home/bipin/Release-v3.3/logs/woogeen-cluster-manager.stdout
2017-03-09 11:17:44.950 - INFO: AmqpClient - Connecting to rabbitMQ server: { host: 'localhost', port: 5672 }
2017-03-09 11:17:44.967 - INFO: AmqpClient - Connection to rabbitMQ server error { [Error: connect ECONNREFUSED 127.0.0.1:5672]
code: 'ECONNREFUSED',
errno: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 5672 }
==On same machine I am getting following error on Firefox 45.7============
Run SocketIO sample!! localhost:3001:43:9
POST
XHR
http://localhost:3001/createToken/ [HTTP/1.1 503 Service Unavailable 5ms]
ERROR: server connection failed: invalid token woogeen.sdk.js:8:11752
What could be reason ? Probably I am missing something, please help.
Thank you.
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I used the 3.3 version also have this problem, some people know how to solve?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Check if rabbitmq-server started
service rabbitmq-server status
Thanks
Naresh
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
[root@localhost bin]# service rabbitmq-server status
Status of node rabbit@localhost ...
[{pid,2731},
{running_applications,
[{rabbitmq_management,"RabbitMQ Management Console","3.6.5"},
{rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.6.5"},
{webmachine,"webmachine","1.10.3"},
{mochiweb,"MochiMedia Web Server","2.13.1"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","3.6.5"},
{rabbit,"RabbitMQ","3.6.5"},
{os_mon,"CPO CXC 138 46","2.2.14"},
{ssl,"Erlang/OTP SSL application","5.3.3"},
{public_key,"Public key infrastructure","0.21"},
{crypto,"CRYPTO version 2","3.2"},
{amqp_client,"RabbitMQ AMQP Client","3.6.5"},
{rabbit_common,[],"3.6.5"},
{inets,"INETS CXC 138 49","5.9.8"},
{mnesia,"MNESIA CXC 138 12","4.11"},
{compiler,"ERTS CXC 138 10","4.9.4"},
{xmerl,"XML parser","1.3.6"},
{syntax_tools,"Syntax tools","1.6.13"},
{asn1,"The Erlang ASN1 compiler version 2.0.4","2.0.4"},
{ranch,"Socket acceptor pool for TCP protocols.","1.2.1"},
{sasl,"SASL CXC 138 11","2.3.4"},
{stdlib,"ERTS CXC 138 10","1.19.4"},
{kernel,"ERTS CXC 138 10","2.16.4"}]},
{os,{unix,linux}},
{erlang_version,
"Erlang R16B03-1 (erts-5.10.4) [source] [64-bit] [smp:4:4] [async-threads:64] [hipe] [kernel-poll:true]\n"},
{memory,
[{total,114106384},
{connection_readers,510072},
{connection_writers,280552},
{connection_channels,766200},
{connection_other,850968},
{queue_procs,917880},
{queue_slave_procs,0},
{plugins,2265704},
{other_proc,19315168},
{mnesia,131664},
{mgmt_db,6076208},
{msg_index,67336},
{other_ets,2002664},
{binary,47345696},
{code,27158116},
{atom,992409},
{other_system,5425747}]},
{alarms,[]},
{listeners,[{clustering,25672,"::"},{amqp,5672,"::"}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,1547108352},
{disk_free_limit,50000000},
{disk_free,31858630656},
{file_descriptors,
[{total_limit,924},
{total_used,20},
{sockets_limit,829},
{sockets_used,18}]},
{processes,[{limit,1048576},{used,679}]},
{run_queue,0},
{uptime,21399},
{kernel,{net_ticktime,60}}]
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Seems RabbitMQ works well. Any firewall policy prevent you access localhost:5672?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Seems Guangming's issue is about remote accessing rabbitMQ with guest user, which has been resolved in topic https://software.intel.com/en-us/forums/intel-collaboration-suite-for-webrtc/topic/720316.
Hi. Bipin Kesharwani
Has your problem resolved with single MCU deployment? Have you run init-all.sh --deps to make sure rabbitMQ started before start-all.sh?
Best wishes,
Zhai Lei
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi,
Thanks all for the help and sorry for very late reply. Rabbitmq was not present in the system, installing it solved the issue.
Best Regards,
Bipin Kesharwani
