Bug 4800 - Slimserver 6.5.0, 6.5.1 and 6.5.2 will not scan / rescan on Opensuse 10.2
: Slimserver 6.5.0, 6.5.1 and 6.5.2 will not scan / rescan on Opensuse 10.2
Status: RESOLVED INVALID
Product: Logitech Media Server
Classification: Unclassified
Component: Scanner
: 6.5.1
: PC SuSE Linux
: P1 normal (vote)
: ---
Assigned To: Ross Levine
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-03 12:58 UTC by Bernhard Laeng
Modified: 2007-03-20 15:09 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Laeng 2007-03-03 12:58:28 UTC
Hi

after a couple of months i found out why the slimserver 6.5.0, 6.5.1 and 6.5.1
on my Opensuse 10.2 will not scan or rescan the music.
The problem is, that the logfile has the owner and the group "root".
so i changed the /tmp/slimserver.log to the user "slimserver" and the
group "slimserver". Now it works perfect! 

that was the error meassage:
2007-03-03 21:15:22.6722 Setup::rescan - initiating scan of type: [rescan]
Can't write to >>/tmp/slimserver.log: Permission denied at /usr/local/slimserver/Slim/Utils/Misc.pm line 1117.
2007-03-03 21:15:23.8563 Got to the END.

This must be an bug in the slimserver! Most software modules writes to the log file as root. But only Misc.pm
wants to write als user "slimserver" and group "slimserver". In the version 6.3.1 the was no problem with the permissions.

have a nice day :-)!
Best regards
suseslim
Comment 1 Mark Miksis 2007-03-03 18:37:44 UTC
FWIW, the only time I've seen this problem is when the user mistakenly runs either slimserver.pl or scanner.pl as root.  I believe the conf file also will become owned by root after doing so.
Comment 2 Ross Levine 2007-03-05 16:28:51 UTC
I'll take a look at this in a little while, I'm downloading SuSE now. 
Comment 3 Ross Levine 2007-03-09 14:49:48 UTC
I'm not able to reproduce this using the default SuSE install instructions here:

http://wiki.slimdevices.com/index.cgi?SUSE102startupscripts

I'm running everything virtually so it's easy for me to clone a fresh SuSE install and install SlimServer and test this, and I've been unable to reproduce it with this means. I understand that your current install is probably not so easy to simply try the whole process again, but is there any way you could try this again? It sure seems like it's fine here. 

On a side note according to bug 4718 it seems it might be possible to incorporate the init script along with the RPM, but we might need to wait to hear from an RPM expert for help doing this. 
Comment 4 Mark Miksis 2007-03-12 19:54:38 UTC
Hi Ross,

I'm not really sure if this is a bug and I don't have time to play with it right now, but here are a few comments/suggestions that may or may not help :)
- I can confirm that I've seen the ownership of the conf file change.  In hindsight, I'm not 100% sure I've seen the same with the log file.
- Try deleting the conf file, log file and cache dir before running as root (simulates a fresh install)
- Try running both slimserver.pl and/or scanner.pl as root (maybe they don't both do the same thing)
- Try using the --logfile=/tmp/slimserver.log command line option.
- Try different variants of sudo, su and su - (the login shell, $HOME dir, etc may matter)

Good luck...
Comment 5 Ross Levine 2007-03-20 15:09:48 UTC
Well I'm still not able to produce this, perhaps it's a combination of things causing this issue. I'm going to mark this bug as invalid for now, if anyone else notices this in the future please feel free to re-open this bug and provide reproduction steps. P