squeezebox

[rages]

Hi,
I read on the logitech site that configure the Squeezebox Receiver need a Squeezebox classic.
This applies even if you use LinuxMCE?
But most of all, you can use the Squeezebox Receiver with Linuxmce?

[posde]

The SqueezeBox Receiver is currently not plug and play with LinuxMCE. It does work, but a bit of manual configuration is necessary, due to the fact, that Logitech uses a different standard setting.

[ccoudsi]

Did anyone experience problem with the Squeezebox in 810 Alpha 2.23??

 I had both boxes (SqueezeBox Receiver &SqueezeBox Boom)  working in the earlier version of 810 now I reinstalled 810, and got both detected and assigned an IP but no sounds output from them.

Both  SqueezeBox player's info shows not registered and Status =” **RUN_CONFIG** !!

here’s what I got from the Slim Server Streamer log of

Code:

/var/log/pluto/59_Slim_Server_Streamer.log

========== NEW LOG SECTION ==========
1 06/27/09 13:41:34 59 (spawning-device) Starting... 1
1 06/27/09 13:41:34 59 (spawning-device) Found /usr/pluto/bin/Slim_Server_Streamer
05 06/27/09 13:41:34.695 Trying to connect to SlimServer at address: 127.0.0.1:9090 <0xb7a7c6c0>
05 06/27/09 13:41:34.696 Creating child 61 <0xb7a7c6c0>
05 06/27/09 13:41:34.696 Creating child 62 <0xb7a7c6c0>
== ATTEMPT FRESH START ==
1 06/27/09 13:41:52 /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device) 17791 Dev: 59; Already Running list: 15,18,19,27,28,29,30,44,16,59,
1 06/27/09 13:41:52 /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device) 17791 Device 59 was marked as 'running'. Not starting
1 06/27/09 13:41:52 /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device) 17791 Dev: 59; Exiting because not starting

Thanks
Charlie,

[felpouse]

Hi,

have you checked if the squeezecenter software was installed and running?
Could you connect to it at http://xxx.xxx.xxx.xxx:9000 ?
Verify that the cli port is setted to 9090 in the web configuration.

I have two squeezeboxes and one squeezebox boom and both of them are working out the box without any strange configuration tips.

Regards,

Luke

[ccoudsi]

Luke,

I have disabled my firewall , not sure about

Verify that the cli port is setted to 9090 in the web configuration

Here's my Squeezecenter setup

Code:

     
SqueezeCenter StatusVersion: 7.3.3 - 27044 @ Mon Jun 15 15:12:32 PDT 2009

Hostname: dcerouter

IP: 192.168.0.34

HTTP Port: 9000

OS: Debian - EN - utf8

Platform: i686-linux

Perl Version: 5.10.0 - i486-linux-gnu-thread-multi

MySQL Version: 5.0.67-0ubuntu6

Total Players Recognized: 1

 
Library StatisticsTotal Tracks: 0

Total Albums: 0

Total Artists: 0

Total Genres: 0

Total Playing Time: 0:00:00

 
Music Scan DetailsPlaylist Scan   (  of  )   Complete  00:00:00


Database Cleanup #1   (0  of  0)   Complete  00:00:00


Database Cleanup #2   (  of  )   Complete  00:00:00


Database Optimize   (  of  )   Complete  00:00:00


   (  of  )     


   (  of  )     


   (  of  )     


   (  of  )     


   (  of  )     


   (  of  )     


   (  of  )     


SqueezeCenter has finished scanning your music collection.
Total Time: 00:00:00 (Saturday, June 27, 2009 / 3:05 PM)
 
Player InformationInformation on all identified devices connected to SqueezeCenter
 
Squeezebox-booomPlayer Model: boom

Firmware: 47

Player IP Address: 192.168.80.135

Player MAC Address: 00:04:20:1e:ee:ff

 
Folders
Cache Folder/var/lib/squeezecenter/cache
Preferences Folder/var/lib/squeezecenter/prefs
Plugin Folders/var/lib/squeezecenter/cache/InstalledPlugins/Plugins, /usr/sbin/Plugins, /usr/share/squeezecenter/Plugins
SqueezeCenter Log FileSqueezeCenter keeps a log file for all application related activities (Audio Streaming, Infrared, etc) here:
/var/log/squeezecenter/server.log (100, 500, 1000 lines)
 
Scanner Log FileSqueezeCenter keeps a log file for all scanning related activities, including iTunes & MusicIP here:
/var/log/squeezecenter/scanner.log (100, 500, 1000 lines)
 
 

[ccoudsi]

Luke,

I just noticed that SqueezeCenter is using my external IP address of the Hybrid, and not the internal, also if I go to (Advanced/Configuration/SLIM Server) it says Loading SqueezeCenter but nothing happened !! How do you set SqueezeCenter IP to 192.168.80.1 Because both players set for 192.168.80.1 SqueezeCenter server.

Thanks.

[ccoudsi]

Update, if I go to "http://localhost:9000" I get the SqueezeCenter, from there I can play music on both devices (Boom & Receiver) but if I play a song on the MD, and go to the FloorPlan and select the squeezbox no audio output
In the past I don't remember I did anything special to do that !!!!

So it looks like SqueezCenter sees my devices but not LMCE !!!

Any Ideas on how to register SqueezeBoxes with 810 LMCE ??

[tschak909]

Did LinuxMCE see the squeezebox?

If so, did it create the Slim Server Streamer?

If so, did it put the squeezebox player as a child of the slim server streamer?

-Thom

[ccoudsi]

Thom,

Yes, LMCE detected both SqueezeBoxes, and created a Slim Server Streamer, and it is registered, also 2 Child "SqueezeBox Player" devices were created under the Streamer, but these Child devices the status shows "**RUN_Config**" and "Registered =NO" 
Here's the Follow Log from the Streamer

Code:

/var/log/pluto/59_Slim_Server_Streamer.log========== NEW LOG SECTION ==========
1 06/28/09 11:34:29 59 (spawning-device) Starting... 1
1 06/28/09 11:34:29 59 (spawning-device) Found /usr/pluto/bin/Slim_Server_Streamer
05 06/28/09 11:34:30.002 Trying to connect to SlimServer at address: 127.0.0.1:9090 <0xb79656c0>
05 06/28/09 11:34:30.011 Creating child 61 <0xb79656c0>
05 06/28/09 11:34:30.011 Creating child 62 <0xb79656c0>
== ATTEMPT FRESH START ==
1 06/28/09 11:34:47 /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device) 17149 Dev: 59; Already Running list: 16,18,28,29,15,19,27,30,44,59,63,
1 06/28/09 11:34:47 /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device) 17149 Device 59 was marked as 'running'. Not starting
1 06/28/09 11:34:47 /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device) 17149 Dev: 59; Exiting because not starting

Charlie,

[felpouse]

Charlie,

could you , please, check if you have a solution like this?

dcerouter_113060:~# netstat -an | grep ":9000"
tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN     

dcerouter_113060:~# tail -f /var/log/pluto/41_Slim_Server_Streamer.log
05      06/28/09 20:54:22.917           OL: (0x86b25f0) (>175) internal-data-structure-mutex Slim_Server_Streamer.cpp l:492 time: 9:36:20p (83882 s) thread: 3063233424 Rel: Y Got: Y <0xb7154b90>
Return code: 2
2       06/28/09 20:54:23       41 (spawning-device)    Device requests restart... count=1/50 dev=41
Sun Jun 28 20:54:23 CEST 2009 Restart
========== NEW LOG SECTION ==========
1       06/28/09 20:54:31       41 (spawning-device)    Starting... 1
1       06/28/09 20:54:31       41 (spawning-device)    Found /usr/pluto/bin/Slim_Server_Streamer
05      06/28/09 20:54:39.468           Trying to connect to SlimServer at address: 127.0.0.1:9090 <0xb79f76c0>
05      06/28/09 20:54:39.470           Creating child 40 <0xb79f76c0>
05      06/28/09 20:54:39.470           Creating child 43 <0xb79f76c0>

And the situation for your two child is correct.

I think you have to investigate on the running mode of you squeezecenter, actually.

Regards,

Luke

[PeteK]

This may be stupid, but I was pulling my hair out for a while over a squeezebox that wasn't working with an earlier 0810 alpha build.  Nothing seemed wrong, but I couldn't get it to play (using lmce), despite multiple router reloads.  I decided to reboot the PC, and it started working and has been since.

-Peter

[ccoudsi]

Luke,

Here's the output of the netstat

Code:

linuxmce@dcerouter:/var/log/pluto$ netstat -an | grep ":9000"
tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:9000          127.0.0.1:38991         ESTABLISHED
tcp        0      0 127.0.0.1:38986         127.0.0.1:9000          ESTABLISHED
tcp        0      0 127.0.0.1:9000          127.0.0.1:38992         ESTABLISHED
tcp        0      0 127.0.0.1:9000          127.0.0.1:38986         ESTABLISHED
tcp        0      0 127.0.0.1:38994         127.0.0.1:9000          ESTABLISHED
tcp        0      0 127.0.0.1:9000          127.0.0.1:38995         ESTABLISHED
tcp        0      0 127.0.0.1:38993         127.0.0.1:9000          ESTABLISHED
tcp        0      0 127.0.0.1:9000          127.0.0.1:38994         ESTABLISHED
tcp        0      0 127.0.0.1:38992         127.0.0.1:9000          ESTABLISHED
tcp        0      0 127.0.0.1:9000          127.0.0.1:38993         ESTABLISHED
tcp        0      0 127.0.0.1:38991         127.0.0.1:9000          ESTABLISHED
tcp        0      0 127.0.0.1:38995         127.0.0.1:9000          ESTABLISHED

And Slim_Server_Streamer.log

Code:

== ATTEMPT FRESH START ==
1       06/28/09 11:34:29       /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device)     ^[[1;00m13318 Dev: 59; Already Running list: 16,18,28,29,15,19,27,30,44,^[[1;00m
== FRESH START ==
1       06/28/09 11:34:29       /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device)     ^[[1;00mdevice: 59 ip: localhost cmd_line: Slim_Server_Streamer^[[1;00m
0       06/28/09 11:34:29       59 (spawning-device)    ^[[1;00mEntering 59^[[1;00m
========== NEW LOG SECTION ==========
1       06/28/09 11:34:29       59 (spawning-device)    ^[[1;00mStarting... 1^[[1;00m
1       06/28/09 11:34:29       59 (spawning-device)    ^[[1;00mFound /usr/pluto/bin/Slim_Server_Streamer^[[1;00m
05      06/28/09 11:34:30.002           ^[[33;1mTrying to connect to SlimServer at address: 127.0.0.1:9090^[[0m <0xb79656c0>
05      06/28/09 11:34:30.011           ^[[33;1mCreating child 61^[[0m <0xb79656c0>
05      06/28/09 11:34:30.011           ^[[33;1mCreating child 62^[[0m <0xb79656c0>
== ATTEMPT FRESH START ==
1       06/28/09 11:34:47       /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device)     ^[[1;00m17149 Dev: 59; Already Running list: 16,18,28,29,15,19,27,30,44,59,63,^[[1;00m
1       06/28/09 11:34:47       /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device)     ^[[1;00m17149 Device 59 was marked as 'running'. Not starting^[[1;00m
1       06/28/09 11:34:47       /usr/pluto/bin/Spawn_Device.sh 59 (spawning-device)     ^[[1;00m17149 Dev: 59; Exiting because not starting^[[1;00m
05      06/28/09 12:18:37.599           ^[[33;1mGot a reload command from 0 ^[[0m <0xb7163b90>
05      06/28/09 12:18:37.851           ^[[33;1mvoid ClientSocket::Disconnect() on this socket: 0x8b6a3e8 (m_Socket: 6)^[[0m <0xb79656c0>
Return code: 2
2       06/28/09 12:18:38       59 (spawning-device)    ^[[1;33mDevice requests restart... count=1/50 dev=59^[[1;00m
Sun Jun 28 12:18:38 PDT 2009 Restart
========== NEW LOG SECTION ==========
"59_Slim_Server_Streamer.log.1" [readonly] 547L, 57034C

Peter,
I did reboot multiple times, same results.

[colinjones]

OK, trying to recall as I haven't got the slimserver/squeezecenter device installed at the moment....

port 9000 as I recall is used for the web interface to what is now known as SqueezeCenter (although it seems as though 0810 still calls it SlimServer). You can connect to that address:port with a web browser to control the SqueezeCenter directly. However, SqueezeCenter (and the older SlimServer) also has another port called the CLI port that allows you to connect to and relay commands to programatically. This is the interface that LMCE uses to send commands to the Squeeze system.

The LMCE DCE device responsible for this (slimserverstreamer, I think) connects to SqueezeCenter through this port, then receives LMCE DCE commands/events from the DCERouter, translates them, and relays them to the SqueezeCenter through the CLI port (not the web interface). The SqueezeCenter (and SlimServer before it) then connects to the appropriate SqueezeBox and sends the necessary native commands to achieve the result required.

From your log output, it would appear that the LMCE DCE device, is #59 (the parent of the 2 actual devices, and responsible for relaying the commands, both in the LMCE schema and the SqueezeCenter "real world"), and that this DCE device believes that the CLI port is 9090.

Now I don't know if this has changed since the 0710 version I am used to, or my memory is faultly, but nothing about 9090 rings a bell. From memory, the port number is configured in the SlimServer DCE device's Device Data. If it is not correct, then either you need to update this Device Data field to reflect the correct port that SqueezeCenter is using, OR connect to SqueezeCenter on its web admin interface (http://192.168.80.1:9000) and change its CLI port configuration to be 9090. Only then can then communicate correctly. Then do a reboot.

From the logging it appears that the DCE device attempts to connect on 9090.... it doesn't explicitly say this fails, but doesn't confirm it either. Then on subsequent reattempts it appears that it may be failing because it never connected correctly and never shutdown correctly either (probably a bug), so LMCE thinks it is already running (which it is) and working/communicating fine (which it isn't).

[ccoudsi]

Colin,

I just verified CLI port using SequeezeCenter web interface, under /settings/Plugin/CLI settings, it shows Port 9090 !!!
Also I noticed under SqueezeCenter web interface/Home/Music Source, there is 2 settings 1)SqueezeNetwork 2)DCErouter, I tried DCErouter nothing happened???

[felpouse]

Charlie,

you can also try to verify that another process of squeezecenter isn't trying to start or an old version is still present.

Verify also that the cli port is really working like this :

dcerouter_113060:~# netstat -an | grep ":9090"
tcp        0      0 0.0.0.0:9090            0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:9090          127.0.0.1:35691         ESTABLISHED
tcp        0      0 127.0.0.1:35691         127.0.0.1:9090          ESTABLISHED

Than take a look on the /etc/hosts files for the corect link to localhost and so on.

dcerouter_113060:~# more /etc/hosts
## @FileType: Pluto Sectioned Config File ##
## @Version: 1 ##
## @KeepSections: ##
## @RemoveSections: ##

## BEGIN : NetworkSetup
192.168.110.1 dcerouter
## END : NetworkSetup

## BEGIN : DisklessMD
192.168.110.201         moon75

## END : DisklessMD

127.0.0.1       localhost.localdomain   localhost
::1             ip6-localhost           ip6-loopback
fe00::0         ip6-localnet
ff00::0         ip6-mcastprefix
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters
ff02::3         ip6-allhosts

## BEGIN : DiskledMD

## END : DiskledMD


Regards,

Luke