Hi Ondřej,
I just found the reason why it didn't work only in OpenVZ container.
It's caused by enforced upstart package instead of sysvinit. In OpenVZ
Debian template is added file /etc/apt/preferences.d/parallels which
contains this:
Package: sysvinit
Pin: release c=main
Pin-Priority: -1
I guess it's done to get working reboot command as I found here
So I will comment out the checking availability of upstart in Knot init
script and it will be OK.
Best regards,
Zdenek
On 17.7.2014 18:29, Ondřej Surý wrote:
Hi Zdeněk,
upstart was never not supported on Debian 7 as init system, thus
the integration might not be ideal. I would suggest using some
other supervisor to keep your processes running (runit, daemontools,
systemd from backports).
Cheers,
Ondrej
--
Ondřej Surý -- Chief Science Officer
-------------------------------------------
CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC
Americka 23, 120 00 Praha 2, Czech Republic
mailto:ondrej.sury@nic.cz
http://nic.cz/
-------------------------------------------
----- Original Message -----
> From: "Zdeněk Zámečník" <zdenek.zamecnik(a)mauriceward.com>
> To: "Anand Buddhdev" <anandb(a)ripe.net>et>, knot-dns-users(a)lists.nic.cz
> Sent: Thursday, 17 July, 2014 18:24:05
> Subject: Re: [knot-dns-users] knot init in Debian
> Hi Anand,
> you are right. I just tried to remove package upstart and it works as I
> expected. I'm going to place it back as I understand it ensures the knot
> will start again in case of crash...
> Maybe it would be fine to modify the init script to get it work with
> upstart too.
>
> Thanks for the help! Best regards,
> Zdenek
>
>
> On 17.7.2014 16:47, Anand Buddhdev wrote:
>> On 17/07/2014 16:00, Zdeněk Zámečník wrote:
>>
>> Hi Zdenek,
>>
>>> I have following issue with Knot: when I try to stop it by command
>>> /etc/init.d/knot stop then the daemon is still running. If i run command
>>> knotc stop then it's stopped but immediately run again. If I kill it by
>>> command kill, it's the same...
>>>
>>> As I found the /etc/init.d/knot is not working at all and Knot is
>>> probably run during boot by /etc/init/knot.conf and I'm not able to
>>> control it. The "unkillable" proccess is named /usr/sbin/knotd -c
>>> /etc/knot/knot.conf
>> Looks like Knot is being run by upstart. In this case, killing Knot with
>> "kill" or "knotc stop" will cause it to be restarted by
upstart, because
>> upstart's job is to keep services running. You will have to stop it by
>> running "stop knot" or "initctl stop knot" (they are
equivalent).
>>
>> Regards,
>>
>> Anand Buddhdev
>> RIPE NCC
>
>
> _______________________________________________
> knot-dns-users mailing list
> knot-dns-users(a)lists.nic.cz
>
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users