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?
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.
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
/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,
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
Luke,
I have disabled my firewall , not sure about
QuoteVerify that the cli port is setted to 9090 in the web configuration
Here's my Squeezecenter setup
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)
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.
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 ??
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
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
/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,
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
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
Luke,
Here's the output of the netstat
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
== 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.
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).
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???
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
Luke,
Here's the output of netstat -an | grep ":9090"
linuxmce@dcerouter:/var/log/pluto$ 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:38027 ESTABLISHED
tcp 0 0 127.0.0.1:38027 127.0.0.1:9090 ESTABLISHED
and here's the output of more /etc/hosts
linuxmce@dcerouter:/var/log/pluto$ more /etc/hosts
## @FileType: Pluto Sectioned Config File ##
## @Version: 1 ##
## @KeepSections: ##
## @RemoveSections: ##
## BEGIN : NetworkSetup
192.168.80.1 dcerouter
## END : NetworkSetup
## BEGIN : DisklessMD
192.168.80.2 moon47
## 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
Here's my Slim_Server_Streamer.log, when I try to switch music from the core to the Boom using the floorplan
linuxmce@dcerouter:/var/log/pluto$ more 59_Slim_Server_Streamer.log
05 06/30/09 8:29:37.912 Going to rotate logs... <0xb7285b90>
05 06/30/09 20:30:25.709 Could not find an controlling device for stream: 1003 <0xb7285b90>
05 06/30/09 20:30:57.124 Could not find an controlling device for stream: 1005 <0xb7285b90>
05 06/30/09 20:33:06.969 Could not find an controlling device for stream: 1007 <0xb7285b90>
05 06/30/09 20:35:21.811 Slim_Server_Streamer::CMD_Stop_Streaming() got a command for a stream that is not registered here: 1009 <0xb
7285b90>
05 06/30/09 20:53:45.015 Slim_Server_Streamer::CMD_Stop_Streaming() got a command for a stream that is not registered here: 1012 <0xb
7285b90>
05 06/30/09 20:54:22.154 Could not find an controlling device for stream: 1013 <0xb7285b90>
05 06/30/09 20:56:22.103 Slim_Server_Streamer::CMD_Stop_Streaming() got a command for a stream that is not registered here: 1015 <0xb
7285b90>
05 06/30/09 21:02:16.426 Slim_Server_Streamer::CMD_Stop_Streaming() got a command for a stream that is not registered here: 1018 <0xb
7285b90>
05 06/30/09 21:06:25.585 Could not find an controlling device for stream: 1020 <0xb7285b90>
linuxmce@dcerouter:/var/log/pluto$
I just want to update on my current status:
Squeezecenter web interface <-----> Boom (Both direction OK)
Squeezecenter web interface -----> Squeezebox receiver (OK)
Linuxmce Floor plan ------->Boom (not ok)
Linuxmce Floor plan ------->Squeezebox receiver (not ok)
Charlie,
have you tried to put both the squeezebox players in a different room of the MD , for example create a home teather room?
Because I remember that in the past I had some problems to play music on those Hw when they were in the same room of a MD. Actually I'm not saing that is a bug of LinuxMCE (absolutly not) but mine problem to manage it.
For my testing I prefer to use those in this situation for semplicity, in a real and complete installation I'll try to integrate all of them in the correct room. I think that what I'm talking about is related to scenarios configuration.
Try it and then tell us what happens !
Regards
Luke
Luke,
My squeezeboxes already assigned to Kitchen, and Patio, so I re-assigned them to a different rooms (Garage, Bath) same results.
So I decided to go and delete both devices, and the Slim Server Streamer, and start all over again, after I rebooted and regenerate all orbiters, I noticed that I still have all 4 objects of the squeezeboxes still on the floorplan. My experience from the past if you delete a device from web admin, and regenerate/reboot the PC, the objects on the floorplan will be deleted, so here tells me something wrong and that's why I was not able to play from the floorplan!!!!
I couldn't figure out how to delete those object from the floorplan, to start all over again, any ideas???
Charlie,
did you try with weborbiter client ? Because in the past with the 0810 alpha I had problems with the orbiter on the core for power on and power off to md . With the weborbiter all work well.
Try it.
I never encounter problem in disinstalling and cancelling devices via web .
Regards,
Luke
Luke,
I made 810 new installation on my laptop using VMWare, then I connected the Boom Squeezebox to the internal network, LinuxMCE detected the device, and installed some software, I noticed some failed messages during the installation, I attached the DCErouter.log if someone interested, after that reloaded the router and added squeezebox object to the floorplan, and setup sqeezecenter from the web interface, everything worked, so I don't know why my Desktop setup didn't work, I guess I need to reinstall everything all over again !!!! :(
the Configure_Squeezebox.pl script needs some slight fixing. That's the error you're seeing (deprecated perl calls)
-Thom
Quote from: tschak909 on July 03, 2009, 08:26:01 AM
the Configure_Squeezebox.pl script needs some slight fixing. That's the error you're seeing (deprecated perl calls)
-Thom
Thom - Uplink fixed those issues about 10 days ago...I am pretty sure all our Squeezecenter/Squeezebox updates/fixes are in the svn already.
Andrew
Quote from: totallymaxed on July 03, 2009, 11:30:39 AM
Thom - Uplink fixed those issues about 10 days ago...I am pretty sure all our Squeezecenter/Squeezebox updates/fixes are in the svn already.
If someone updates the SVN, and corrects a mistake, and wants to have the whole participate in the fix, s/he might want to update http://wiki.linuxmce.org/index.php/LinuxMCE-0810_alpha2#upcoming... so whoever is taking care of the build of updated packages, knows about it.
Currently I have Alpha 2.26, I'm not able to play any music from my DNS-323 shared folder to the squeezebox, I can play music from my "/home/public/data/audio" folder (local Drive) to squeezebox no problem, also I can play music from my DNS-323 to any MD without any problem???
I checked Squeezecenter settings, the music folder is set for "/home/public/data/audio" but I couldn't see the NAS shared folder to selected.
Any ideas??
Thanks.
When you say you can't see the NAS shared folder, do you mean even when you terminal into your core, and cd to that folder? If so, then I think you have added your share as "public" rather than "use LMCE folder structure" when the share was detected by LMCE.... this is not advisable at all. You should always use the LMCE folder structure unless you have _very_ good reasons not to. One (of many) reason for this is that it won't have the symlink in that folder, thus if your Squeezebox is looking at that folder, it won't see your library.
Colin,
I added my NAS folder share "\volume1\multimedia" as "use LinuxMCE folder structure" with no password using "all users", and I can see all the files on the NAS from my other MDs, from the terminal mode I did "ls -l /mnt/device/98" it asked fo higher privileges so I did "sudo ls -l /mnt/device/98" and I saw all folder under "\volume1\multimedia".
Charlie
No matter how you tell it to add the shares they will always appear in the /mnt folders. What I am talking about is looking in /home/public/data/video|audio|pictures|etc - under there you should see "Windows Share blah blah" and then under that, your media. If not you have some problem. If so, then you should be set for Squeezebox, as it just needs to be pointed at the root for audio, being /home/public/data/audio.
Colin,
Here's the output
linuxmce@dcerouter:~$ cd /home/public/data/audio/
linuxmce@dcerouter:/home/public/data/audio$ ls -l
total 4
drwxrwxr-x 2 pluto_charlie public 4096 2009-07-18 20:15 Arabic Helene 1
lrwxrwxrwx 1 root public 32 2009-07-30 04:39 Windows Share-Multimedia [92] -> /mnt/device/92/public/data/audio
linuxmce@dcerouter:/home/public/data/audio$
linuxmce@dcerouter:/home/public/data/audio$ cd Windows Share-Multimedia [92]
-bash: cd: Windows: No such file or directory
sudo ls /mnt/device/92/public/data/
[sudo] password for linuxmce:
audio documents games pictures pvr videos
linuxmce@dcerouter:/home/public/data/audio$
when you are in the audio folder, type cd W then just hit the tab key. Let it autocomplete to make sure it recognises it and it is spelt correctly.
If that still doesn't work then you have a problem somewhere. What colour and background is the symlink when you ls -al? This should tell you whether it is available and online or offline.
The other thing you need to confirm is - have you ever tried to either mount and symlink (using the commands ln or mount for instance) anything on your system? This is an absolute no-no, if you have then you could easily have screwed up the automounting functionality. LMCE manages its media, shares, mounts and links automatically. If it doesn't work, then there is a problem somewhere else, the answer isn't to start trying to create them manually! That's kind of like pulling your car dashboard to pieces so that you can replace the oil warning light because its on, rather than checking to see if you have oil! So can you confirm you have never done this?
Colin,
Autocomplete is not working with the "cd W"??
I'm using SecureCRT to SSH, everything looks black even the link.
Yes I can confirm I didn't create any links manually on the system.
The issue here when I browse the media from the other 3 MDs at home it is ok as I mentioned before only Squeezebox can not see the audio files on the NAS??
Here's a snapshot of the current status of the NAS
It really shouldn't matter which terminal program you are using, as this is a function of the bash shell, however you could just try going to the KDE desktop and starting the terminal program in there. Also, can you try tab in a few other locations? It should do command completion as well as directory path completion. Try cd'ing into another directory using auto complete like Arabic Helene 1 (remember everything is case sensitive)... it is possible that completion won't work if it thinks the target is not a valid target, so try with a normal directory first.
You also didn't attempt to manually mount anything? (you only mention links above)
A _possible_ issue here is, UpdateMedia (used to create the media library) sometimes can scan folders that other methods fail on. If this was the case just for that Windows Share folder, but folders below it are fine, UpdateMedia will build your library correctly. Then when you browse and play the media on an MD, you aren't actually browsing the folders themselves, you are browsing the database, so any specific issues with particular folders would not be apparent. When you select and play a piece of media, the entire path is passed to the media player, and so potentially it could still be able to play the media even if there was an issue with the Windows Share folder. However, with Squeezebox, that same issue on that folder could prevent it from scanning inside the media folders, thus preventing it from seeing and playing your media.
Its a long shot, but I am still concerned that you don't seem to be able to cd into that folder, and there should be no issue with that. Can you please try cding into the same folder under the mnt?
ie cd /mnt/device/92/public/data/audio
I don't have any difficulty cding or lsing into those folders without having to sudo, so I think you should do an ls -al of /mnt and /mnt/device and /mnt/device/92 so we can see the permissions of each of these folders.
Finally, you haven't set up an upnp either on the NAS or LMCE, have you? I know allowing it to mount the same media shares by both methods can get things into a complete loop (literally!)
Colin,
No i didn't setup pnp, and I didn't mount anything manually.
I'm going home now, I wil try the rest from home, I can cd to other folder fine like Arabic Helene 1 and see the data
Here's the output
linuxmce@dcerouter:~$ ls -al /mnt
total 12
drwxr-xr-x 4 root root 4096 2009-07-29 20:20 .
drwxr-xr-x 21 root root 4096 2009-07-29 20:20 ..
drwxr-xr-x 3 root root 0 2009-07-30 16:20 device
drwxr-xr-x 2 root root 4096 2009-07-04 19:34 upnp
linuxmce@dcerouter:~$ ls -al /mnt/device
total 4
drwxr-xr-x 3 root root 0 2009-07-30 16:20 .
drwxr-xr-x 4 root root 4096 2009-07-29 20:20 ..
drwxrwx--- 7 501 501 0 2009-06-17 23:15 92
linuxmce@dcerouter:~$ ls -al /mnt/device/92
ls: cannot open directory /mnt/device/92: Permission denied
linuxmce@dcerouter:~$
Colin,
I tried directly from terminal mode at the hybrid, the link color was red, I added admin username & password in the NAS & the shared folder in webadmin I was able to switch at least to /mnt/device/92 without sudo but I can not see any files below that point, and when I rebooted the PC, on power up I got "CIFS VFS: send error in QFSAttributeInfo = -5"
Update1:
I removed the username & password & I rebooted, the NAS came back online, so I opened Dolphin and I was able to see all my NAS files using the following path:" /Network/Samba Share/Linuxmce/Dns-323 (Dlink-DNS323)/Multimedia/public/data/audio/"
If I try to go to "/root/mnt/device/92" using dolphin no files visible
If I try to go to "/Root/home/public/data/audio/Windows Share-Multimedia [92]" I get Open with pop up window
FYI Here's the output of the mount command
//192.168.80.139/Multimedia on /mnt/device/92 type cifs (rw,mand,unc=\\192.168.80.139\Multimedia,username=guest,posixpaths,acl,rsize=16384,wsize=57344)
linuxmce@dcerouter:~$
Update2:
I decided to go and start from scratch, I deleted from Webadmin the Share & NAS device, also I removed all entries in the "PnpQueue" table which I was surprised there was 95 rows!!! then I rebooted both Hybrid and NAS, it got detected by the pnp and used Multimedia share and reloaded the router, exactly the same results as we were having before !!!!
Any other suggestions??
Thanks
Just one question here, why my Windows Share always has the "Readonly" always checked?? I never put any restrictions during setup/configuration.
Anybody else having similar problem with NAS sharing???or only my setup???
I'm at a bit of a loss here....
First the permissions on that mount are the main issue you are having. You will note that it says the 92 folder has read/write/excute access for the user and group "501". But no access to "other" and that is the critical issue. On mine, I have read/write/excute access for user, group and other (open access) and the owner and groups are both "root" not "501" - I have no idea what "501" is, I am using 0710, if you are using 0810 then perhaps there was a change and someone else can suggest the reason why. But it doesn't make any sense to me. It is certainly what is preventing you lsing and cding into that folder without sudo, and could be implicated in the main issue.
Pigdog - can you check this on yours as well?
In the meantime, you could try manually overriding the permissions on that folder, this may resolve the problem, although it will tell us nothing about why you are having the problem in the first place. You can use chmod to change the permissions and chown to change the ownership.
sudo chmod ugo+rwx /mnt/device/92
sudo chown root:root /mnt/device/92
As for the pnpqueue - it is normal for that to have lots of entries... remember, in pnp the _initial_ detection of a new device is only a special case. pnp more generally is for detection of devices irrespective of whether they are new or not. For instance, as remote media shares (like NASes) come and go, the pnp system detects this and either makes the media available or hides it. So that table will continue to fill up, especially when you reload the router as this causes all devices to be rediscovered.
Colin,
I really thank you for spending time with me.
When I had 710 setup everything was working as expected, this issues started when I switched to 810.
The 95 rows were for the NAS only, BTW the NAS id is 102 after I reinstalled it here the output.
linuxmce@dcerouter:/home/public/data/audio$ cd /mnt/device/
linuxmce@dcerouter:/mnt/device$ ls -al
total 4
drwxr-xr-x 3 root root 0 2009-07-31 14:43 .
drwxr-xr-x 4 root root 4096 2009-07-30 21:22 ..
drwxrwx--- 7 501 501 0 2009-06-17 23:15 102
linuxmce@dcerouter:/mnt/device$ sudo chmod ugo+rwx 102
[sudo] password for linuxmce:
chmod: changing permissions of `102': Not a directory
linuxmce@dcerouter:/mnt/device$
hmm I logged into your core, I can see the same behaviour you are seeing with the chmod. On my 0710 it executes fine, but doesn't seem to change anything.... I am thinking this is because it is actually a mount point rather than a real directory (the underlying directory is currently hidden by the mounted share), and perhaps 0810 and 0710 handle this differently when you try to modify it. Which makes me think that the owner and permissions are coming from somewhere else... either the mount code or the remote share itself.
I am hoping that someone with greater knowledge on this will chime in soon! But I looked around your system, and couldn't find either a user or group called 501... is there any chance this has come from the NAS? I'm now thinking that the Squeezecenter software has not got the permissions to enter that folder, hence your issues... but that is a guess.
Your mount string is different from mine. Mine doesn't mention the posixpaths or acl options, but does specify uid and gid to be 0 which is what is setting my ownership to root:root
In particular, the acl option on yours I think may be the key... guessing here, but the manual page for mount seems to be suggesting that mount has determined that your NAS is an ex2/3 filesystem and so is attempting to use its permissions, groups and users instead of the core's, and that would be an obvious issue... if that is the case, then it would seem to be a bug in 0810's mounting system, it should force root:root (gid=0 uid=0) ... perhaps one of the devs is reading this?
Check to see if the NAS has a user and group of 501.... (can you ssh into it?)
Colin,
The NAS, is connected on the inside network, I can only control the external network from the router, I will be home in couple hours to check it out.
I was not able to ssh nor telnet to the D-link NAS, from the web interface there was one user I deleted the user and rebooted the NAS, same results, still shows user 501 on the /mnt/device/102 !!!
I doubled checked my core there is no user 501, it must be from the Dlink-323!!!
Time to start a new thread - the thread title is misleading and most people will not be coming in here and reading the updates.
Create a descriptive title (don't go overboard!), write a precis in your first post - talk only about this specific issue, what we have discovered, the permissions/ownership issue and the mount options that seem different in 0810. And ask for others to compare your results, and for recommendations on how you can override these options without breaking the automouting system so that you can check if that is the issue.
Then put a link in to this thread, for background. Now, go to the IRC channel, and ask for help - when someone puts their hand up, paste a link to your new thread and ask them to look at the brief description there...