Bug#644839: Bug #644839

2012-05-28 Thread Quentin PEYREGNE
Hello,

I seem to have the same issue on the next version (0.19gcd-2.1). I am
running on a openvz virtual machine. The previous version was running OK.

I am on both host and virtual machine latest Wheezy 64bits up-to-date
system (28/05/2012).

See logs below, if you want more details/tests, tell me. TY!

# uname -a
Linux vnas 2.6.32-5-openvz-amd64 #1 SMP Sun May 6 05:21:56 UTC 2012 x86_64
GNU/Linux

# aptitude install forked-daapd
The following partially installed packages will be configured:
  forked-daapd
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up forked-daapd (0.19gcd-2.1) ...
Starting RSP and DAAP media server: invoke-rc.d: initscript forked-daapd,
action start failed.
dpkg: error processing forked-daapd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 forked-daapd
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up forked-daapd (0.19gcd-2.1) ...
Starting RSP and DAAP media server: invoke-rc.d: initscript forked-daapd,
action start failed.
dpkg: error processing forked-daapd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 forked-daapd


# cat /var/log/dpkg.log
...
2012-05-28 19:14:12 startup packages configure
2012-05-28 19:14:12 configure forked-daapd:amd64 0.19gcd-2.1 none
2012-05-28 19:14:12 status half-configured forked-daapd:amd64 0.19gcd-2.1


Bug#644839: Bug #644839

2012-05-28 Thread Quentin PEYREGNE
Hello again,

Please ignore my previous message.

I saw that my vmachine was running 8 processes /usr/sbin/forked-daapd, and
it was taking 100% of my CPU on each core. (weird...?)

After I killed these process, the installation work fine, and my music
server is back, with normal CPU usage.

TY for your work !!

Quentin.