Sorry for hacking this topic. My issue is closely related to this.
I have the same problems as topic starter and have been running tru the steps mentioned
I figured it was going to be easy-peasy as:
Code: Select all
admin@b3:~$ /etc/init.d/forked-daapd status
forked-daapd is not running.
So I issued:
Code: Select all
admin@b3:~$ /etc/init.d/forked-daapd start
But this resulted in:
Code: Select all
Starting RSP and DAAP media server: Could not open logfile /var/log/forked-daapd.log: Permission denied
Could not reinitialize log facility with config file settings
okay, so:
Code: Select all
admin@b3:~$ ls -l /var/log/forked-daapd.log
-rw-r--r-- 1 daapd root 409 Apr 24 20:27 /var/log/forked-daapd.log
Can anyone confirm these permissions, and if not post the settings for his B3 server?
I'm not really the kind of person giving everything and everywhere the 777
Thank you!
EDIT:
Forgot to mention I'm on:
Code: Select all
2.5.1.2
Detailed information
Package name Package version
bubba 2.5.1.2
bubba-album 2.5.1.3
bubba-backend 2.5.1.5
bubba-frontend 2.5.1.6
bubba3-kernel 1:2.6.39.4-11
filetransferdaemon 0.55
logitechmediaserver 7.7.2.dfsg1-1
grmbll sorry for my too fast posting...
permission denied was off course because I was logged in as admin and not root
Nevertheless I still can't start forked-daapd. In the log it's mentioning:
"Unable to open database file"
Found my problem (mind the owner for forked-daapd):
Code: Select all
root@b3:/var/cache# ls -l
total 48
drwxr-xr-x 3 www-data www-data 4096 Mar 30 22:12 apache2
drwxr-xr-x 3 root root 4096 Apr 24 20:44 apt
drwxr-xr-x 2 root root 4096 Mar 29 2012 bubba-notify
drwxr-xr-x 2 root root 4096 Apr 12 2012 cracklib
drwxrwxr-x 3 root lp 4096 Mar 31 10:47 cups
drwxr-xr-x 3 root root 4096 Apr 12 2012 dbconfig-common
drwxr-xr-x 2 root root 4096 Mar 30 22:14 debconf
drwxr-xr-x 3 dnsmasq root 4096 Apr 24 22:09 forked-daapd
drwx------ 2 root root 4096 Mar 31 09:29 ldconfig
drwxr-sr-x 29 man root 4096 Apr 24 06:25 man
drwxr-xr-x 3 root root 4096 Apr 24 22:12 samba
drwxr-xr-x 2 root root 4096 Mar 30 21:22 web-admin
in /etc/forked-daapd.conf is saw that uid is daapd
=> so the db file songs3.db could never be created
Changed owner to daapd:root and it works.
Can someone from excito confirm/explain why dnsmasq is the owner for that directory. Is this supposed to and need I to revert and change something else? Or is it a bug?
(