sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Andy Ruddock
Subject: Re: [Sks-devel] debian sks start from init file fails
Date: Fri, 13 Mar 2009 18:09:32 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12 (Ubuntu-1.1.12+nobinonly-0ubuntu1)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Phil Pennock wrote:
> 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.

If the Debian install is anything like the Ubuntu one, then the pid
files are stored in /var/run/sks/sksdb.pid & /var/run/sks/sksrecon.pid.
The problem is that /var/run is mounted as a temporary filesystem and
the sks sub-directory doesn't exist.
You'll need to create the /var/run/sks directory, and set its owner to
debian-sks before starting the daemons.

I documented it here :

http://tinyurl.com/az9w2h

- --
Andy Ruddock
- ------------
address@hidden (GPG Key ID 0xA622D452)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkm6k0IACgkQfSkWkaYi1FLXPACeP7jUlxULRIEIjZeWKpoNhF3D
cm8An2jfG1zs2bf45n76HvBeivVDRhNX
=U7EN
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]