no music, nor firefly access

[Valgard]

Hi Guys,


my b3 came online today, updated himself to 2.4, i setup an user account for me and copied some of my music into /storage/music/albums; inside this albums folder are my digital cds, when i try to hear them over the internet with my smartphone or tablet with the b3 frontend http://...myownb3.com/admin/music no music is displayed, nor i get access to the firefly server with common admin/excito phrase like the manual told me?? whats going wrong?

so how to setup my files, that i can use them everywhere?

thx for help
Chris

[Valgard]

anyone can login in his firefly server since 2.4?
http://b3:3689
admin pw: excito won´t work?

can`t use fireplay function because my music is not recognized (

anyone a tip who to bring my b3 to recognize my music?

greetings
Chris

[Binkem]

In version 2.4 Firefly media server has been exchanged for forked-daapd.There is no web-server for Forked-daapd.

[blacklodge]

Why have an login screen then?

Same for me, can't login

[Cheeseboy]

I had some problems myself earlier, and tried to access the web admin interface in order to find out what was going on...
It is no longer there in forked-daapd as Binkem said.
The login prompt is probably just something that has been left in there...
From /etc/forked-daapd.conf:

Code: Select all

# Admin password for the non-existent web interface
admin_password = "unused"

You should be able to see your music in http://b3/admin/music though...
If not, try editing the file mentioned above, and change the log level:

Code: Select all

# Available levels: fatal, log, warning, info, debug, spam
loglevel = info

Then restart the daap streaming service from the web interface or from the command prompt:

Code: Select all

sudo /etc/init.d/forked-daapd restart

You should now hopefully get more information in /var/log/forked-daapd.log.
Unfortunately this log file does not seem to be viewable from the web interface...

[pulp]

Did you turn on DAAP streaming service?

[pompopom]

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?