Release notes for BUBBA|2 version 2.0

[pa]

This seems odd, there should not be anything in this release (from 1.3.1 -> 2.0) that would affect the transferspeeds.

What protocol are you using?

/PA

[wil]

Before I had 6.3 mb/sec. and after 2.0 (with no other changes, network, cables ie) I have 2.0 mb/sec.
Puma

Strange, using 'wget' in a loop to retrieve 100MB files (on a relative slow laptop) I get this:

Code: Select all

2010-04-29 12:47:32 (8.25 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:47:45 (8.89 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:47:59 (8.25 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:48:15 (7.40 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:48:30 (8.51 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:48:43 (8.48 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:48:57 (8.79 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:49:10 (8.71 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:49:25 (8.44 MB/s) - `100mb.bin' saved [104900000]
2010-04-29 12:49:43 (7.50 MB/s) - `100mb.bin' saved [104900000]
Average speed = 8.32 MB/s

Looks better than the 2MB/s you mention

[Puma]

Dear Pa,

I'm using a windows machine as allways wich samba enabled

Windows share file = on (which should be samba)

puma

[pa]

Have you rebooted after the upgrade?
If not, there is a possibility that you are running an old kernel.

/PA

[jonte]

The excito-crew have managed to get my Firefly-server up and running again

How? I still have the same problems with Firefly server, getting permission denied while trying to load/build the database even though I've changed mode of the music folder.

2010-04-20 13:29:18 (480241c0): Starting mp3 scan
2010-04-20 13:29:18 (480241c0): opendir: Permission denied

//Jonte

Any news on the Firefly folder permission issue?

//Jonte

[pa]

1. Check that the "runas" paramter in the config file (/etc/mt-daapd.conf) says www-data (not mtdaapd)
2. Check the permissions of the database

Code: Select all

 ls -l /var/cache/mt-daapd

should read something like:

Code: Select all

-rw-r--r-- 1 www-data www-data 2259968 Apr 21 11:37 songs3.db

If any of the above is incorrect, edit the config file, then remove the database and restart the service.

/PA

[jonte]

1. Check that the "runas" paramter in the config file (/etc/mt-daapd.conf) says www-data (not mtdaapd)
2. Check the permissions of the database

Code: Select all

 ls -l /var/cache/mt-daapd

should read something like:

Code: Select all

-rw-r--r-- 1 www-data www-data 2259968 Apr 21 11:37 songs3.db

Both checked, and correct, I'm afraid.
Also the musicdir is 777 these days.

Funny thing is, running a test: changing runas user in the config file from www-data to mt-daapd and chown the /var/cache/mt-daapd/ folder to mt-daapd instead of www-data makes the database load and mt-daapd serve my MP3 dir. But the web interface isn't functioning and this was not recommended by Excito as I recall it due to security reasons. Any help?

//Jonte

[efiggy]

Can't login to http://bubba/music

the log file output is:

2010-05-05 05:47:40 (4a1ff4e0): Thread 4: Entering ws_returnerror (401: Unauthorized)
2010-05-05 05:47:51 (4a1ff4e0): Thread 5: Entering ws_returnerror (401: Unauthorized)


here is the log when I rebooted my mt-daapd\

2010-05-05 05:44:45 (480241c0): Starting signal handler
2010-05-05 05:44:45 (480241c0): Starting rendezvous daemon
2010-05-05 05:44:45 (480241c0): Client running
2010-05-05 05:44:45 (480241c0): Initializing database
2010-05-05 05:44:54 (480241c0): Starting web server from /usr/share/mt-daapd/admin-root on port 3689
2010-05-05 05:44:54 (480241c0): Registering rendezvous names
2010-05-05 05:44:54 (480241c0): Serving 15567 songs. Startup complete in 9 seconds
2010-05-05 05:44:54 (480241c0): Rescanning database
2010-05-05 05:45:52 (490294e0): Thread 0: Entering ws_returnerror (401: Unauthorized)
2010-05-05 05:46:03 (490294e0): Thread 1: Entering ws_returnerror (401: Unauthorized)
2010-05-05 05:46:30 (490294e0): Thread 2: Entering ws_returnerror (401: Unauthorized)

[pa]

Jonte,

The problem with your setup was that the "/home/storage" folder did not have the "x" bit set for all uses anymore so the mt-daapd process (now owed by www-data) could not open the directory even though the music folder had enough privileges.

/PA

[tor]

Hi efiggy,

The reason that you see (401: Unauthorized) in the log file is due to you not being logged into the web-admin. If you first do that and then access http://bubba/music you should be able to reach mt-daapd's admin interface.

(This is a change in behavior from the earlier versions where you logged in directly to the admin interface)

/Tor

[jonte]

Jonte,

The problem with your setup was that the "/home/storage" folder did not have the "x" bit set for all uses anymore so the mt-daapd process (now owed by www-data) could not open the directory even though the music folder had enough privileges.

/PA

D'oh
Thanks for helping out PA!

//Jonte

[efiggy]

Thanks. It is okay now!

[eds_oyo]

I have a similar problem. I have tried all the different fixes stated in this thread, but had no luck yet.

This is the error message I get when browsing to http://bubba/music:
***************************************
502 Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /music.

Reason: DNS lookup failure for: localhost

Apache/2.2.9 (Debian) mod_fastcgi/2.4.2 PHP/5.2.6-5ex1 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8c Server at 84.48.89.194 Port 80

**************************************

Folder permissions:


drwxrwxrwt 8 root users 4096 May 4 23:19 storage

drwxrwxrwx 16 eirik users 4096 Apr 22 21:32 music

[eds_oyo]

I figured it out. My /etc/hosts was wrong, so i was not able to ping localhost.

my /etc/hosts no looks like this:

127.0.0.1 localhost localhost.localdomain
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Is that OK now or should i change it?

[Jockewhbg]

Tried to update and it seemed to go well but something probably went wrong. It seems to be stuck between versions. When trying to update again it fails, see log. Something wrong with Horde package. The webinterface is really slow and main page coming up is the old one. When selecting Administration I´ll come to the new page. Under Status it says Software version 1.2.4. Under software update it says something else, see log.
When trying to update manually in the prompt I´ll end up in a Horde database configuration and are being prompted with common-config and asked for a database password. What can I do?

/Jocke

May 30 10:11:42 bubba bubba-networkmanager: Starting up
May 30 10:12:42 bubba bubba-networkmanager: Server timed out, terminating
May 30 10:12:42 bubba bubba-networkmanager: Daemon terminating
May 30 10:12:42 bubba bubba-networkmanager: Shutting down
May 30 10:12:43 bubba php5-cgi: {"bubba-frontend":"1.9.69","bubba-backend":"2.0.0.2","bubba-album":"1.9.8","filetransferdaemon":"0.50.20","squeezecenter":"7.5.0.dfsg1-5"}
May 30 10:12:50 bubba bubba-networkmanager: Starting up
May 30 10:12:50 bubba Bubba::Hotfix[9720]: 0, Server starting
May 30 10:12:52 bubba php5-cgi: {"stop":0,"statusMessage":"Checking for hotfixes","done":0}
May 30 10:12:58 bubba last message repeated 4 times
May 30 10:12:59 bubba Bubba::Hotfix[9724]: 2, Status: Failed to verify response from server, proceeding with upgrade
May 30 10:13:00 bubba php5-cgi: {"stop":0,"statusMessage":"Failed to verify response from server, proceeding with upgrade","done":1}
May 30 10:13:04 bubba Bubba::Apt[9752]: 0, Server starting
May 30 10:13:06 bubba php5-cgi: {"done":0,"logs":{},"statusMessage":"","progress":0}
May 30 10:13:09 bubba php5-cgi: {"done":0,"logs":{},"statusMessage":"Verifying pre upgrade system integrity.","progress":0}
May 30 10:13:12 bubba last message repeated 2 times
May 30 10:13:14 bubba php5-cgi: {"error":1,"done":1,"logs":{"ERROR":[{"Data":"iF bubba-horde 3.3.5ex3 Horde installation for the bubba platform\n","Desc":"Failures found in package (dpkg) database, unable to continue with upgrade."}]},"statusMessage":"System integrity failure.","progress":100}