Re: [Sks-devel] debian sks start from init file fails

[Phil Pennock]

On 2009-03-13 at 08:44 +0100, Gab wrote:
> Hi!
> If i start sks with the usual debian way /etc/init.d/sks start or
> restart sksdb e sksrecon don't start living this error message:
> 
> > address@hidden:~# /etc/init.d/sks start
> > Starting sks daemons: sksdb.. sksrecon.. done.
> 
> Apparently go smooth but there's no server listening.
> If i restart it it says:
> 
> > address@hidden:~# /etc/init.d/sks restart
> > Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to kill 
> > 16818: No such process
> >  sksdb..start-stop-daemon: warning: failed to kill 16815: No such process
> >  done.
> > Starting sks daemons: sksdb.. sksrecon.. done.
> 
> If i launch sksdb& abd sksrecon& singulary all goes well:
> 
> > tcp        0      0 0.0.0.0:11370           0.0.0.0:*               LISTEN  
> >     0          134370      16673/sks       
> > tcp        0      0 0.0.0.0:11371           0.0.0.0:*               LISTEN  
> >     0          134346      16671/sks
> 
> I have executed one by one all commands inside sks_build.sh separately
> and all went well , i have never seen this behaviur .

Well, what about the logs, what do they say?

And what user owns all the files and which user is sks running as when
started by the init.d script?

Eg, if Debian is doing something like creating a Debian-sks user, then
you'll need to make sure that most of the sks directory area is
read-writeable by that user -- typically by making it owned by that
user.

pgpKye4uDFPu2.pgp
Description: PGP signature