MrGrumpie Posted November 2, 2010 Share Posted November 2, 2010 Followed of all the instructions, but I'm getting this error: BEGIN failed--compilation aborted at slimserver.pl line 164. Any ideas? Thanks Quote Link to comment
MrGrumpie Posted November 3, 2010 Share Posted November 3, 2010 This is the full log, it appears that a folder is missing...can anyone help? root@Tower:/mnt/disk1# chmod -R 777 slimserver root@Tower:/mnt/disk1# chmod -R 777 Music root@Tower:/mnt/disk1# eco >> /etc/passwd -bash: eco: command not found root@Tower:/mnt/disk1# echo >> /etc/passwd root@Tower:/mnt/disk1# echo slimserver:$1$oExleBv6$Ux2qBpAanWMqJqUeH2xqp1:1000 :100:,,,:/home/slimserver:/bin/bash >> /etc/passwd root@Tower:/mnt/disk1# chown -R slimserver.users . cd slimseroot@Tower:/mnt/disk1# cd slimserver root@Tower:/mnt/disk1/slimserver# perl slimserver.pl --daemon --user slimserver perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_COLLATE = "C", LANG = "en_US" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). Your locale was detected as C, you may have problems with non-Latin filenames. Consider changing your LANG variable to the correct locale, i.e. en_US.utf8 Can't locate Slim/Buttons/Common.pm in @INC (@INC contains: /mnt/disk1/slimserver/CPAN/arch/5.10/i386-linux-thread-multi /mnt/disk1/slimserver/CPAN/arch/5.10/i386-linux-thread-multi/auto /mnt/disk1/slimserver/CPAN/arch/5.10.0/i486-linux-thread-multi /mnt/disk1/slimserver/CPAN/arch/5.10.0/i486-linux-thread-multi/auto /mnt/disk1/slimserver/CPAN/arch/5.10/i486-linux-thread-multi /mnt/disk1/slimserver/CPAN/arch/5.10/i486-linux-thread-multi/auto /mnt/disk1/slimserver/CPAN/arch/i486-linux-thread-multi /mnt/disk1/slimserver/lib /mnt/disk1/slimserver/CPAN /mnt/disk1/slimserver /mnt/disk1/slimserver /usr/lib/perl5/5.10.0/i486-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl/5.10.0/i486-linux-thread-multi /usr/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.10.0/i486-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl .) at slimserver.pl line 164. BEGIN failed--compilation aborted at slimserver.pl line 164. root@Tower:/mnt/disk1/slimserver# ps- ef Quote Link to comment
joshpond Posted November 6, 2010 Share Posted November 6, 2010 have you installed mySQL? Needed installed first as it needs the files but you don't have to enable reinstall every time. Get it off unMenu. what version of slimserver did you tar? Josh Quote Link to comment
johnieutah Posted December 19, 2010 Share Posted December 19, 2010 I've just updated my SBS install to the latest nightly version of 7.6 and kept all preferences, plugins intact. Here's a quick guide for anyone that's interested: I would kill the currently running SBS process first! 1. Unrar the new package and move to new install directory: • tar -xf squeezeboxserver-7.x.x.tgz • mv squeezeboxserver-7.x.x. /SBS_new_install/ 2. Permissions of directories and files needs to be 755: • chmod -R 755 /SBS_new_install/ 3. Ownership of root program directory needs to be changed (I use slimserer:1000 for some reason!): • chown -R slimserver:1000 4. Copy across the Prefs, Plugins, and Cache directories from the old installation: • cp -pR /SBS_old_install/Prefs /SBS_new_install/ • cp -pR /SBS_old_install/Plugins /SBS_new_install/ • cp -pR /SBS_old_install/Cache /SBS_new_install/ 5. Change any references in prefs/server.prefs to the old installation and update with the new path (I find it easiest just to use TextPad find/replace in windows TBH) 6. Try and run the slimserver process, it will fail but the Logs directory will be created. Change this directory and its files ownership and permissions otherwise the process will bomb out again! • chown -R slimserver:1000 Logs • chmod -R 755 Logs 7. Start up the new installation: • perl /SBS_new_install/slimserver.pl --daemon --user slimserver >/dev/null 2>&1 & Good luck. Matt. Quote Link to comment
dedwards Posted December 21, 2010 Share Posted December 21, 2010 Hey everyone, Not really a Linux user here, but I followed the steps posted above by keyman33. Plus the steps from the first post for installing slimserver. Everything seemed to work, except I can't see that it is running - any thoughts? root@MediaServer:/mnt/disk1/slimserver# perl slimserver.pl --daemon --user slims erver perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_COLLATE = "C", LANG = "en_US" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). Your locale was detected as C, you may have problems with non-Latin filenames. Consider changing your LANG variable to the correct locale, i.e. en_US.utf8 [10-12-20 21:32:48.5240] main::init (323) Starting Squeezebox Server (v7.5.3, r3 1652, Mon Dec 20 03:05:17 MST 2010) perl 5.010000 root@MediaServer:/mnt/disk1/slimserver# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 Dec15 ? 00:00:01 init root 2 0 0 Dec15 ? 00:00:00 [kthreadd] root 3 2 0 Dec15 ? 00:00:00 [migration/0] root 4 2 0 Dec15 ? 00:00:00 [ksoftirqd/0] root 5 2 0 Dec15 ? 00:00:00 [events/0] root 6 2 0 Dec15 ? 00:00:00 [khelper] root 11 2 0 Dec15 ? 00:00:00 [async/mgr] root 112 2 0 Dec15 ? 00:00:02 [sync_supers] root 114 2 0 Dec15 ? 00:00:00 [bdi-default] root 116 2 0 Dec15 ? 00:00:00 [kblockd/0] root 117 2 0 Dec15 ? 00:00:00 [kacpid] root 118 2 0 Dec15 ? 00:00:00 [kacpi_notify] root 119 2 0 Dec15 ? 00:00:00 [kacpi_hotplug] root 217 2 0 Dec15 ? 00:00:00 [ata/0] root 218 2 0 Dec15 ? 00:00:00 [ata_aux] root 222 2 0 Dec15 ? 00:00:00 [ksuspend_usbd] root 227 2 0 Dec15 ? 00:00:00 [khubd] root 230 2 0 Dec15 ? 00:00:00 [kseriod] root 263 2 0 Dec15 ? 00:00:00 [rpciod/0] root 286 2 0 Dec15 ? 00:00:04 [kswapd0] root 331 2 0 Dec15 ? 00:00:00 [aio/0] root 337 2 0 Dec15 ? 00:00:00 [nfsiod] root 342 2 0 Dec15 ? 00:00:00 [kslowd000] root 343 2 0 Dec15 ? 00:00:00 [kslowd001] root 552 2 0 Dec15 ? 00:00:00 [usbhid_resumer] root 591 1 0 Dec15 ? 00:00:00 /sbin/udevd --daemon root 703 2 0 Dec15 ? 00:00:00 [scsi_eh_0] root 705 2 0 Dec15 ? 00:00:00 [usb-storage] root 722 2 0 Dec15 ? 00:00:00 [scsi_eh_1] root 723 2 0 Dec15 ? 00:00:00 [scsi_eh_2] root 724 2 0 Dec15 ? 00:00:00 [scsi_eh_3] root 727 2 0 Dec15 ? 00:00:00 [scsi_eh_4] root 728 2 0 Dec15 ? 00:00:00 [scsi_eh_5] root 730 2 0 Dec15 ? 00:00:00 [scsi_eh_6] root 732 2 0 Dec15 ? 00:00:00 [scsi_eh_7] root 733 2 0 Dec15 ? 00:00:00 [scsi_eh_8] root 1137 1 0 Dec15 ? 00:00:00 /usr/sbin/syslogd -m0 root 1141 1 0 Dec15 ? 00:00:00 /usr/sbin/klogd -c 3 -x root 1180 1 0 Dec15 ? 00:00:00 /usr/sbin/ifplugd -i eth0 -fwI - root 1210 1 0 Dec15 ? 00:02:23 /sbin/dhcpcd -d -t 30 -h MediaSe bin 1222 1 0 Dec15 ? 00:00:00 /sbin/rpc.portmap nobody 1226 1 0 Dec15 ? 00:00:00 /sbin/rpc.statd root 1236 1 0 Dec15 ? 00:00:00 /usr/sbin/inetd root 1246 1 0 Dec15 ? 00:00:00 /usr/sbin/acpid root 1253 1 0 Dec15 ? 00:00:00 /usr/sbin/crond -l10 daemon 1255 1 0 Dec15 ? 00:00:00 /usr/sbin/atd -b 15 -l 1 root 1260 1 0 Dec15 ? 00:00:01 /usr/sbin/nmbd -D root 1262 1 0 Dec15 ? 00:00:00 /usr/sbin/smbd -D root 1267 1 0 Dec15 ? 00:00:00 /usr/local/sbin/emhttp root 1269 1262 0 Dec15 ? 00:00:00 /usr/sbin/smbd -D root 1284 2 0 Dec15 ? 00:00:00 [mdrecoveryd] root 1285 2 0 Dec15 ? 00:00:00 [spinupd] root 1286 2 0 Dec15 ? 00:00:00 [spinupd] root 1287 2 0 Dec15 ? 00:00:00 [spinupd] root 1289 1 0 Dec15 ? 00:00:00 /bin/bash /boot/unmenu/uu root 1290 1 0 Dec15 ? 00:00:00 logger -tunmenu -plocal7.info -i root 1293 1289 0 Dec15 ? 00:00:00 awk -W re-interval -f ./unmenu.a root 1408 2 0 Dec15 ? 00:00:41 [unraidd] root 1427 2 0 Dec15 ? 00:00:00 [reiserfs/0] root 1641 1 0 Dec15 ? 00:03:01 /usr/local/sbin/shfs /mnt/user - root 1681 1 0 Dec15 ? 00:00:00 /boot/twonkymedia/twonkymedia root 1682 1 0 Dec15 tty1 00:00:00 /sbin/agetty 38400 tty1 linux root 1683 1 0 Dec15 tty2 00:00:00 /sbin/agetty 38400 tty2 linux root 1684 1 0 Dec15 tty3 00:00:00 /sbin/agetty 38400 tty3 linux root 1685 1 0 Dec15 tty4 00:00:00 /sbin/agetty 38400 tty4 linux root 1686 1 0 Dec15 tty5 00:00:00 /sbin/agetty 38400 tty5 linux root 1687 1 0 Dec15 tty6 00:00:00 /sbin/agetty 38400 tty6 linux root 1690 1681 0 Dec15 ? 00:03:32 /boot/twonkymedia/twonkymediaser root 8929 1262 0 Dec19 ? 00:01:47 /usr/sbin/smbd -D root 9121 1262 0 Dec19 ? 00:00:41 /usr/sbin/smbd -D root 10369 1690 0 06:37 ? 00:00:00 [mediafusion-int] <defunct> root 14017 1 0 21:15 ? 00:00:00 /bin/sh /usr/bin/mysqld_safe --d root 14049 14017 0 21:15 ? 00:00:00 /usr/libexec/mysqld --basedir=/u root 14086 1236 0 21:17 ? 00:00:00 in.telnetd: 192.168.1.4 root 14087 14086 0 21:17 pts/0 00:00:00 -bash root 14225 2 0 21:32 ? 00:00:00 [flush-9:1] root 14247 14087 0 21:33 pts/0 00:00:00 ps -ef root@MediaServer:/mnt/disk1/slimserver# Quote Link to comment
joshpond Posted December 21, 2010 Share Posted December 21, 2010 Trying to use memory from a long time ago but try opening a web browser with address: tower:9000 (if yours is called tower) I think you had to start the slimserver up sign up for an account scan media etc first....... maybe...... Josh Quote Link to comment
foo_fighter Posted December 24, 2010 Share Posted December 24, 2010 Hi Matt, Very helpful post. I used your instructions, but there are a few modifications/optimizations that I did: I've just updated my SBS install to the latest nightly version of 7.6 and kept all preferences, plugins intact. Here's a quick guide for anyone that's interested: I would kill the currently running SBS process first! 1. Unrar the new package and move to new install directory: • tar -xf squeezeboxserver-7.x.x.tgz • mv squeezeboxserver-7.x.x. ./SBS_new_install/ 2. Permissions of directories and files needs to be 755: • chmod -R 755 ./SBS_new_install/ 3. Copy across the Prefs, Plugins, Cache and Logs directories from the old installation: • cp -pR ./SBS_old_install/prefs ./SBS_new_install/ • cp -pR ./SBS_old_install/Plugins ./SBS_new_install/ • cp -pR ./SBS_old_install/Cache ./SBS_new_install/ • cp -pR ./SBS_old_install/Logs ./SBS_new_install/ 4. Ownership of root program directory needs to be changed (I use slimserer:1000 for some reason!): • chown -R slimserver:1000 ./SBS_new_install (I never had to do this in the past...but it probably won't hurt.) 5. ln -s SBS_new_install slimserver (This way you can keep the old ones around but re-link the latest back to slimserver and you don't have to keep changing the prefs I didn't even rename it in step 1, just kept the complete version number exactly as it untarred) 7. Start up the new installation: • perl /slimserver/slimserver.pl --daemon --user slimserver >/dev/null 2>&1 & Quote Link to comment
starcat Posted January 7, 2011 Share Posted January 7, 2011 Anyone tried running Slimserver off a (separate, reiserfs formatted) USB stick? How intensive are the Log updates? Quote Link to comment
joshpond Posted January 7, 2011 Share Posted January 7, 2011 Mainly because of the log files causing the drives to spin up all the time, I've shifted the audio stuff off the unRAID server and copied all the files onto another server I'm trying to get up (LinuxMCE). Josh Quote Link to comment
goinsnoopin Posted January 7, 2011 Share Posted January 7, 2011 Matt or foo_fighter, I have two questions about the update process: Can you clarify what slimserver:1000 is? Is it the username you defined or is it the root folder of the original install? This part is confusing me. Also in step 7 you say to run: perl /slimserver/slimserver.pl --daemon --user slimserver >/dev/null 2>&1 & what does the: >/dev/null 2>&1 & at the end do? I previously only typed everything up to this point. Also one last question. Where have you kept your playlists - I assume in a directory and what permissions did you use for this directory? Thanks, Dan Quote Link to comment
starcat Posted January 7, 2011 Share Posted January 7, 2011 Can you clarify what slimserver:1000 is? Is it the username you defined or is it the root folder of the original install? This part is confusing me. slimserver is the user and 1000 is the GID it belongs to, i.e. the Group ID. Check /etc/group to found out the associated name. Also in step 7 you say to run: perl /slimserver/slimserver.pl --daemon --user slimserver >/dev/null 2>&1 & what does the: >/dev/null 2>&1 & at the end do? I previously only typed everything up to this point. stdout and stderr goes to /dev/null, i.e. output and errors won't be shown anywhere. You may ignore this of course, then you will see the output in the xterm or logfile, etc... depending where you run the command. Also one last question. Where have you kept your playlists - I assume in a directory and what permissions did you use for this directory? Same as the other directories. I would suggest the following directory hierarchy: SlimServer/ SlimServer/Library SlimServer/Playlists SlimServer/TrackStat where SlimServer is best a link to the version you use (but may be the directory itself of course). In TrackStat you put the output from Erland's TrackStat and Library is a link to the user share containing your audio. Quote Link to comment
Bolle Posted January 7, 2011 Share Posted January 7, 2011 Yes, extreme thanks indeed to everyone! I had no chance without you. Here's the summary of actions I did to get this working, for the record. For UnRaid 4.5.6 & Squeezebox Server 7.5.2: Downloaded & installed UnMenu Start unmenu Navigate to Unmenu in browser: //tower:8080 (if this doesn't work and your ISP is hijacking your DNS search, then in Win7, go to Control Panel -> Network and Internet -> Network Connections. Right click on the connection icon -> Properties. Click on IP Version 4, Properties. At the bottom, radio button "Use the following DNS server address:" fill in 8.8.8.8 to use Google, or find another that you like) Click on Package Manager Perl: Download-install and enable on start up MySQL: Download-install Telnet into Tower, and run: cd /mnt/disk1 chmod -R 777 slimserver chmod -R 777 Music\ Listening (or the name of your music directory) echo >> /etc/passwd echo slimserver:$1$oExleBv6$Ux2qBpAanWMqJqUeH2xqp1:1000:100:,,,:/home/slimserver:/bin/bash >> /etc/passwd chown -R slimserver.users . cd slimserver perl slimserver.pl --daemon --user slimserver To see if it's running run: ps- ef Will see a series of apps at the bottom that start "/mnt/disk1/slimserver/bin/i386- ...." I'm following this instruction to get SB server working on my unRAID box so I can ditch my atom based Vortexbox music server, consolidating the amount of boxes in my home (although that might be rethought seeing the comments about SB server spinning up all disks...). Therefore I downloaded and installed perl and mysql through unmenu. However, whilst not paying any attention, I accidentaly installed the mysql files on disk1. This while my music is on disk2, so it makes more sense to put the mysql files there as well? Can I just copy the files over to disk2, or delete and reinstall on the preferred disk? Could use some advice... Quote Link to comment
starcat Posted January 7, 2011 Share Posted January 7, 2011 chown -R slimserver.users . There is at least one typo, above command should read: chown -R slimserver:users . Quote Link to comment
starcat Posted January 7, 2011 Share Posted January 7, 2011 I'm following this instruction to get SB server working on my unRAID box so I can ditch my atom based Vortexbox music server, consolidating the amount of boxes in my home (although that might be rethought seeing the comments about SB server spinning up all disks...). Slim would spin the disks of course. You may install it on an SSD if you want the otherdisks to spin down. However, I am not sure if the server will go to sleep if SS is running all the time (but you may check for clients and if all they are not playing - easily to check through the SlimSever cmdline interface - then initiate S3. You may use the SSD for other stuff too, like the YAMJ library. Vortexbox is different app. You may have for instance several of them and replicate (a single local) library between them (using rsync), use them to rip and have them play locally (unRAID can't and needs an SB client). So, depending on needs both are excellent but different solutions, even being based on the same SlimServer software and idea. Quote Link to comment
goinsnoopin Posted January 7, 2011 Share Posted January 7, 2011 Starcat, Thanks for the information. I have slimserver running on disk1 and I have all my music in a directory called Music on this disk. In your response you said: "Library is a link to the user share containing your audio". I would love to move my music to a user share. Can you explain what you mean by a link and how you would do this? Is there anything special about permissions and setting this up. Thanks, Dan Quote Link to comment
starcat Posted January 7, 2011 Share Posted January 7, 2011 The link you may change later on the fly; this is the advantage of using links (you don't have to copy your source directories, only change links from within other directories). You may start with having Library pointing to your /mnt/disk1/Music for instance, the generic command would be: ln -s <targetdir> <linkdir> # and to remove the link, you invoke rm <linkdir> or in your case, if you installed SlimServer in /mnt/disk1/SlimServer ln -s /mnt/disk1/Music /mnt/disk1/SlimServer/Library I would suggest in addition to the above three directories, to have the following SlimServer/SlimServer -> link to currently used SS installation SlimServer/Logs SlimServer/Library SlimServer/Playlists SlimServer/TrackStat SlimServer/whatever_v7.2 SlimServer/whatever_v7.5 SlimServer/whatever_latest then link in SlimServer/SlimServer for instance to SlimServer/whatever_latest SlimServer/Library may be also a directory, containing several links if you have your audio spread over several disks and do not use User Shares, something like SlimServer/Library/Music -> link to /mnt/disk1/Music SlimServer/Library/audio2 -> whatever directory containg audio2 SlimServer/Library/audio3 -> whatever directory containing audio3 Then your library is comprised of everything that is in Music, audio2 and audio3 and you specify a single path for your library: SlimServer/Library ... Quote Link to comment
Bolle Posted January 7, 2011 Share Posted January 7, 2011 Slim would spin the disks of course. You may install it on an SSD if you want the otherdisks to spin down. However, I am not sure if the server will go to sleep if SS is running all the time (but you may check for clients and if all they are not playing - easily to check through the SlimSever cmdline interface - then initiate S3. You may use the SSD for other stuff too, like the YAMJ library. Vortexbox is different app. You may have for instance several of them and replicate (a single local) library between them (using rsync), use them to rip and have them play locally (unRAID can't and needs an SB client). So, depending on needs both are excellent but different solutions, even being based on the same SlimServer software and idea. So if I understand you correctly, if you install SB Server on one disk the other disks will not be spun up? Does this have to be an SSD disk, or could I also use an USB stick? Regarding going to sleep, I use the 'Server Power Control' plug-in in SB Server which controls S3 sleep within certain timeslots and no active SB clients. I suppose I can use this plugin on SB server on the unRAID box as well to command S3 sleep? My Vortexbox is now solely used as an SB server and storage for music files. The ripping function is hardly used as I mostly rip from my iMAC using XLD as this gives me full control over all parameters. I also used it as a torrent client, but will migrate this to my unRAID server next week when I install a cache disk. For replay I solely use SB clients (SB Touch in living room, SB radio in bedroom, Squeezeplay on my iMac) Using the Vortexbox as my music source, my unRAID server now provides a backup of the collection by syncing the folders over the network. But I also back the music up to an external USB disk, and with parity protection on the unRAID server I might feel comfortable with just using the unRAID server as the music source. So the need to keep the Vortexbox server is decreasing, if with a limited bit of fiddling I can get SB Server working on unRAID (without it spinning up all the disks...) I would remove the Vortexbox server to consolidate boxes. I hope unRAID 5 will provide easier support for SB Server. I already have a friend willing to buy the Vortexbox server from me, or I'll stick an mITX atom/ION mainboard in it to replace my Apple TV as XMBC hardware. (it's an DIY Vortexbox Server in a rather livingroom friendly mITX case) Quote Link to comment
starcat Posted January 7, 2011 Share Posted January 7, 2011 So if I understand you correctly, if you install SB Server on one disk the other disks will not be spun up? Does this have to be an SSD disk, or could I also use an USB stick? USB is too slow for all the log updates. If you turn all logging off and if you format it with reiserfs, then theoretically yes. Regarding going to sleep, I use the 'Server Power Control' plug-in in SB Server which controls S3 sleep within certain timeslots and no active SB clients. I suppose I can use this plugin on SB server on the unRAID box as well to command S3 sleep? Yes, it may be adapted. But checking the player status is really simple. And unRAID has it's own S3 script where this check might be performed. You may need to experiment, all depends on your needs (and skills). So the need to keep the Vortexbox server is decreasing, if with a limited bit of fiddling I can get SB Server working on unRAID (without it spinning up all the disks...) I would remove the Vortexbox server to consolidate boxes. Sounds reasonable, yes. I just wanted to point out that Vortexbox may be used slightly different too, that it also contains a player, etc. Quote Link to comment
Bolle Posted January 7, 2011 Share Posted January 7, 2011 Thank you. Unfortunately my Linux skills are minimal, so might be wiser to keep the Vortexbox server untill an 'easier' implementation of SB server on unRAID is developed. Quote Link to comment
joshpond Posted January 7, 2011 Share Posted January 7, 2011 @starcat, just curious With having slimserver on a ssd, that would stop the log files causing spinup of the disk it is installed on. Does slimserver also cause spinup of other disks to scan automatically or does it only scan when directed to? ie. I had slimserver and music installed on disk1 and found parity and disk 1 would spin up a couple of times a day but occasionally other disks as well. I also found that randomly maybe after a few days the slimserver process would kill itself and the squeezebox would stop working. Poor WAF so moved it all onto a Linux MCE server. Thanks Josh Quote Link to comment
starcat Posted January 7, 2011 Share Posted January 7, 2011 It only scans the Music Library in the specified path. It doesn't write to it, thus the parity disc would not be activated. The parity disc is activated only if SS logs to disk1 for example (or other writes) and disk1 is part of the array, so parity calc is performed on unRAID - at least those two discs would be active. If you put SlimServer on a disk that is not member of the array, the parity disk would not get activated. You may try this out with a spare disk outside of the array, later dump it to an SSD and grow the array with that spare disk (after pre-clearing it). Quote Link to comment
goinsnoopin Posted January 7, 2011 Share Posted January 7, 2011 Starcat, Thanks for all the great information, I can't wait to try this this weekend. I have been running the 7.5 version of slimserver for a year now and it has worked well. I am going to update to 7.52 this weekend. One of the issues that has plagued me is the addition of new songs. When I rip a cd and add music to my music folder the new music does not get picked up by an automatic or manual scan of slimserver. I assume this is a permissions /ownership issue. To pickup the new music I have to run the commands I found on page 8 of this thread: find . -type d -exec chmod 755 {} \; find . -type f -exec chmod 644 {} \; Are you able to get slimserver to automatically scan for new music? What permissions do you use for each folder that you recommended in your last reply to me. Thanks - all of you information has been very valuable to this linux newbie. Dan Quote Link to comment
starcat Posted January 7, 2011 Share Posted January 7, 2011 If you write data through Samba (CIFS) to unRAID, default permissions are controlled by the file found in /etc/samba/smb-shares.conf - however this files is auto generated on unRAID - will have to look up where this happens, but in general you need to set the 644 and 755 create permissions respectively for files and directories. I just see default create masks are set to 711 and 611 in /etc/samba/smb-names.conf, again auto-generated... Just look up where these files are generated and change the mask to 755 and 644 respectively. Edit: I think if you put the following in /boot/config/smb-extra.conf (and reboot), it will overwrite the default values (this is the last file read in by smb.conf) and all will be fine for you: create mask = 0644 directory mask = 0755 For home use, I don't see any reason why not to use 755/644 for all directories and files. Quote Link to comment
goinsnoopin Posted January 9, 2011 Share Posted January 9, 2011 Starcat, I updated and have everything running, thanks for the help! One quick question about the links...will they survive a reboot of the unraid server or will I need to make these links each time I reboot? I did not have a smb-extra.conf file so I added one to the root of my flash drive with just the text you had in your message. I am not sure it is working as the album was not picked up by a scan. After changing directory and file permissions manually they scanned. So I must not have something correct with the smb-extra.conf file. I'm going to research this some more. Thanks again! Dan Quote Link to comment
starcat Posted January 9, 2011 Share Posted January 9, 2011 Dan, The links as described above will survive a reboot as they would reside on the disks in the SlimServer installation directory. The create masks will affect only newly added files. So, if you had not added any files recently, they will not go and change permissions of existing files (this is what the find command is doing). So, check the /etc/samba/smb.conf, if there is a reference to smb-extra.conf (location should be /boot/config/smb-extra.conf) and if yes, you said you already rebooted, try to create a new file and directory via SMB and see on the cmd line what permissions do they get - should be 644 for files and 755 for directories, if everything works correct. In that case, from now on also newly added music will have the same permissions and thus it will be picked up during rescan. You definitely have a permission issues here, as SlimServer runs as different user. Next thing, while running SlimServer as a separate (non root) user is generally a good idea, I don't think this gives you any benefit in a home environment except for added headache and admin work... Hope this helps! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.