Customer has recorded a lot of data and included them in his email responses to Right Now ticket # 090227-000973.

I don't have access to RN.  If this is about rebuffering, it's most likely just the nature of the Internet, you cannot stream forever, eventually you will need to rebuffer.

(In reply to comment #2)
> I don't have access to RN.  If this is about rebuffering, it's most likely just
> the nature of the Internet, you cannot stream forever, eventually you will need
> to rebuffer.

What you say may be true in some circumstances but I have the Squeezebox operating alongside of a similar device, a Roku Soundbridge. The Soundbridge plays without interruption when tuned to either the same station at the Squeezebox or other stations.

Andy: Could this be related to the RadioTime Packet Flood issue?

No.

BTW: I have tested here in the office, a Boom has been playing KQED for 4 days
with no interruption.  I'm connected to SqueezeNetwork, not SqueezeCenter.

Ken: Can you please re-test while you are connected to Squeezenetwork to see if
the same issue happens for you.

James:

Thank you for the followup. I always only use SqueezeNetwork, since I prefer to not have to keep my computer "awake" 24 hours/day. I feed my Squeezebox via WiFi from an Apple Airport Express located approximately six feet from both my Squeezebox and my Roku Soundbridge.

For testing purposes would you prefer that I tune to KQED rather than either KFI or KGO? I wouldn't think it wouldn't make and difference.

Although I do not normally listen to KQED, I will tune my Squeezebox to that station and keep a log of what I observe.

On your airport express, what are the wireless options set to?

First, status on my KQED reception:
Tuned my Squeezebox to KQED at 2000 hours 26 Mar

0740 hours 27MAR Elapsed Time  11:43
1350 hours 27MAR Elapsed Time  05:49

This would imply that the Squeezebox restarted at approximately 0800 hours today.

The AirportExpress Settings (not sure which ones you meant):

Wireless Mode: Participate in a WDS Network
Wireless Security: None
Channel: 10
Connect Using: Airport(WDS)
Radio Mode: 802.11 b/g compatible
MAC address: Not Enabled

How this answers your question. If not please let me know.

My WiFi configuration is as follows:

--telephone line(RJ-11)-->2Wire 2701HG-B DSL Router/Modem--Ethernet-->AirPort Extreme--WiFi-->AirPort Express--WiFi-->Squeezebox & Roku Soundbridge

Note: Last week I connected my Squeezebox to the AirPort Extreme via an Ethernet cable and encountered the problem with KFI just "STOPPED". It remained in the "STOPPED" mode until I manually pressed "Play". Not the same situation as with the KQED configuration, which apparently restarted spontaneously.

Try setting "Radio Station Buffer Seconds" set to 10 to see if it changes the behavior of this error for you?

IF not, set it back to 30 and try changing "Maximum WMA Stream Bitrate" to 96 kbps or 128 kbps

I tried responding via email I just received a "bounce" message. Here is what was in my email:



To: jrichardson@slimdevices.com
From: Ken W <kwbear@bellsouth.net>
Subject: Re: BUG 11388 information request
Cc: 
Bcc: 

At 9:02 AM -0700 3/30/09, James Richardson wrote with great perspicuity:

Ken: can you email me your AirPort Config File:  AirPort Utility > File > Save a Copy As (do not include passwords)

I believe I've attached the file you requested. When I opened Airport Utility V. 5.4.1 the left panel displayed both my Airport Express and Ken and Jens Network (the name of my WiFi network) but the Save As... was grayed out. By double-clicking on the AirportExtreme I managed to open a Summary panel and I then could save was, hopefully,  what you need.


Also, email me the MAC address of your SB Boom.

I don't believe I have a Squeezebox Boom. My device is a Squeezebox Classic. (930-000009)

The MAC Address is:  00:04:20:07:F4:7A

  I tried to find KFI but don't know if I have the proper station location.  Can you include the HTTP address you are using to get to that feed?

The URL, copied from my Squeezebox is:
<http://opml.radiotime.com/Tune.ashx?id=s32618&Username=sampletime&PartnerID=16>

(I checked with a Browser and it appears to connect to KFI correctly.)

Let me know if you need any more information.

Also a status update:

30MAR 0830 hours Display shows KFI, elapsed time frozen at 9:19:19 and no activity on the spectrum display or audio output. No error message displayed.

Pressed "Play", screen brightens but no other activity.

Pressed "Now playing" no response.

Pressed "Play" again and output resumes but with a full-panel spectrum analyzer display. I normally have the spectrum display showing in the small area on the right side of the display.

NEW UPDATE:

01APR 0835 hours Display indicated Date/Time (standby mode?) Squeezebox was operating normally at 0730 hours.

Pressed "Play" Display indicates KFI Elapsed time 00:00 - no output
Pressed "Play" second time KFI starts - output indicated as normal

01APR 1230 hours  Elapsed Time: 03:51 (KFI playing)
01APR 2105 hours Elapsed Time: 12:28 NO output, no error message
Pressed "Play" twice KFI started to play

02APR 0830 Elapsed time 10:10 (frozen) - Display indicated "NOW PLAYING" but no output.

Pressed "Play" twice KFI output resumes

Note: 02APR 0715 KFI was playing.

Unfortunately, my Squeezebox continues to exhibit the original problem, namely, stopping during the the receiption of various broadcast channels. The unit will play a given channel from anywhere from a hour or so up to 25 hours or more. I've tried tuning to stations such as KGO, KFI and KQED, Pandora channels and Internet Radio stations.

All seem to exhibit the same problem. When I output stops the indication (after I press "Play") is "STOPPED". The Squeezebox display shows the screensaver until I press "Play". Pressing "Play" a second times causes the channel to reconnect.

My Roku Soundbridge does not exhibit the same problem.

Any suggestions for troubleshooting would be welcome. Is it possible that my Squeezebox is defective?

No reply to my post #12 of April 16.

My problem continues. Please help.

To clarify, the main bug here is that something has happened to the stream that the player has not detected and communicated with the server about.

Andy points out that we have thousands of commercial customers that play around the clock without seeing this issue.  The commercial customers will try to restart after the server detects a drop, but in this case no drop is being detected.

This user only uses Squeezenetwork.

QA will try to repro this on SC so that we can get logs: player.Streaming.direct and player.source

(In reply to comment #14)
> To clarify, the main bug here is that something has happened to the stream that
> the player has not detected and communicated with the server about.
> 
> Andy points out that we have thousands of commercial customers that play around
> the clock without seeing this issue.  The commercial customers will try to
> restart after the server detects a drop, but in this case no drop is being
> detected.
> 
> This user only uses Squeezenetwork.
> 
> QA will try to repro this on SC so that we can get logs:
> player.Streaming.direct and player.source

As of today, 7 May 2009, the problem continues. What I am doing now is tuning both my Squeezebox and a competitor's device (a Roku Soundbridge) to radio station KGO. KGO is left on the Roku continuously and does not stop for disconnect. So far the Squeezebox has stopped once when turned to KGO after approximately five hours.

Both the Squeezebox and the Roku receive their signal from an Apple Express WiFi unit located approximately three feet away.

(In reply to comment #15)

Since I haven't received any response to my prior post I called Level 2 Tech Support yesterday, 12May2009. While they could not determine the source of my problem either, they did suggest that I employ packet-sniffing to gather more data.Since Wireshark will not work on my computer (1.25 GHz G4 Power Mac with OS 10.4.11 - Tiger) I agreed to research a suitable packet-sniffer that would work on my machine. I found an application called "packetpeeper" at <http://sourceforge.net/projects/packetpeeper> and installed and activated it but now that I have I have no idea with what to do with the data it is collecting. Can you help?

It continues to collect data that appears to be very interesting, but what do I do now? I can save the data as a TCP dump. But what then? The file continues to build in size.

I look forward to any advice you can supply.

Ken: please connect your SB3 to your router via Ethernet and try your test again.

As for the logs, you may want to filter them by the IP address of your SB3, this will keep them small and provide some useful data

(In reply to comment #17)
> Ken: please connect your SB3 to your router via Ethernet and try your test
> again.
> 
By connecting to the Router do you mean I need to physically connect to my 2Wire 2701 ? If so, that presents a problem with setup since it is physically located a distance away from other equipment I use with my Squeezebox. If you mean that I connect, via ethernet, to my Airport Express, that is easily accomplished.

> As for the logs, you may want to filter them by the IP address of your SB3,
> this will keep them small and provide some useful data

Unfortunately, I've tried to configure a filter in Packet Peeper without success. I've looked for setup information onine and have not found any.I fear I'm stuck.The IP address for my Squeezebox is: 192.168.1.66, but the filter setup asks for an ethernet address. I believe that is 00:04:20:f4:7a for the Squeezebox. but when I enter that into the filter setup I receive the messing "parsing error". Sorry, I'm stuck at this point.

(In reply to comment #18)
> (In reply to comment #17)
> > Ken: please connect your SB3 to your router via Ethernet and try your test
> > again.
> > 
> By connecting to the Router do you mean I need to physically connect to my
> 2Wire 2701 ? If so, that presents a problem with setup since it is physically
> located a distance away from other equipment I use with my Squeezebox. If you
> mean that I connect, via ethernet, to my Airport Express, that is easily
> accomplished.

Connect the SB3 to your Airport Express, do a Factory Reset, Connect it to your network and SqueezeNetwork again.


> 
> > As for the logs, you may want to filter them by the IP address of your SB3,
> > this will keep them small and provide some useful data
> 
> Unfortunately, I've tried to configure a filter in Packet Peeper without
> success. I've looked for setup information onine and have not found any.I fear
> I'm stuck.The IP address for my Squeezebox is: 192.168.1.66, but the filter
> setup asks for an ethernet address. I believe that is 00:04:20:f4:7a for the
> Squeezebox. but when I enter that into the filter setup I receive the messing
> "parsing error". Sorry, I'm stuck at this point.

The Ethernet Address appears to be the MAC 00:04:20:f4:7a number.  I am not familiar with Packet Peeper, but will download it and attempt to use it to see if it will help in this case or not.

(In reply to comment #19)
> (In reply to comment #18)
> > (In reply to comment #17)
> > > Ken: please connect your SB3 to your router via Ethernet and try your test
> > > again.
> > > 
> > By connecting to the Router do you mean I need to physically connect to my
> > 2Wire 2701 ? If so, that presents a problem with setup since it is physically
> > located a distance away from other equipment I use with my Squeezebox. If you
> > mean that I connect, via ethernet, to my Airport Express, that is easily
> > accomplished.
> 
> Connect the SB3 to your Airport Express, do a Factory Reset, Connect it to your
> network and SqueezeNetwork again.
> 
> 
> > 
> > > As for the logs, you may want to filter them by the IP address of your SB3,
> > > this will keep them small and provide some useful data
> > 
> > Unfortunately, I've tried to configure a filter in Packet Peeper without
> > success. I've looked for setup information online and have not found any.I fear
> > I'm stuck.The IP address for my Squeezebox is: 192.168.1.66, but the filter
> > setup asks for an Ethernet address. I believe that is 00:04:20:f4:7a for the
> > Squeezebox. but when I enter that into the filter setup I receive the messing
> > "parsing error". Sorry, I'm stuck at this point.
> 
> The Ethernet Address appears to be the MAC 00:04:20:f4:7a number.  I am not
> familiar with Packet Peeper, but will download it and attempt to use it to see
> if it will help in this case or not.

Typo on my part. The MAC/Ethernet Address is actually 00:04:20:07:f4:7a. I did as you suggested and Factory Reset the Airport Express <http://support.apple.com/kb/HT1450> and restarted the Squeezebox and it for an Ethernet connection.  Since the initial connection the radio station has STOPPED twice. In other words it's the same as with the WiFi Connection.

Have you had a chance to try Packet Peeper? Any other tests you'd like me to perform, just let me know. I'll leave the Ethernet connection until I hear from you. I appreciate your patience and help.

Here is the next experiment I would like you to try.

Leave your SB3 wired to your Airport
Down load and Install SC 7.3.3 to one of your computers
Enter your SN credentials during the setup process
Move your SB3 from SN to SC
Enable Logging : SqueezeCenter > Settings > Advanced > Logging > Log Set = Internet Radio

This will create a Server Log with lots of data.  Continue to test, generate the error condition, then attach the log file to this report

I am still investigating Packet Peeper so I'll have to get back with you on that one next week.

(In reply to comment #21)
> Here is the next experiment I would like you to try.
> 
> Leave your SB3 wired to your Airport
> Down load and Install SC 7.3.3 to one of your computers
> Enter your SN credentials during the setup process
> Move your SB3 from SN to SC
> Enable Logging : SqueezeCenter > Settings > Advanced > Logging > Log Set =
> Internet Radio
> 
> This will create a Server Log with lots of data.  Continue to test, generate
> the error condition, then attach the log file to this report
> 
> I am still investigating Packet Peeper so I'll have to get back with you on
> that one next week.

I already have SqueezeCenter 7.3.2 installed - although I haven't used it. I have been using SqueezeNetwork exclusively. I'll be happy to install and test with SqueezeCenter 7.3.3 though.

I've been unable to find SC7.3.3. Can you provide a link?

Sorry, I should have given you the link to the beta download.  You can get 7.3.3 from this location:

http://downloads.slimdevices.com/nightly/?ver=7.3

Also, there is no need to click [reply] when entering bugs, simply type you new comments in the Additional Comments: box :)  Bugzilla keeps and shows the history.

Depending on your operating system, the LOG file will be located in different locations.  You can see where your log file is by going to Settings > Advanced > Information.  On that page, it should show you the location of your log file.

To attach the log file to this bug, click on 'Add an attachment" above, then follow the dialog.

Ooops! Installed 7.3.3 without a problem but there are two Log files: "SqueezeCenter Log File" and "Scanner Log File". I assume you mean the SqueezeCenter Log File but want to confirm.

I just looked in the Log location and there are three files:

perfmon.log
scanner.log
server.log

No, SqueezeCenter Log File.

Also, should I keep my SB connected to my Airport Express via Ethernet? I eventually would like to return to the wireless connection.

server.log please

You don't need to keep it connected to your Airport via Ethernet, I just wanted to eliminate 802.11 as a source.  Once you are done with the test, you can move it back to wireless.

Roger!

How long should we collect the log data? Until I encounter one or more STOPPED events or data stream interrupts?

Should I clear the log at this point to start with a clean data set?

Starting with a clean log would be good.

If you select 'Save logging settings for use at next application restart' after you set the debug logs, then you can safely stop and start the server.

To make a clean log...stop the server, delete the server.log file, then start the server again.

Get to your first stop event, then shut down the server and attach the server.log file to this bug.

In your last message to me you suggested: "If you select 'Save logging settings for use at next application restart' after you set the debug logs, then you can safely stop and start the server."

I know how to stop and start the Server but where/how do I select 'Save logging settings for use..." and how to I 'set the debug logs'?

I looked and cannot find where I perform those actions. Also, should I just send the log after one or after many interrupts?

Sorry to be so dense!

Enable Logging:
 In SqueezeCenter select Settings > Advanced > Logging > Log Set =
Internet Radio

 On that same page, also select "Save logging settings for use at next application restart"
--------------------
You should also perform a Factory Reset on your SB3, after you have attached it by Ethernet to your Airport.

On the SB3, using the IR remote, press and HOLD the Left Arrow button until you get to the setup menu.
Select Setup Networking.
Select Connect to Ethernet network, and continue through the setup menu.

When I set Log Set to "Internet Radio" and click "Apply" the pulldown menu reverts to "Please select log set..."

All other setup advice has been performed without a problem.

Problems with the 7.3.3 beta?

Not really, it's by design to go back to the selector menu item.

Created attachment 5240 [details]
server.log file

Should I reset (delete) the current log file or continue to collect data on the current file? Good luck!

Get one more data failure point in the log, then start over with a fresh log please

Andy: is there anything in the log that may help diagnose the issue?

Created attachment 5242 [details]
server.log as of 20May 0650PDST

I will delete this server log and start afreash with the Squeezebox tuned to KGO.

Created attachment 5243 [details]
server.log file midday 20 May2009

Since switching to KGO yesterday the dropouts have increased significantly. Should I continue to collect data via the Ethernet connection?

Any thoughts on the source of this problem?

Ken:  Thank you for the logs.  Lets change the logging set to a different setting.

Reset the Logging Preference (via the drop down)
Scroll down to (player.source) - Player Source Audio & Conversion Logging then set that to Debug -- all other logs should be set to Error (default)
Select Save Logging (if its not already)
Click Apply
Stop the server
Delete the log(s)
Start the server again, and start testing

Lets get 2 logs this time, one with the SB3 attached to Ethernet and one Wireless

After this round of logs, you can put the unit back into it's normal spot, and you can connect it again to SqueezeNetwork.

James:

Thanks for your guidance. I've started the setup with Ethernet and the Debug configured. How long would you like me to run Ethernet and then WiFi? 

BTW: Test has started 2009-05-26 1215 PDST.

Best wishes,

Ken Workman

Created attachment 5282 [details]
server.log 26-27MAY 2009 (Ethernet connection)

Here is the ZIPed source.log for my SB3 for 26-27MAY using the Squeezecenter and the setup configuration you suggested.

Note: During this logging period the Roku Soundbridge, connected wirelessly to the same Airport Express did not experience any dropouts.

Configuration: 1.25 GHz G4 Power Mac, OS 10.4.11

Alan: your thoughts on this?

Created attachment 5288 [details]
server.log 29MAY2009 (wireless connection)

Something tells me this part of the test needs to be repeated.

Haven't heard from you in a while. Problem still persists, but a strange message appeared this morning. The SB was stopped with the following message on the screen: "Connection reset by remote host". I don't believe I've ever seen this message previously. Is Logitech working behind the scenes to troubleshoot my Squeezebox?

We are always fixing issues on the back end.  The message "Connection reset by remote host" is generated when there is an error from the host source.

We will be working to improve our messaging to the end user when these types of situations occur.

I'm going to mark this bug as closed. The error condition is generated by the host and our products are functioning as designed when the error condition is encountered.

When a host drops the stream for any reason, our products will not 'auto tune' into the station again.  This is more then likely the cause of the issues you have been experiencing.
------------------------------------------------------------------------
If you would like that feature added, please open a new Enhancement bug requesting that feature.

Jim:

I'm puzzled! The message "Connection reset by remote host" was received only once on the morning of June 4. Does this imply that the stopping of the data streams that have been going on previously were due to the same cause but didn't result in a similar message? 

Also, I do not experience similar outages with the Roku Soundbridge even when I tune both the Roku and my Squeezebox to the same station. This seems to say that the software/firmware in the SB does not 'auto tune' but that in the Roku does. I hate to say it, but if this is the case wouldn't I be better off with a second Roku Soundbridge?

It doesn't seem that the issue has been resolved.

*** This bug has been marked as a duplicate of bug 5115 ***

Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version.  If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.