The start script is messed up OR disco doesn't write the right PID to
the .pid file. The effect of this bug is that disco actually works (on
my workstation), but upon instalation of every package it throws an
error like that.
Can you confirm that /etc/disco/disco.conf doesn't exist as it seems
based on the above message?
It might be the known PID issue, as suggested by Pawel, which causes
an error message but Disco still works. Or it might be a new bug.
Ville
>> Setting up disco-node (0.2.1) ...
>> .: 25: Can't open /etc/disco/disco.conf
>> invoke-rc.d: initscript disco-node, action "start" failed.
>> dpkg: error processing disco-node (--configure):
>> subprocess post-installation script returned error exit status 2
>> Processing triggers for libc6 ...
>> ldconfig deferred processing now taking place
>> Processing triggers for python-support ...
>> Errors were encountered while processing:
>> disco-node
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Can you confirm that /etc/disco/disco.conf doesn't exist as it seems
> based on the above message?
>
> It might be the known PID issue, as suggested by Pawel, which causes
> an error message but Disco still works. Or it might be a new bug.
The file does not exist, the only content of /etc/disco is a link for
lighttpd.conf which points at a non existent file:
metson@disco-master:~/disco-0.2.1$ ls -lh /etc/disco/
total 0
lrwxrwxrwx 1 root root 18 2009-06-18 17:37 lighttpd.conf -> lighttpd-
node.conf
I think I'm going to use the packages to install the dependancies and
then install disco from source.
Cheers
Simon
I opened a new ticket for this issue
http://github.com/tuulos/disco/issues#issue/13
I'll have a look at it for the next release.
Thanks for the bug report!
Ville