Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
mherger wrote: > >> Awesome. Thanks, bpa and philippe_44 for helping to analyze and fix > >> this. Can you check in this change to the repository of LMS 8? > > Thanks guys! I committed this change to LMS8. It'll be out there in a > bit. Please let me know if I got it the wrong way :-) > > -- > > Michael Michael, as responsive as ever! Thanks, I updated and can confirm that you got it right. :-) schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
Awesome. Thanks, bpa and philippe_44 for helping to analyze and fix this. Can you check in this change to the repository of LMS 8? Thanks guys! I committed this change to LMS8. It'll be out there in a bit. Please let me know if I got it the wrong way :-) -- Michael ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > Now it works!!! I cannot produce any dead connections any more. They are > all closed after the timeout. The log shows that. > > Awesome. Thanks, bpa and philippe_44 for helping to analyze and fix > this. Can you check in this change to the repository of LMS 8? That's great. It's good that Philippe got involved - he knows that part of LMS v. well and been making significant improvements. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
Here is the log file. I had the timeout first set to 8 seconds. [20-08-21 08:55:34.2418] First, I reproduced the case of getting no body data from the server. [20-08-21 09:04:55.9254] Then, I tried "normal" internet radio stations [20-08-21 09:23:16.0842] Then, I gave my own server "normal" signal again and tried the working case, but this time with a very tough timeout of 1 second. Everything working well. +---+ |Filename: server.log-2.txt | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=31338| +---+ schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
I got it running. There was a $self-> in the setTimer line missing. I
inserted a log command to check:
Code:
# After reading headers, some callers may want to continue and
# read the body
sub read_body {
my $self = shift;
my $args = shift;
$self->socket->set( passthrough => [ $self, $args ] );
# Timer in case the server never sends any body data
my $timeout = $self->timeout || $prefs->get('remotestreamtimeout');
Slim::Utils::Timers::setTimer( $self->socket, Time::HiRes::time() + $timeout,
\&_http_read_timeout, $self, $args );
$log->debug("Set read body timeout to " . $timeout);
Slim::Networking::Select::addError( $self->socket, \&_http_socket_error );
Slim::Networking::Select::addRead( $self->socket, \&_http_read_body );
}
Now it works!!! I cannot produce any dead connections any more. They are
all closed after the timeout.
Awesome. Thanks, bpa and philippe_44 for helping to analyze and fix
this. Can you check in this change to the repository of LMS 8?
schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557
View this thread: http://forums.slimdevices.com/showthread.php?t=112774
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
I got the info how to change HTTP.pm. Unfortunately, LMS does not start with the change. I double checked several times. Can you check again? schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
I have found the file but in fact I could not figure out how to write on it. Posted forum question. I am back from my vacation, but fortunately, I found I way how to reproduce this also at home. I have a similar setup here. In fact, by insanely trying different satellite radio channels and making sat signal quality very bad, I could produce 5 dead and persisting connections. I will come back once I know how to write on HTTP.pm. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > I think I know how to mount that partition. Nothing needs to be > compiled? (Sorry, I am not familiar at all with the LMS tool chain). No, no compilation for that part LMS 7.9 on Pi 3B+ & Odroid-C2 - *SqueezeAMP!*, 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, Riva 1 & 3 philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
philippe_44 wrote: > You should but I dont remember how to access the non RO partition. Ask > a question on the picore thread I think I know how to mount that partition. Nothing needs to be compiled? (Sorry, I am not familiar at all with the LMS tool chain). schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > Can I do it on a piCorePlayer system? You should but I dont remember how to access the non RO partition. Ask a question on the picore thread LMS 7.9 on Pi 3B+ & Odroid-C2 - *SqueezeAMP!*, 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, Riva 1 & 3 philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
philippe_44 wrote:
> That's interesting... If you know how to do that, can you edit file
> /usr/share/perl5/Slim/Networking/Async/HTTP.pm, go to function
> "read_body" and replace with
>
> >
Code:
> >
> # After reading headers, some callers may want to continue and
> # read the body
> sub read_body {
> my $self = shift;
> my $args = shift;
>
> $self->socket->set( passthrough => [ $self, $args ] );
>
> # Timer in case the server never sends any body data
> my $timeout = $self->timeout || $prefs->get('remotestreamtimeout');
> Slim::Utils::Timers::setTimer( $socket, Time::HiRes::time() + $timeout,
\&_http_read_timeout, $self, $args );
>
> Slim::Networking::Select::addError( $self->socket, \&_http_socket_error
);
> Slim::Networking::Select::addRead( $self->socket, \&_http_read_body );
> }
>
> >
Can I do it on a piCorePlayer system?
schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557
View this thread: http://forums.slimdevices.com/showthread.php?t=112774
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote:
> Actually I added Reliable plugin only yesterday to see whether this
> could help - it did not do anything to my specific problem.
>
> Anyway, I did it again with Reliabe Plugin deactivated. This time, it
> took a little more channel switches to reproduce the situation where the
> server does not provide audio.
>
> I see the HTTP=GLOB(0x6021268) being connected, but not disconnected.
That's interesting... If you know how to do that, can you edit file
Networking::Async::HTTP.pm, go to function "read_body" and replace with
Code:
# After reading headers, some callers may want to continue and
# read the body
sub read_body {
my $self = shift;
my $args = shift;
$self->socket->set( passthrough => [ $self, $args ] );
# Timer in case the server never sends any body data
my $timeout = $self->timeout || $prefs->get('remotestreamtimeout');
Slim::Utils::Timers::setTimer( $self->socket, Time::HiRes::time() +
$timeout, \&_http_socket_error, $self, $args );
Slim::Networking::Select::addError( $self->socket, \&_http_socket_error
);
Slim::Networking::Select::addRead( $self->socket, \&_http_read_body );
}
LMS 7.9 on Pi 3B+ & Odroid-C2 - *SqueezeAMP!*, 5xRadio, 3xBoom, 4xDuet,
1xTouch, 1 SB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000,
ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2,
Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5,
Riva 1 & 3
philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=112774
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
philippe_44 wrote: > For mp3 or any stream? Because for mp3, they do by design I seem to have only MP3 with my local server. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > In my logs, it seems that the "scanning" http connection and the real > "playing" (in a working case where the server provides a valid audio > stream) overlap for a couple of seconds. For mp3 or any stream? Because for mp3, they do by design LMS 7.9 on Pi 3B+ & Odroid-C2 - *SqueezeAMP!*, 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, Riva 1 & 3 philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
philippe_44 wrote: > Ive updated that section of LMS heavily recently. I will read this > thread but LMS does close any connection used for scanning. For most > formats, scanning has to be done before streaming starts. Only mostly in > mp3 is there streaming in parallel with scanning (and in HTTP only, not > in HTTPS). > In my logs, it seems that the "scanning" http connection and the real "playing" (in a working case where the server provides a valid audio stream) overlap for a couple of seconds. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
I will try a summary: I can reproduce a case where LMS does not close this first "scanning" Http connection. This occurs in case the server accepts the connection, but does not provide an audio stream. Player state remains buffering, and LMS does not close its connection. No matter what I do afterwards, the connection remains unless the server side closes it or LMS is restarted. And: it is http. Whether it is MP3 I am not sure, but I think you will find out reading the server logs attached above. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
I will try a summary: I can reproduce a case where LMS does not close this first "scanning" Http connection. This occurs in case the server accepts the connection, but does not provide an audio stream. Player state remains buffering, and LMS does not close its connection. No matter what I do afterwards, the connection remains unless the server side closes it or LMS is restarted. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > Maybe I am thinking too simply, but to me it's quite clear now: > > We have to check the section where LMS reads a first portion of the > stream in order to get info about bitrate, codec and so on. The > conditions to close that http connection by calling > Slim::Networking::Async::disconnect have to be reviewed. At latest when > the same player wants to stream or play something else, the connection > has to be closed. Or, in other words, LMS has to make sure that it does > not keep multiple HTTP connections "serving" one player. > > Do you agree? > > I can try to do it when I am at home after tomorrow, but I have never > really seen a single line of code of LMS and after today, I cannot test > it under these special circumstances. Ive updated that section of LMS heavily recently. I will read this thread but LMS does close any connection used for scanning. For most formats, scanning has to be done before streaming starts. Only mostly in mp3 is there streaming in parallel with scanning (and in HTTP only? Not in HTTPS). But can you do a summary of what makes you think that a change is needed? LMS 7.9 on Pi 3B+ & Odroid-C2 - *SqueezeAMP!*, 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, Riva 1 & 3 philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
Maybe I am thinking too simply, but to me it's quite clear now: We have to check the section where LMS reads a first portion of the stream in order to get info about bitrate, codec and so on. The conditions to close that http connection by calling Slim::Networking::Async::disconnect have to be reviewed. At latest when the same player wants to stream or play something else, the connection has to be closed. I can try to do it when I am at home after tomorrow, but I have never seen a single line of code of LMS and after today, I cannot test it under these special circumstances. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
OK, now with netstat -p: Normal working case: Code: Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp1 0 collePlayer:43002 collePlayer:9000 CLOSE_WAIT 8562/sbpd tcp0 0 collePlayer:9000collePlayer:43002 FIN_WAIT2 - tcp0 0 192.168.0.102:445 192.168.0.101:55656 ESTABLISHED 9105/smbd tcp0 0 collePlayer:3483collePlayer:56528 ESTABLISHED 7148/perl tcp0 0 collePlayer:56528 collePlayer:3483 ESTABLISHED 8480/squeezelite tcp0 0 192.168.0.102:35144 192.168.0.102:9000 ESTABLISHED 9094/jivelite tcp0 0 192.168.0.102:9000 192.168.0.102:35144 ESTABLISHED 7148/perl tcp0208 192.168.0.102:ssh 192.168.0.101:55663 ESTABLISHED 9114/sshd: tc [priv tcp0 0 collePlayer:53236 collePlayer: ESTABLISHED 8562/sbpd tcp0 0 192.168.0.102:35190 192.168.0.102:9000 ESTABLISHED 9094/jivelite tcp0 0 192.168.0.102:445 192.168.0.101:55657 ESTABLISHED 9107/smbd tcp0 0 192.168.0.102:38244 192.168.0.100:3000 ESTABLISHED 8480/squeezelite tcp0 0 192.168.0.102:9000 192.168.0.102:35190 ESTABLISHED 7148/perl tcp0 0 collePlayer:53238 collePlayer: ESTABLISHED 8562/sbpd tcp0 0 192.168.0.102:ssh 192.168.0.101:54724 ESTABLISHED 9016/sshd: tc [priv tcp0 0 collePlayer:collePlayer:53236 ESTABLISHED 8524/pigpiod tcp0 0 collePlayer:collePlayer:53238 ESTABLISHED 8524/pigpiod Active UNIX domain sockets (w/o servers) Proto RefCnt Flags Type State I-Node PID/Program name Path unix 2 [ ] DGRAM 29198 1389/wpa_supplicant /var/run/wpa_supplicant/wlan0 unix 2 [ ] DGRAM 40076 9105/smbd /usr/local/var/lib/samba/private/msg.sock/9105 unix 3 [ ] STREAM CONNECTED 39961 9094/jivelite unix 3 [ ] DGRAM 7866 81/udevd unix 2 [ ] STREAM CONNECTED 39199 9016/sshd: tc [priv unix 3 [ ] STREAM CONNECTED 40183 9116/1 unix 3 [ ] STREAM CONNECTED 39202 9018/0 unix 3 [ ] STREAM CONNECTED 39962 9094/jivelite unix 3 [ ] STREAM CONNECTED 40184 9114/sshd: tc [priv unix 3 [ ] STREAM CONNECTED 39203 9016/sshd: tc [priv unix 3 [ ] DGRAM 7867 81/udevd unix 2 [ ] STREAM CONNECTED 40180 9114/sshd: tc [priv "First point of failure": Code: Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp1 0 collePlayer:43002 collePlayer:9000 CLOSE_WAIT 8562/sbpd tcp0 0 192.168.0.102:35210 192.168.0.102:9000 ESTABLISHED 9094/jivelite tcp0 0 192.168.0.102:445 192.168.0.101:55656 ESTABLISHED 9105/smbd tcp0 0 192.168.0.102:38270 192.168.0.100:3000 ESTABLISHED 8480/squeezelite tcp0 0 192.168.0.102:9000 192.168.0.102:35210 ESTABLISHED 7148/perl tcp 61 0 collePlayer:3483collePlayer:56528 ESTABLISHED 7148/perl tcp0 0 192.168.0.102:35198 192.168.0.102:9000 ESTABLISHED 9094/jivelite tcp0 0 collePlayer:56528 collePlayer:3483 ESTABLISHED 8480/squeezelite tcp0 0 192.168.0.102:35144 192.168.0.102:9000 ESTABLISHED 9094/jivelite tcp0 0 192.168.0.102:9000 192.168.0.102:35144 ESTABLISHED 7148/perl tcp0208 192.168.0.102:ssh 192.168.0.101:55663 ESTABLISHED 9114/sshd: tc [priv tcp0 0 collePlayer:53236 collePlayer: ESTABLISHED 8562/sbpd tcp0 0 192.168.0.102:38268 192.168.0.100:3000 ESTABLISHED 7148/perl tcp0 0 192.168.0.102:9000 192.168.0.102:35198 ESTABLISHED 7148/perl tcp0 0 192.168.0.102:445 192.168.0.101:55657 ESTABLISHED 9107/smbd tcp0 0 192.168.0.102:38264 192.168.0.100:3000 TIME_WAIT - tcp0 0 collePlayer:53238 collePlayer: ESTABLISHED 8562/sbpd tcp0 0 192.168.0.102:ssh 192.168.0.101:54724 ESTABLISHED 9016/sshd: tc [priv tcp0 0 collePlayer:collePlayer:53236 ESTABLISHED 8524/pigpiod tcp0 0
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > This is why Wireshark logs are good - it records the whole conversation > but it can be a lot of work to analyse unless you can make the network > very quiet. So it is last resort. > > Can you use the "-p" option on your netstat ? this will show program > and PID > > > > My understanding is you play VDR stream on PCP which has LMS and > Jivelite ? So WIn10 is just a files server & remote login into pcp ? No > other network functions ? Correctly. Win10 has no other functions. I use it only for (sometimes) WebGUI and for writing into this forum here :-). schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > Please note that calling netstat takes a couple of seconds, therefore I > could not get "intermediate" states, like a connection being established > and closed shortly after. This is why Wireshark logs are good - it records the whole conversation but it can be a lot of work to analyse unless you can make the network very quiet. So it is last resort. Can you use the "-p" option on your netstat ? this will show program and PID > piCorePlayer system: "collePlayer": 192.168.0.102 > VDR streaming server: 192.168.0.100 > Win10 Laptop: 192.168.0.101 My understanding is you play VDR stream on PCP which has LMS and Jivelite ? So WIn10 is just a files server & remote login into pcp ? No other network functions ? bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
> Is VDR using HTTP 1.1 "actively" and are TCP connection being kept open > between HTTP requests from same source ? I am not able to answer that. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > Please show netstat log and do not "assume" anything. When chasing bugs > you have to be pedantic. Confirm the TCP connection against the > originating process id and the executable of the process id. > > Is VDR using HTTP 1.1 "actively" and are TCP connection being kept open > between HTTP requests from same source ? OK. Working normal case: Code: Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 192.168.0.102:9000 192.168.0.102:35118 ESTABLISHED tcp0 0 192.168.0.102:35126 192.168.0.102:9000 ESTABLISHED tcp0 0 collePlayer:3483collePlayer:56528 ESTABLISHED tcp0 0 collePlayer:56528 collePlayer:3483 ESTABLISHED tcp1 0 collePlayer:42926 collePlayer:9000CLOSE_WAIT tcp0 0 collePlayer:53236 collePlayer: ESTABLISHED tcp0 0 192.168.0.102:9000 192.168.0.102:35124 ESTABLISHED tcp0 0 192.168.0.102:38178 192.168.0.100:3000 ESTABLISHED tcp0 0 192.168.0.102:9000 192.168.0.101:54702 ESTABLISHED tcp0 0 192.168.0.102:9000 192.168.0.102:35088 ESTABLISHED tcp0 0 192.168.0.102:445 192.168.0.101:54699 ESTABLISHED tcp0 0 192.168.0.102:35088 192.168.0.102:9000 ESTABLISHED tcp0 0 192.168.0.102:35124 192.168.0.102:9000 ESTABLISHED tcp0 0 192.168.0.102:35118 192.168.0.102:9000 ESTABLISHED tcp0 0 collePlayer:53238 collePlayer: ESTABLISHED tcp0 0 192.168.0.102:445 192.168.0.101:54703 ESTABLISHED tcp0208 192.168.0.102:ssh 192.168.0.101:54724 ESTABLISHED tcp0 0 collePlayer:collePlayer:53236 ESTABLISHED tcp0 0 collePlayer:collePlayer:53238 ESTABLISHED Active UNIX domain sockets (w/o servers) Proto RefCnt Flags Type State I-Node Path unix 2 [ ] DGRAM 38658 /usr/local/var/lib/samba/private/msg.sock/8881 unix 2 [ ] DGRAM 29198 /var/run/wpa_supplicant/wlan0 unix 2 [ ] DGRAM 35471 /usr/local/var/lib/samba/private/msg.sock/8490 unix 2 [ ] DGRAM 35486 /usr/local/var/lib/samba/private/msg.sock/8493 unix 2 [ ] DGRAM 35490 /usr/local/var/lib/samba/private/msg.sock/8494 unix 2 [ ] DGRAM 35511 /usr/local/var/lib/samba/private/msg.sock/8495 unix 2 [ ] DGRAM 35523 /usr/local/var/lib/samba/private/msg.sock/8496 unix 2 [ ] DGRAM 38648 /usr/local/var/lib/samba/private/msg.sock/8879 unix 3 [ ] DGRAM 7866 unix 2 [ ] STREAM CONNECTED 39199 unix 3 [ ] STREAM CONNECTED 39202 unix 3 [ ] STREAM CONNECTED 38602 unix 3 [ ] STREAM CONNECTED 39203 unix 3 [ ] DGRAM 7867 unix 3 [ ] STREAM CONNECTED 38603 "First point of failure": Code: Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 192.168.0.102:9000 192.168.0.102:35118 ESTABLISHED tcp0 0 192.168.0.102:35126 192.168.0.102:9000 TIME_WAIT tcp0 0 collePlayer:3483collePlayer:56528 ESTABLISHED tcp0 0 collePlayer:56528 collePlayer:3483 ESTABLISHED tcp1 0 collePlayer:42926 collePlayer:9000CLOSE_WAIT tcp0 0 collePlayer:53236 collePlayer: ESTABLISHED tcp0 0 192.168.0.102:38182 192.168.0.100:3000 ESTABLISHED tcp0 0 192.168.0.102:9000 192.168.0.102:35124 ESTABLISHED tcp0 0 192.168.0.102:9000 192.168.0.101:54702 ESTABLISHED tcp0 0 192.168.0.102:9000 192.168.0.102:35088 ESTABLISHED tcp0 0 192.168.0.102:38180 192.168.0.100:3000 ESTABLISHED tcp0 0 192.168.0.102:445 192.168.0.101:54699 ESTABLISHED tcp0 0 192.168.0.102:35088 192.168.0.102:9000 ESTABLISHED tcp0 0 192.168.0.102:35124 192.168.0.102:9000 ESTABLISHED tcp0 0 192.168.0.102:35118 192.168.0.102:9000 ESTABLISHED tcp0 0 collePlayer:53238 collePlayer: ESTABLISHED tcp0 0
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > I confirmed that behaviour with netstat. Usually, when I hear the audio, > there is one connection established. During the above described "First > point of failure", I see two connections established (I assume one from > LMS, one from Squeezelite). During the second mode, I see these two > connections still active, one with state TIME_WAIT, one with state > ESTABLISHED. Please show netstat log and do not "assume" anything. When chasing bugs you have to be pedantic. Confirm the TCP connection against the originating process id and the executable of the process id. Is VDR using HTTP 1.1 "actively" and are TCP connection being kept open between HTTP requests from same source ? bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
I have a general problem. This system here is at a holiday apartment. I am leaving tomorrow and will return only in winter. Therefore, I can do any tests until tonight, but not after that. Sorry. But I appreciate very much your help, thanks a lot! schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > OK - I have a lot on now so won't be able to look at this again until > weekend. Netstat and Wireshark are still relevant and would provide > useful info. > > Can you clarify another point - in first post you say- 'In this case, > the piCorePlayer display gets stuck at "Connection being established"'- > > In the log you say > > Code: > > > * > * Getting NO Audio, Jivelite displays pop up error message "503 Service Unavailable" *** > * > > > > To me this seems like there are at least two modes of behaviour. > > Are there multiple modes ? > If so please - provide describe the different categories - just one > line per category. Yes, there are. I described them in the log. --- There is the first point of failure. I described it at [20-08-18 21:27:14.8269] There, Jivelite only display "Connection being established". I would not rate this as a real "failure" because obviously the server does not send audio. --- --- And then, as a consequence after channel switch, with the server not being able to do it, there is the second "mode". I desdcribed it at [20-08-18 21:27:38.7170] There, the server declines to provide the channel, and the LMS displays the error message. I would not rate that as a failure, either. --- The error occurs in between, because the connection from the first point of failure is not closed. I confirmed that behaviour with netstat. Usually, when I hear the audio, there is one connection established. During the above described "First point of failure", I see two connections established (I assume one from LMS, one from Squeezelite). During the second mode, I see these two connections still active, one with state TIME_WAIT, one with state ESTABLISHED. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > No! Sorry! You are looking at the wrong point of the log. > > The error occurs before. The connection HTTP=GLOB(0x6021268) is never > closed by LMS!!! And playing state there is > > The one after that (0x5ffd1f0), where the VDR server declines the > connection with the 503 response, is closed properly by LMS. But the old > one is still existing at that point of time. OK - I have a lot on now so won't be able to look at this again until weekend. Can you clarify another point - in first post you say- 'In this case, the piCorePlayer display gets stuck at "Connection being established"'- In the log you say Code: * * Getting NO Audio, Jivelite displays pop up error message "503 Service Unavailable" *** * To me this seems like there are at least two modes of behaviour. Are there multiple modes ? If so please - provide describe the different categories - just one line per category. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > No it looks like connection was closed an stream put into IDLE state. > > To check actual state of network connections and not just the last > message shown on Jivelite, use netstat > > Alternatively, if you want to check whether TCP connection is closed or > left hanging in some way after 503 response - you can use Wireshark and > log the network IP packets. Ok, confirmed with netstat. In the usual (working) case, netstat shows one connection. In the case it goes wrong, it shows two connections, both with state Established. Then after the 503 response has been sent from the server, these two connections are still there, one with state TIME_WAIT and the other one with Established. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > No it looks like connection was closed an stream put into IDLE state. > > > Code: > > > [20-08-18 21:27:38.6939] Slim::Networking::Async::disconnect (251) Close Slim::Networking::Async::Socket::HTTP=GLOB(0x5ffd1f0) => 29 > [20-08-18 21:27:38.6991] Slim::Utils::Scanner::Remote::__ANON__ (192) Error: Can't connect to remote server to retrieve playlist for, http://192.168.0.100:3000/ES/1052: 503 Service Unavailable. > [20-08-18 21:27:38.7079] Slim::Player::StreamingController::_playersMessage (796) 503 Service Unavailable: http://192.168.0.100:3000/ES/1052 > > * > * Getting NO Audio, Jivelite displays pop up error message "503 Service Unavailable" *** > * > > [20-08-18 21:27:38.7170] Slim::Player::StreamingController::_setStreamingState (2386) new streaming state IDLE > > > > > No! Sorry! You are looking at the wrong point of the log. The error occurs before. The connection HTTP=GLOB(0x6021268) is never closed by LMS!!! And playing state there is The one after that (0x5ffd1f0), where the VDR server declines the connection with the 503 response, is closed properly by LMS. But the old one is still existing at that point of time. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > Yes, sure, the 503 response is the effect that the streaming server > denies a new connection, and that one (in log: HTTP=GLOB(0x5ffd1f0)) is > closed properly by LMS. But the one before (HTTP=GLOB(0x6021268)), and > that is the root cause in my opinion, is not closed. And this causes the > server to serve this connection forever. > > I guess this is because of the special situation the player or LMS is > in. The log says > > > Code: > > 20-08-18 21:27:14.4926] Slim::Player::StreamingController::_setPlayingState (2377) new playing state BUFFERING > > > > It does not reach PLAYING. It seems LMS is still waiting for the > playing state PLAYING and therefore does not close the connection. > > Don't you agree with this? No it looks like connection was closed an stream put into IDLE state. Code: [20-08-18 21:27:38.6939] Slim::Networking::Async::disconnect (251) Close Slim::Networking::Async::Socket::HTTP=GLOB(0x5ffd1f0) => 29 [20-08-18 21:27:38.6991] Slim::Utils::Scanner::Remote::__ANON__ (192) Error: Can't connect to remote server to retrieve playlist for, http://192.168.0.100:3000/ES/1052: 503 Service Unavailable. [20-08-18 21:27:38.7079] Slim::Player::StreamingController::_playersMessage (796) 503 Service Unavailable: http://192.168.0.100:3000/ES/1052 * * Getting NO Audio, Jivelite displays pop up error message "503 Service Unavailable" *** * [20-08-18 21:27:38.7170] Slim::Player::StreamingController::_setStreamingState (2386) new streaming state IDLE bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > The log shows that LMS closed the TCP connection. The 503 connection > comes from VDR server and is the reply to the GET. > > Code: > > > [20-08-18 21:27:38.3582] Slim::Player::Song::getNextSong (252) scanning URL http://192.168.0.100:3000/ES/1052 > [20-08-18 21:27:38.3779] Slim::Networking::Async::connect (108) Connecting to 192.168.0.100:3000 > [20-08-18 21:27:38.4978] Slim::Networking::Async::_async_connect (196) Slim::Networking::Async::Socket::HTTP=GLOB(0x5ffd1f0) => 29 connected, ready to write request > [20-08-18 21:27:38.5079] Slim::Networking::Async::write_async (226) Sending: [GET /ES/1052 HTTP/1.0 > Connection: close > Cache-Control: no-cache > Accept: */* > Host: 192.168.0.100:3000 > User-Agent: iTunes/4.7.1 (Linux; N; piCore; armv8l-linux; DE; utf8) SqueezeCenter, Squeezebox Server, Logitech Media Server/8.0.0/1597263993 > Icy-Metadata: 1 > > > > > > Yes, sure, the 503 response is the effect that the streaming server > denies a new connection, and that one (in log: HTTP=GLOB(0x5ffd1f0)) > is closed properly by LMS. But the one before (HTTP=GLOB(0x6021268)), > and that is the root cause in my opinion, is not closed. And this > causes the server to serve this connection forever. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote:
> The log shows that LMS closed the TCP connection. The 503 connection
> comes from VDR server and is the reply to the GET.
> >
Code:
> >
> [20-08-18 21:27:38.3582] Slim::Player::Song::getNextSong (252) scanning URL
http://192.168.0.100:3000/ES/1052
> [20-08-18 21:27:38.3779] Slim::Networking::Async::connect (108) Connecting
to 192.168.0.100:3000
> [20-08-18 21:27:38.4978] Slim::Networking::Async::_async_connect (196)
Slim::Networking::Async::Socket::HTTP=GLOB(0x5ffd1f0) => 29 connected, ready to
write request
> [20-08-18 21:27:38.5079] Slim::Networking::Async::write_async (226)
Sending: [GET /ES/1052 HTTP/1.0
> Connection: close
> Cache-Control: no-cache
> Accept: */*
> Host: 192.168.0.100:3000
> User-Agent: iTunes/4.7.1 (Linux; N; piCore; armv8l-linux; DE; utf8)
SqueezeCenter, Squeezebox Server, Logitech Media Server/8.0.0/1597263993
> Icy-Metadata: 1
>
> ]
> [20-08-18 21:27:38.5805] Slim::Player::TranscodingHelper::checkBin (285)
couldn't find binary for: lame
> [20-08-18 21:27:38.5881]
Slim::Player::TranscodingHelper::getConvertCommand2 (467) Error: Didn't find
any command matches for type: mp3
> [20-08-18 21:27:38.6757] Slim::Networking::Async::HTTP::_http_read (406)
Headers read. code: 503 status: Service Unavailable
> [20-08-18 21:27:38.6901] Slim::Networking::Async::HTTP::_http_read (407)
bless({
> "::std_case" => { "set-cookie" => "Set-Cookie", "set-cookie2" =>
"Set-Cookie2" },
> "cache-control" => "no-cache",
> connection => "close",
> date => "Tue, 18 Aug 2020 19:28:41 GMT",
> pragma => "no-cache",
> server => "VDR-2.4.1 / streamdev-server-0.6.1-git",
> }, "HTTP::Headers")
> [20-08-18 21:27:38.6939] Slim::Networking::Async::disconnect (251) Close
Slim::Networking::Async::Socket::HTTP=GLOB(0x5ffd1f0) => 29
> [20-08-18 21:27:38.6991] Slim::Utils::Scanner::Remote::__ANON__ (192)
Error: Can't connect to remote server to retrieve playlist for,
http://192.168.0.100:3000/ES/1052: 503 Service Unavailable.
> [20-08-18 21:27:38.7079] Slim::Player::StreamingController::_playersMessage
(796) 503 Service Unavailable: http://192.168.0.100:3000/ES/1052
>
> >
>
> It doesn't look like squeezelite has been told to do a GET (in
> slimproto stream_s message) as in previous playing
> >
Code:
> >
> [20-08-18 21:27:14.4365] Slim::Player::Squeezebox::stream_s (837) setting
up direct stream (3232235620:3000) autostart: 3 format: m.
> [20-08-18 21:27:14.4488] Slim::Player::Squeezebox::stream_s (838) request
string: GET /ES/1290 HTTP/1.0
>
> >
>
> Where/When does picoreplayer still say "Connection being established"
> - is this a pcp special display or a message displayed on Jivelite ?
It is in Jivelite, in Now playing the top status bar.
schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557
View this thread: http://forums.slimdevices.com/showthread.php?t=112774
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote:
> You misunderstood my writings. I am not interpreting the log, but have
> added - more or less precisely - my perception, i.e. the point of time
> when I heared the player playing the radio station (if it did).
The log shows that LMS closed the TCP connection. The 503 connection
comes from VDR server and is the reply to the GET.
Code:
[20-08-18 21:27:38.3582] Slim::Player::Song::getNextSong (252) scanning URL
http://192.168.0.100:3000/ES/1052
[20-08-18 21:27:38.3779] Slim::Networking::Async::connect (108) Connecting to
192.168.0.100:3000
[20-08-18 21:27:38.4978] Slim::Networking::Async::_async_connect (196)
Slim::Networking::Async::Socket::HTTP=GLOB(0x5ffd1f0) => 29 connected, ready to
write request
[20-08-18 21:27:38.5079] Slim::Networking::Async::write_async (226) Sending:
[GET /ES/1052 HTTP/1.0
Connection: close
Cache-Control: no-cache
Accept: */*
Host: 192.168.0.100:3000
User-Agent: iTunes/4.7.1 (Linux; N; piCore; armv8l-linux; DE; utf8)
SqueezeCenter, Squeezebox Server, Logitech Media Server/8.0.0/1597263993
Icy-Metadata: 1
]
[20-08-18 21:27:38.5805] Slim::Player::TranscodingHelper::checkBin (285)
couldn't find binary for: lame
[20-08-18 21:27:38.5881] Slim::Player::TranscodingHelper::getConvertCommand2
(467) Error: Didn't find any command matches for type: mp3
[20-08-18 21:27:38.6757] Slim::Networking::Async::HTTP::_http_read (406)
Headers read. code: 503 status: Service Unavailable
[20-08-18 21:27:38.6901] Slim::Networking::Async::HTTP::_http_read (407)
bless({
"::std_case" => { "set-cookie" => "Set-Cookie", "set-cookie2" =>
"Set-Cookie2" },
"cache-control" => "no-cache",
connection => "close",
date => "Tue, 18 Aug 2020 19:28:41 GMT",
pragma => "no-cache",
server => "VDR-2.4.1 / streamdev-server-0.6.1-git",
}, "HTTP::Headers")
[20-08-18 21:27:38.6939] Slim::Networking::Async::disconnect (251) Close
Slim::Networking::Async::Socket::HTTP=GLOB(0x5ffd1f0) => 29
[20-08-18 21:27:38.6991] Slim::Utils::Scanner::Remote::__ANON__ (192) Error:
Can't connect to remote server to retrieve playlist for,
http://192.168.0.100:3000/ES/1052: 503 Service Unavailable.
[20-08-18 21:27:38.7079] Slim::Player::StreamingController::_playersMessage
(796) 503 Service Unavailable: http://192.168.0.100:3000/ES/1052
It doesn't look like squeezelite has been told to do a GET (in slimproto
stream_s message) as in previous playing
Code:
[20-08-18 21:27:14.4365] Slim::Player::Squeezebox::stream_s (837) setting up
direct stream (3232235620:3000) autostart: 3 format: m.
[20-08-18 21:27:14.4488] Slim::Player::Squeezebox::stream_s (838) request
string: GET /ES/1290 HTTP/1.0
Where/When does picoreplayer still say "Connection being established" -
is this a pcp special display or a message displayed on Jivelite ?
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=112774
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > > > Can you check the end point of connection from the VDR server and > determine the status of the initial LMS connection and status of the 2nd > connection from Squeezelite. I am not sure whether I am able to I have an integrated piCorePlayer setup with player and LMS on one RasPi. So from the IP address, I can't tell. But still, I have to say that I got this behaviour with direct and proxied streaming. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > Your interpretation of LMS log about getting audio is not quite right. > With direct streaming Audio is read directly by the squeezelite by a > separate HTTP GET which is not logged by LMS. The small fragment of > audio retrieved by LMS after header is only used to parse the > audiostream for sample rate etc. The main playing audio is read directly > by squeezelite and not logged by LMS. I think "direct" playing will > report fullness of buffers. You misunderstood my writings. I am not interpreting the log, but have added - more or less precisely - my perception, i.e. the point of time when I heared the player playing the radio station (if it did). schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
Your interpretation of LMS log about getting audio is not quite right. With direct streaming Audio is read directly by the squeezelite by a separate HTTP GET which is not logged by LMS. The small fragment of audio retrieved by LMS after header is only used to parse the audiostream for sample rate etc. The main playing audio is read directly by squeezelite and not logged by LMS. I think "direct" playing will report fullness of buffers. When the connection is still open but LMS does't show playlist - it is possible the connection is open to squeezelite. Can you check the end point of connection from the VDR server and determine the status of the initial LMS connection and status of the 2nd connection from Squeezelite. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > I'll check log again but Reliable plugin means connection is always > proxied and never direct. For the latest server log, I have deactivated the Reliable Plugin. Streaming method setting was and is direct. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > I'll check log again but Reliable plugin means connection is always > proxied and never direct. For the latest server log. I had deactivated the Reliable Plugin. Streaming method setting was and is direct. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > Actually I added Reliable plugin only yesterday to see whether this > could help - it did not do anything to my specific problem. > > Anyway, I did it again with Reliabe Plugin deactivated. This time, it > took a little more channel switches to reproduce the situation where the > server does not provide audio. > > I see the HTTP=GLOB(0x6021268) being connected, but not disconnected. I'll check log again but Reliable plugin means connection is always proxied and never direct. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > I noticed you are using a "Reliable" plugin. > > Please test with this removed - This plugin does "special" things with > TCP connection to ensure when they drop they are reconnected > automagically. > > Code: > > > [70-01-01 20:14:40.9156] Slim::Player::Song::open (468) Opening stream (no direct streaming) using Plugins::Reliable::ProtocolHandler [http://192.168.0.100:3000/ES/1052] > > > > > Also - for lots of odd things - it is good to set up a date & time > that is close to reality, Actually I added Reliable plugin only yesterday to see whether this could help - it did not do anything to my specific problem. Anyway, I did it again with Reliabe Plugin deactivated. This time, it took a little more channel switches to reproduce the situation where the server does not provide audio. I see the HTTP=GLOB(0x6021268) being connected, but not disconnected. +---+ |Filename: VDR_channels_server_3.log.txt| |Download: http://forums.slimdevices.com/attachment.php?attachmentid=31322| +---+ schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
I noticed you are using a "Reliable" plugin. Please test with this removed - This plugin does "special" things with TCP connection to ensure when they drop they are reconnected automagically. Code: [70-01-01 20:14:40.9156] Slim::Player::Song::open (468) Opening stream (no direct streaming) using Plugins::Reliable::ProtocolHandler [http://192.168.0.100:3000/ES/1052] Also - for lots of odd things - it is good to set up a date & time that is close to reality, bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > There are some other ideas to try - mainly concentrating on direct > connection and understanding what squeezelite is doing. If a mod is > needed it is easier to modify squeezelite. > > Just to be sure what is happening - can you get a log with player.source > set to INFO when playing a VDR radio channel. Make sure player is set to > use "direct" and not "proxied" OK, I did that, but I did a little bit more: I turned on player.source INFO player.streaming INFO player.streaming.direct INFO network.asynchttp DEBUG That shows also the HTTP connection, sorry, it's a little verbose. I inserted my actions or perceptions into the log. In this special case, the HTTP connection (here: HTTP=GLOB(0x6375f90)) is not disconnected afterwards. Hope you can find what you are aiming for. +---+ |Filename: VDR_channels_server_2.log.txt| |Download: http://forums.slimdevices.com/attachment.php?attachmentid=31320| +---+ schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
There are some other ideas to try - mainly concentrating on direct connection and understanding what squeezelite is doing. If a mod is needed it is easier to modify squeezelite. Just to be sure what is happening - can you get a log with player.source set to INFO when playing a VDR radio channel. Make sure player is set to use "direct" and not "proxied" bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > Thinking a bit more. > > If HTTP connection is established LMS will wait for audio. With internet > radio station it is the radio station that breaks a connection with LMS. > LMS is content to wait to fill buffer before initiating playing, if far > end (i.e. VDR) is acking all TCP request to say link is OK - then > nothing will happen. > > To clear such a dead link I think you should try to "clear playlist" - > on WebUI is the is thr small "x"button on bottom RHS of WebUI or the > "clear playlist" on Jivelite. Yes, with a usual internet radio station this is not a problem . It has to provide thousands of Http connections, it won't matter if there are some dead ones. Only my special "station" cares because it then cannot tune to another transponder. I think the timeout should apply in this case or at least the http should be closed once something new to play is chosen in LMS. I guess that the timeout was initially meant to be the maximum waiting time until the server acks the TCP request from LMS. Thanks a lot for your suggestion. I tried, but unfortunately it doesn't help. Neither in the WebUI not in Jivelite this had an effect. The dead link doesn't show up in the playlist, either. I even tried to play something from my library. After having done that, the http link still exists and is being served by the server. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > Thinking a bit more. > > If HTTP connection is established LMS will wait for audio. With internet > radio station it is the radio station that breaks a connection with LMS. > LMS is content to wait to fill buffer before initiating playing, if far > end (i.e. VDR) is acking all TCP request to say link is OK - then > nothing will happen. > > To clear such a dead link I think you should try to "clear playlist" - > on WebUI is the is thr small "x"button on bottom RHS of WebUI or the > "clear playlist" on Jivelite. Yes, I think with usual internet radio stations, this is no problem. Such a station has to provide thousands of Http connections. If there are some dead ones, it won't really care. In my special case, my "station" cares I think the timeout should apply also here. Probably it was meant to be the maximum waiting time until the server acks the TCP. Thanks a lot for your suggestion. Unfortunately, it doesn't help. I tried, but neither in Jivelite nor in WebUI this has an effect. The "dead" connection doesn't show up in the playlist, either. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > I don't know enough about VDR and if I understand the issue correctly, > with LMS when a new stream is being started while another is playing > (i.e. stream has not been stopped) I think there will be overlap with > one HTTP connection open and a second connection being opened. Normally > they are two different sources. In this case it seems LMS will have one > connection open and will be trying to open the same address but with a > different URL. This is unlike VLC which will stop one connection > before opening a second. > > Can VDR support two HTTP connection open at the same time ? Satellite > decoders often have a single tuner and so can only support a single > stream at a time. Normally, in case satellite tuning is fine, VLC and LMS behave exactly the same. Yes, there are always two overlapping HTTP connections, with one being closed shortly after channel switch. The behaviour is only different if the satellite tuner does not provide audio. It seems to be some kind of intermediate state for LMS - as I said you can't even pause the stream because there is none - it displays still "Connection being established'. And then, you realize younger nothing, and want to switch to another channel, and LMS does request the new HTTP, but does not close the old one. VLC instead does. Yes, the streaming server accepts multiple connections, but it can only provide multiple channels from the one transponder it is tuned to. It cannot tune to two transponders at a time, but it in principle provide all channels from one transponders. Of course at a certain stage there will be also performance issues of the RasPi schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
Thinking a bit more. If HTTP connection is established LMS will wait for audio. With internet radio station it is the radio station that breaks a connection with LMS. LMS is content to wait to fill buffer before initiating playing, if far end (i.e. VDR) is acking all TCP request to say link is OK - then nothing will happen. To clear such a dead link I think you should try to "clear playlist" - on WebUI is the is thr small "x"button on bottom RHS of WebUI or the "clear playlist" on Jivelite. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > In this special case where the server does not provide audio, LMS > remains stuck at "Connection being established", and it isn't even > possible to pause it. But latest when I request another stream, the old > (stuck, not working) HTTP connection should be really closed by LMS. But > it is not. And thus, the server is also stuck because it "thinks" it > still has to provide / try to provide this channel, and cannot change to > a channel of another transponder. > > I can see this "closing or not closing HTTP connection" in the log of > the VDR streaming server. It normally works, if the server has provided > an audio stream. But it should also work in the case there is no audio > stream, otherwise it is a dead lock, which can only be repaired by > restart of LMS or of the streaming server. I don't know enough about VDR and I understand the issue, with LMS when a new stream is being started while another is playing (i.e. stream has not been stopped) there will be overlap with one HTTP connection open and a second connection being opened. Normally they are two different sources. In this case it seems LMS will have one connection open and will be trying to open the same address but with a different URL. This is unlike VLC which will stop one connection before opening a second. Can VDR support two HTTP connection open at the same time ? Satellite decoders often have a single tuner and so can only support a single stream at a time. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
bpa wrote: > I don't understand this sentence ? Please clarify - has audio stopped > and HTTP is still active ? > > On LMS - a stream is not "stopped" if it is just "paused" - single short > press on "||" just pauses a stream. In this special case where the server does not provide audio, LMS remains stuck at "Connection being established", and it isn't even possible to pause it. But latest when I request another stream, the old (stuck, not working) HTTP connection should be really closed by LMS. But it is not. And thus, the server is also stuck because it "thinks" it still has to provide / try to provide this channel, and cannot change to a channel of another transponder. I can see this "closing or not closing HTTP connection" in the log of the VDR streaming server. It normally works, if the server has provided an audio stream. But it should also work in the case there is no audio stream, otherwise it is a dead lock, which can only be repaired by restart of LMS or of the streaming server. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
It is a Opera DVB-S USB box connected to a Raspberry Pi Zero W, with Raspbian Buster and VDR on it. The VDR software has a plugin called streamdev-server, which provides the Http server and forwards the audio stream. VLC codec info says: MPEG Audio layer 1/2 (mpga). schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
It is a Opera DVB-S USB box connected to a Raspberry Pi Zero W, with Raspbian Buster and VDR on it. The VDR software has a plugin called streamsev-server, which provides the Http server and forwards the audio stream. VLC codec info says: MPEG Audio layer 1/2 (mpga). schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > BTW: It is no TCP over Satellite. It is a DVB-S satellite receiver, > which provides a local http streaming server. I have only mobile (LTE) > internet here on my mobile phone What is the model/make of satellite decoder ? Is the stream really HTTP/MP3 - many DVB-S decoder just provide HTTP/MPEG-2/MP3 streams What does VLC media "CODEC Info" say about the stream ? bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > It just does not close the HTTP connection in case the server does not > provide audio. I don't understand this sentence ? Please clarify bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > BTW: It is no TCP over Satellite. It is a DVB-S satellite receiver, > which provides a local http streaming server. I have only mobile (LTE) > internet here on my mobile phone What format (i.e. transport & codec) is coming out of DVB-S decoder ? I'd still try "proxied" for same reason - LMS has more control assuming the stream is HTTP/AAC or HTTP/MP3. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
BTW: It is no TCP over Satellite. It is a DVB-S satellite receiver, which provides a local http streaming server. I have only mobile (LTE) internet here on my mobile phone schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
It is MP3. I tried both proxied and direct streaming. The behaviour did not change. It just does not close the HTTP connection in case the server does not provide audio. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
Satellite connection because of long transit time have "unusual" TCP parameter such as large window sizes. This may be part of the issue. What is the format of the stream ? If its http/AAC ir http/MP3 then it will be played "direct" by squeezelite and so LMS has less control over it (eg. if LMS dies , stream will keep playing) I suggest try enabling "proxied streaming" for the player (WebUI Settings/Player/Audio/StreamingMethod ) - this give LMS more direct control over the stream. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
d6jg wrote: > I think you will need to post LMS version no etc Ok, sorry. I am currently on 8.0.0, 1597263993, but I had the same issue on 7.9.x before. piCorePlayer 5.0.1, Squeezelite 1.9.2-1158 System is running on a Pi Zero W. schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
Re: [SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
schup011 wrote: > Hi guys, > > I have problems with streaming radio from an own satellite radio > streaming server (don't have wired internet here), which is a separate > Raspberry Pi with a VDR installation on it. > > My squeeze setup, here acting as streaming client, is a piCorePlayer > with integrated LMS and Jivelite on 7 inch screen. > > The radio stations are set as favourites in LMS, pointing to the VDR > streaming server, e.g. 192.168.0.100:3000/ES/1052 > > Usually, this works really well: the display goes (quickly) from > "Connection being established" over > "Buffering" > to > "Now Playing". > Everything fine, I am listening radio. > > Sometimes, however, when I change the radio channel by choosing another > favourite, the satellite radio server accepts the HTTP connection, but > does not send any audio because it cannot tune to the transponder (bad > signal). In this case, the piCorePlayer display gets stuck at > "Connection being established". I cannot even stop the connection in > Jivelite. > > The problem now is that the LMS does not close the HTTP connection > because it still waits for an audio stream. And because of this, I > cannot tune to another radio station. LMS requests a new HTTP > connection, but does not close the old one, and the server is stuck at > the old one and does not accept a new one. I can only proceed if I > "motivate" the server to close this HTTP connection by itself, but that > is not feasible for normal use, as it is headless. > > I would have expected that LMS closes the HTTP connection after a > certain timeout period, but it doesn't. I know that there is this > timeout setting, but it doesn't seem to have any effect in this case. > > I have tested another streaming client instead of LMS / squeezelite: VLC > Player on Windows 10. With it, it works properly. VLC closes the HTTP > connection at latest when I request a new HTTP stream. > > Does anyone have a clue whether this LMS behaviour (obviously different > from that of VLC) is desired? Why does it not close the HTTP after a > certain timeout? Should I activate special logging to track that? > > Thanks for your help! I think you will need to post LMS version no etc VB2.4[/B] STORAGE *QNAP TS419P (NFS) [B]Living Room* - Joggler & SB3 -> Onkyo TS606 -> Celestion F20s *Office* - Pi3+Sreen -> Sony TAFE320 -> Celestion F10s / Pi2+DAC & SB3 -> Onkyo CRN755 -> Wharfedale Modus Cubes *Dining Room* -> SB Boom *Kitchen* -> UE Radio (upgraded to SB Radio) *Bedroom (Bedside)* - Pi2+DAC ->ToppingTP21 ->AKG Headphones *Bedroom (TV)* - SB Touch ->Sherwood AVR ->Mordaunt Short M10s Everything controlled by iPeng d6jg's Profile: http://forums.slimdevices.com/member.php?userid=44051 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
[SlimDevices: SqueezeCenter] Streaming Radio: HTTP connection is not closed
Hi guys, I have problems with streaming radio from an own satellite radio streaming server (don't have wired internet here), which is a separate Raspberry Pi with a VDR installation on it. My squeeze setup, here acting as streaming client, is a piCorePlayer with integrated LMS and Jivelite on 7 inch screen. The radio stations are set as favourites in LMS, pointing to the VDR streaming server, e.g. 192.168.0.100:3000/ES/1052 Usually, this works really well: the display goes (quickly) from "Connection being established" over "Buffering" to "Now Playing". Everything fine, I am listening radio. Sometimes, however, when I change the radio channel by choosing another favourite, the satellite radio server accepts the HTTP connection, but does not send any audio because it cannot tune to the transponder (bad signal). In this case, the piCorePlayer display gets stuck at "Connection being established". I cannot even stop the connection in Jivelite. The problem now is that the LMS does not close the HTTP connection because it still waits for an audio stream. And because of this, I cannot tune to another radio station. LMS requests a new HTTP connection, but does not close the old one, and the server is stuck at the old one and does not accept a new one. I can only proceed if I "motivate" the server to close this HTTP connection by itself, but that is not feasible for normal use, as it is headless. I would have expected that LMS closes the HTTP connection after a certain timeout period, but it doesn't. I know that there is this timeout setting, but it doesn't seem to have any effect in this case. I have tested another streaming client instead of LMS / squeezelite: VLC Player on Windows 10. With it, it works properly. VLC closes the HTTP connection at latest when I request a new HTTP stream. Does anyone have a clue whether this LMS behaviour (obviously different from that of VLC) is desired? Why does it not close the HTTP after a certain timeout? Should I activate special logging to track that? Thanks for your help! schup011's Profile: http://forums.slimdevices.com/member.php?userid=66557 View this thread: http://forums.slimdevices.com/showthread.php?t=112774 ___ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
