调查ERROR_LOST_CONNECTION问题

Question

我想知道您如何建议调查暂时性的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可能意味着很多事情)？我有点不知所措，特别是因为这些错误似乎是暂时的，我不能将它们与服务端错误联系起来……

Answer 1

通常，ERROR_LOST_CONNECTION意味着无法访问服务器；通常，这是由网络连接问题引起的。在本例中，错误来自传输层，这意味着我们无法根据getMediaUri请求到达服务器。

您可以通过点击以下urls来增加在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

这将在日志中为您提供更多有关故障期间发生的情况的更多信息。

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