On Fri, 2016-04-22 at 15:57 +0200, Guus Sliepen wrote:
> The sks package contains an init script that does not depend on
> $network
> in its LSB header, so it is likely that it is being started before
> the
> network is brought up.
Indeed... thanks for catching that :)


> Therefore I'm reassigning this to the sks package. Christoph, as a
> workaround you can just configure sks to bind to 0.0.0.0 and ::.
Sure...


> > 
> > Interestingly, sks runs two daemons (or better said the same one in
> > two modes,
> > db and recon)... db always succeeds to start up, while recon always
> > fails.
> Are they both binding to specific addresses, or just recon? Maybe it
> helps if you send us your /etc/sks/sksconf.
Yes they are, and I just remembered why it works for db:
hkp_address: localhost
recon_address: 1.2.3.4 a:b:c:d::1:2

it's because it binds to localhost, which in turn is then reverse
proxied by apache httpd ;-)



Cheers,
Chris.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to