PDA

View Full Version : Scanning the Music Library on SlimCD



MLaw
2007-07-23, 13:21
I have just moved my music library from a Windows xp server to a dedicated SlimCD -laptop based system. The MP3 files are stored in a directory /music on a USB HD formatted with NTFS. SlimCD worked exactly as required. However, I have installed the software on the laptop's internal HD. The installation looked exactly the same as the CD version - with one exception - the SlimServer will not scan the music files. They can be seen on the mounted sda1 disk via the linux commands, but the slimserver just reports that a rescan is in progress with no activity indicated on my external drive.

Can any Slimserver or Linux wizards help point me in the right direction.

Mike

mherger
2007-07-23, 13:52
> directory /music on a USB HD formatted with NTFS. SlimCD worked exactly

What are the permissions on this mountpoint (ls -l /music)?

> They can be seen on the mounted sda1 disk via the linux commands, but
> the slimserver just reports that a rescan is in progress with no
> activity indicated on my external drive.

Turn on d_scan before starting the scan - this will give us some more
hints.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

MLaw
2007-07-23, 14:15
------What are the permissions on this mountpoint (ls -l /music)?


drwx------ 1 dsl staff 118784 jul 20 3:23 music



-----Turn on d_scan before starting the scan - this will give us some more
hints.



2007-07-23 22:01:47.6360 Setup::rescan - initiating scan of type: [wipecache]
2007-07-23 22:01:52.7409 MultiLibrary: Synchronizing libraries data, please wait...
2007-07-23 22:01:52.7424 MultiLibrary: Synchronization finished-----


Mike

mherger
2007-07-23, 14:27
> drwx------ 1 dsl staff 118784 jul 20 3:23 music

This means that the slimserver user very likely is not allowed to access
it, but only the user dsl. Make sure everybody has read access to that
drive (drwxr-xr-x).

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

MLaw
2007-07-23, 14:28
Just a note to say that the Slimserver can see and play all the mp3 files in the Music Folder

Mike

MLaw
2007-07-23, 16:50
Hi Michael,

I have changed the permissions as requested and the results are exactly the same. I guess that I need to find the other differences between running from the CD and the hard disk installation.

Mike

mherger
2007-07-23, 23:12
> I have changed the permissions as requested and the results are exactly
> the same.

As you noticed in your previous post:

> Just a note to say that the Slimserver can see and play all the mp3files
> in the Music Folder

....guess it's still playing, same result?

I'm confused. Does it work? Then you don't have to change anything. If it
doesn't - what did you do with what result?

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

MLaw
2007-07-24, 12:05
Hi Michael,

I am afraid I was not clear in my last response.Changing the permissions on the Music directory via the addition of Umask to the /etc/fstab file has made no difference. What I was trying to explain was that the "Music Folder" ( ie the physical files) can be browsed and played, but no database is built by the scanner to select music through browse and search by artists, Genres etc. The scanning process works with the bootable CD whilst on the same sda1 drive the hd installed version does not.

Here is the complete trace of a clear library and rescan process straight after booting the HD installation. All users have read and execute permissions on the ntfs drive


NTFSdrive.2007-07-24 19:44:24.0729 ERROR: Cannot write to preferences file /opt/slimserver/slimserver.pref, any changes made will not be preserved for the next startup of the server

2007-07-24 19:44:24.1034 Use of uninitialized value in join or string at /usr/local/lib/perl5/5.8.6/File/Spec/Unix.pm line 73.
2007-07-24 19:44:24.1036 Use of uninitialized value in join or string at /usr/local/lib/perl5/5.8.6/File/Spec/Unix.pm line 73.
2007-07-24 19:44:40.0845 Warning: Slim::Music::Info::getCurrentDataStore() is deprecated. Please use Slim::Schema directly.
2007-07-24 19:44:49.7151 Warning: Slim::Music::Info::getCurrentDataStore() is deprecated. Please use Slim::Schema directly.
2007-07-24 19:44:53.4844 MultiLibrary: Synchronizing libraries data, please wait...
2007-07-24 19:44:53.4967 MultiLibrary: Synchronization finished
2007-07-24 19:45:17.7338 ERROR: Async: Couldn't resolve IP address for: update.slimdevices.com

2007-07-24 19:45:17.7346 There was an error while checking for updates to SlimServer:
Failed to connect to http://update.slimdevices.com/update/?version=6.5.3&lang=EN (Couldn't resolve IP address for: update.slimdevices.com)

2007-07-24 19:45:17.9726 MultiLibrary: Synchronizing libraries data, please wait...
2007-07-24 19:45:17.9761 MultiLibrary: Synchronization finished
2007-07-24 19:47:03.5761 Setup::rescan - initiating scan of type: [wipecache]
2007-07-24 19:47:08.7372 MultiLibrary: Synchronizing libraries data, please wait...
2007-07-24 19:47:08.7402 MultiLibrary: Synchronization finished

regards

Mike

mherger
2007-07-24, 12:47
Hi Mike

> I am afraid I was not clear in my last response.Changing the
> permissions on the Music directory via the addition of Umask to the
> /etc/fstab file has made no difference. What I was trying to explain
> was that the "Music Folder" ( ie the physical files) can be browsed and
> played, but no database is built by the scanner to select music through
> browse and search by artists, Genres etc.

They're not even added when you're browsing that folder?

The fact that you can brows the music folder says that your problem is
elsewhere. I rather guess it's a permission issue on MySQL.

> NTFSdrive.2007-07-24 19:44:24.0729 ERROR: Cannot write to preferences
> file /opt/slimserver/slimserver.pref, any changes made will not be
> preserved for the next startup of the server

Not even the preference file can be written. Please check permissions on
/opt/slimserver. Where is MySQL writing to? By default it's
/tmp/slimserver/Cache or something. Could you add -d_startup to the start
parameters and post the log file here (please upload the file instead of
pasting it in, as the line breaks make it harder to read - thanks!).

> 2007-07-24 19:44:40.0845 Warning:
> Slim::Music::Info::getCurrentDataStore() is deprecated. Please use
> Slim::Schema directly.

That's very likely one of the numerous plugins which needs an update...
Nothing serious, only a warning.

Michael

MLaw
2007-07-24, 15:17
Hi Michael,

Here is the Startup log you requested.Permissions on /

regards

Mike

mherger
2007-07-24, 15:31
> Here is the Startup log you requested.Permissions on /

I see three issues here:

1. already mentioned: "Cannot write to preferences file
/opt/slimserver/slimserver.pref" - make sure the slimserver user has the
appropriate permissions for that file

2. remove the /home/root/slimserver.pref file

3. check permissions on /tmp/.slimcache - that's where MySQL is trying to
write its data and is failing miserably:

2007-07-24 22:15:08.7659 ERROR: DBI Connection failed: DBI
connect('hostname=127.0.0.1;port=9092;database=sli mserver:mysql_socket=/tmp/.slimcache/slimserver-mysql.sock','slimserver',...)
failed: Can't connect to MySQL server on '127.0.0.1' (111) at
/opt/slimserver/CPAN/DBIx/Class/Storage/DBI.pm line 652

It's time for me to call it a day...

Michael

MLaw
2007-07-25, 10:42
Hi Michael,

Thanks for your guidance and patience. I now have a working HD installation ( and a far greater understanding of the Linux command set ) File permissions and a missing Slimserver.pref file were the root cause of the problem.

Thanks and best regards

Mike

mherger
2007-07-25, 12:34
Hi Mike

> Thanks for your guidance and patience. I now have a working HD
> installation ( and a far greater understanding of the Linux command set
> ) File permissions and a missing Slimserver.pref file were the root
> cause of the problem.

Great! Have fun!

Michael