我想知道您如何建议调查暂时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
可能意味着很多事情)?我有点不知所措,特别是因为那些错误似乎是暂时的,我无法将它们与服务端错误相关联......
答案 0 :(得分:0)
通常,ERROR_LOST_CONNECTION意味着无法访问服务器;通常这些是由网络连接问题引起的。在这种情况下,错误来自传输层,这意味着我们无法在getMediaUri
请求上访问服务器。
您可以通过点击以下网址来增加您在anacapa.trace文件中看到的日志记录:
HTTP:// IP_address_of_ZonePlayer
:1400 / DIAGLEVEL模块= chsrc&安培;电平= 5
HTTP:// IP_address_of_ZonePlayer
:1400 / DIAGLEVEL模块=皂&安培;电平= 5
HTTP:// IP_address_of_ZonePlayer
:1400 / DIAGLEVEL模块= sonoscp&安培;电平= 5
这将为您提供有关日志中失败期间所发生情况的更多信息。
另一种查看您想要的方法是使用具有端口镜像功能的交换机,这样您就可以完全看到传入和传出的流量。