- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
今天我们生产环境发现房间的 token 创建失败,我们看了nuve,portal,cluster-manager 的日志发现如下相关信息,请帮忙分析是哪里的问题。谢谢!
查看nuve log 发现有如下打印:
2019-05-06 03:22:11.337 - INFO: CloudHandler - Faild in scheduling portal, tokenCode: 39346759040 , keep trying.
2019-05-06 03:22:11.407 - INFO: CloudHandler - Faild in scheduling portal, tokenCode: 17439080317 , keep trying.
2019-05-06 03:22:11.472 - INFO: CloudHandler - Faild in scheduling portal, tokenCode: 54750202303 , keep trying.
2019-05-06 03:22:11.582 - DEBUG: RoomResource - Room 5ccfa78cfefb2301b55f0343 deleted for service 5cadcdcb4b4eaf37f269a6ca
2019-05-06 03:22:11.603 - DEBUG: RoomsResource - Room created: 95_V270466_2019-05-06 11:21:47 for service hc-mcu-3
2019-05-06 03:22:12.208 - INFO: CloudHandler - Faild in scheduling portal, tokenCode: 67086559039 , keep trying.
2019-05-06 03:22:12.243 - INFO: CloudHandler - Faild in scheduling portal, tokenCode: 29199007881 , keep trying.
2019-05-06 03:22:12.338 - INFO: CloudHandler - Faild in scheduling portal, tokenCode: 39346759040 , keep trying.
2019-05-06 03:22:12.408 - INFO: CloudHandler - Faild in scheduling portal, tokenCode: 17439080317 , keep trying.
2019-05-06 03:22:12.473 - INFO: CloudHandler - Faild in scheduling portal, tokenCode: 54750202303 , keep trying.
2019-05-06 03:22:13.210 - INFO: TokensResource - CloudHandler does not respond
2019-05-06 03:22:13.210 - DEBUG: Nuve - { Error: Failed to get portal
name: 'Error',
status: 500,
code: 1301,
data: { error: { code: 1301, message: 'Failed to get portal' } } }
2019-05-06 03:22:13.211 - WARN: Nuve - { Error: Failed to get portal
name: 'Error',
status: 500,
code: 1301,
data: { error: { code: 1301, message: 'Failed to get portal' } } }
然后查看Portal的log,有“Unknown by cluster manager woogeen-cluster” 和 “INFO: Main - portal lost.” 打印
2019-05-06 03:21:12.891 - DEBUG: SocketIOServer - sendMessage, event: progress data: { id: '457673395273724200',
status: 'error',
data: 'Source stream loss' }
2019-05-06 03:21:12.891 - DEBUG: SocketIOServer - notify participant: ZGU70tsmFyWZv16DANl4 event: participant data: { action: 'leave', data: 'kRsz2Io0oVFbiw69ANl3' }
2019-05-06 03:21:12.891 - DEBUG: SocketIOServer - sendMessage, event: participant data: { action: 'leave', data: 'kRsz2Io0oVFbiw69ANl3' }
2019-05-06 03:21:12.891 - INFO: ClusterWorker - Unknown by cluster manager woogeen-cluster
2019-05-06 03:21:12.892 - DEBUG: Portal - participant leave: 1gsME5yDPjyEgiI0ANmg
2019-05-06 03:21:12.892 - DEBUG: SocketIOServer - onClientLeft, id: undefined
2019-05-06 03:21:12.892 - DEBUG: Portal - participant leave: q2N69BavUVUMFaJlANmz
。。。
2019-05-06 03:21:12.893 - DEBUG: Portal - participant leave: kRsz2Io0oVFbiw69ANl3
2019-05-06 03:21:12.893 - DEBUG: SocketIOServer - onClientLeft, id: undefined
2019-05-06 03:21:12.893 - DEBUG: Portal - participant leave: ZGU70tsmFyWZv16DANl4
2019-05-06 03:21:12.893 - DEBUG: SocketIOServer - onClientLeft, id: undefined
2019-05-06 03:21:12.896 - INFO: Main - portal lost.
2019-05-06 03:21:13.069 - DEBUG: SocketIOServer - sendMessage, event: drop data: undefined
2019-05-06 03:21:13.069 - DEBUG: Portal - participant leave: K1_GbKo8TEzK7_DeAAAA
2019-05-06 03:21:13.069 - DEBUG: SocketIOServer - close it, client_id: undefined
继续跟踪cluster-manager 的日志,发现如下的打印:
2019-04-10 11:11:25.657 - INFO: ClusterManager - Run as candidate.
2019-04-10 11:11:25.852 - INFO: ClusterManager - Run as master.
2019-04-10 11:11:25.856 - INFO: ClusterManager - Cluster manager is in service as master!
2019-05-06 03:21:09.473 - INFO: ClusterManager - Worker portal-e20b205253512ef1f85e@hc-mcu-prod.ikandy.cn is not alive any longer, Deleting it.
2019-05-06 03:21:13.114 - WARN: ClusterManager - schedule failed, purpose: portal task: 67086559039 reason: No worker available, all in full load.
2019-05-06 03:21:13.168 - WARN: ClusterManager - schedule failed, purpose: portal task: 29199007881 reason: No worker available, all in full load.
2019-05-06 03:21:13.223 - WARN: ClusterManager - schedule failed, purpose: portal task: 39346759040 reason: No worker available, all in full load.
2019-05-06 03:21:13.322 - WARN: ClusterManager - schedule failed, purpose: portal task: 17439080317 reason: No worker available, all in full load.
2019-05-06 03:21:13.397 - WARN: ClusterManager - schedule failed, purpose: portal task: 54750202303 reason: No worker available, all in full load.
2019-05-06 03:21:14.115 - WARN: ClusterManager - schedule failed, purpose: portal task: 67086559039 reason: No worker available, all in full load.
2019-05-06 03:21:14.169 - WARN: ClusterManager - schedule failed, purpose: portal task: 29199007881 reason: No worker available, all in full load.
2019-05-06 03:21:14.225 - WARN: ClusterManager - schedule failed, purpose: portal task: 39346759040 reason: No worker available, all in full load.
- Tags:
- HTML5
- JavaScript*
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
部分模块的机子没连上cluster

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page