0

我想知道您会如何建议调查瞬态ERROR_LOST_CONNECTION问题。这个周末我经历了很多，所以我去了扬声器上的 anacapa.trace 日志，得到了很多这样的行：

[Thu Jan  8 22:24:37 1970] <diag:chsrc,0> Transport error ERROR_LOST_CONNECTION for account type 40711, URI: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, friendly name: Void (Radio Edit), share/server: ..., path: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, extra info: , http: -1, framer: mp3
[Thu Jan  8 22:24:48 1970] <diag:chsrc,0> Transport error ERROR_LOST_CONNECTION for account type 40711, URI: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, friendly name: Pirate Games, share/server: ..., path: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, extra info: , http: -1, framer: mp3
[Thu Jan  8 22:24:59 1970] <diag:chsrc,0> Transport error ERROR_LOST_CONNECTION for account type 40711, URI: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, friendly name: Boondocks, share/server: ..., path: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, extra info: , http: -1, framer: mp3
[Thu Jan  8 22:25:12 1970] <diag:upnpeventing,1> Canceled subscription uuid:RINCON_B8E93729083201400_sub0000000074 to AVTransport svc (6 failures outstanding)
[Thu Jan  8 22:25:14 1970] <diag:chsrc,0> Transport error ERROR_LOST_CONNECTION for account type 40711, URI: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, friendly name: Time Again (Radio Edit), share/server: ..., path: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, extra info: , http: -1, framer: mp3
[Thu Jan  8 22:25:18 1970] <diag:trackplaymonitor,1> notifyEvent ignoring TPM_CHSNK_TRACK_BOUNDARY during 16 past buffered tracks: time: 685503:981882
[Thu Jan  8 22:26:07 1970] <diag:chsrc,0> Transport error ERROR_LOST_CONNECTION for account type 40711, URI: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, friendly name: Eistee aus der Dose, share/server: ..., path: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, extra info: , http: -1, framer: mp3
[Thu Jan  8 22:26:18 1970] <diag:chsrc,0> Transport error ERROR_LOST_CONNECTION for account type 40711, URI: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, friendly name: Outback, share/server: ..., path: x-sonosprog-http:....mp3?sid=159&flags=8224&sn=3, extra info: , http: -1, framer: mp3
[Thu Jan  8 22:26:33 1970] <diag:upnpeventing,1> 2 failure(s) sending event to 192.168.0.14:3400.  Retry in 10 secs: 1
[Thu Jan  8 22:26:48 1970] <diag:upnpeventing,1> 3 failure(s) sending event to 192.168.0.14:3400.  Retry in 20 secs: 1
[Thu Jan  8 22:27:13 1970] <diag:upnpeventing,1> 4 failure(s) sending event to 192.168.0.14:3400.  Retry in 40 secs: 1
[Thu Jan  8 22:27:58 1970] <diag:upnpeventing,1> 5 failure(s) sending event to 192.168.0.14:3400.  Retry in 80 secs: 1
[Thu Jan  8 22:29:23 1970] <diag:upnpeventing,1> 6 failure(s) sending event to 192.168.0.14:3400.  Retry in 160 secs: 1
[Thu Jan  8 22:32:08 1970] <diag:upnpeventing,1> 7 failure(s) sending event to 192.168.0.14:3400.  Retry in 160 secs: 0
[Thu Jan  8 22:32:08 1970] <diag:upnpeventing,0> Terminated subscription #69 for 192.168.0.14:3400

我搜索了服务端日志，但没有发现任何问题，而且大多数时候我什至找不到getMediaURI调用这些轨道的日志行，所以由于某种原因，它们没有进入服务代码.

有没有办法获得更多有用的客户端日志（比如对服务的请求和它得到的响应）？或者我可以从当前日志中提取哪些信息（ERROR_LOST_CONNECTION可能意味着很多事情）？我有点不知所措，特别是因为这些错误似乎是暂时的，我无法将它们与服务端错误联系起来......

4

1 回答 1

0

通常 ERROR_LOST_CONNECTION 意味着无法访问服务器；通常这些是由网络连接问题引起的。在这种情况下，错误来自传输层，这意味着我们无法通过getMediaUri请求到达服务器。

您可以通过点击以下网址来增加您在 anacapa.trace 文件中看到的日志记录： http:// IP_address_of_ZonePlayer:1400/diaglevel?module=chsrc&level=5 http:// IP_address_of_ZonePlayer:1400/diaglevel?module=soap&level=5 http: // IP_address_of_ZonePlayer:1400/diaglevel?module=sonoscp&level=5

这将为您提供更多有关日志失败期间发生的情况的更多信息。

另一种查看您想要的内容的方法是使用具有端口镜像的交换机，因为这将允许您完整查看传入和传出流量。

于 2015-11-01T19:33:24.200 回答