Daemons and deboostrap

Daemons and deboostrap

[Alexander Smirnov]

Hi all,

testing patches from mailing list I've found the problem with the 
current next: there are lots of daemons remain running after build is 
complete (./scripts/ci_build.sh -q).

8<--

$ ps ax
...
24785 ?        Ssl    0:00 /usr/bin/qemu-arm-static /usr/sbin/sshd
25085 ?        Ssl    0:00 /usr/bin/qemu-arm-static /usr/bin/dbus-daemon 
--system
  3046 ?        Ssl    0:00 /usr/bin/qemu-arm-static 
/usr/bin/dbus-daemon --system
  4582 ?        Ss     0:00 /usr/bin/dbus-daemon --system
  8577 ?        Ssl    0:00 /usr/bin/qemu-arm-static 
/usr/bin/dbus-daemon --system
...

8<--

There was dedicated code for multistrap, which prevents daemons start 
inside chroot, but it was dropped during switch to debootstrap. Seems it 
should be restored.

-- 
With best regards,
Alexander Smirnov

ilbers GmbH
Baierbrunner Str. 28c
D-81379 Munich
+49 (89) 122 67 24-0
http://ilbers.de/
Commercial register Munich, HRB 214197
General manager: Baurzhan Ismagulov

Re: Daemons and deboostrap

[Alexander Smirnov]

On 05/27/2018 07:00 PM, Alexander Smirnov wrote:
> Hi all,
> 
> testing patches from mailing list I've found the problem with the 
> current next: there are lots of daemons remain running after build is 
> complete (./scripts/ci_build.sh -q).
> 
> 8<--
> 
> $ ps ax
> ...
> 24785 ?        Ssl    0:00 /usr/bin/qemu-arm-static /usr/sbin/sshd
> 25085 ?        Ssl    0:00 /usr/bin/qemu-arm-static /usr/bin/dbus-daemon 
> --system
>   3046 ?        Ssl    0:00 /usr/bin/qemu-arm-static 
> /usr/bin/dbus-daemon --system
>   4582 ?        Ss     0:00 /usr/bin/dbus-daemon --system
>   8577 ?        Ssl    0:00 /usr/bin/qemu-arm-static 
> /usr/bin/dbus-daemon --system
> ...
> 
> 8<--
>

CI server contains tens of dbus processes, so it's not the issue of my host.

Alex


> There was dedicated code for multistrap, which prevents daemons start 
> inside chroot, but it was dropped during switch to debootstrap. Seems it 
> should be restored.
> 

Re: Daemons and deboostrap

[Jan Kiszka]

On 2018-05-27 21:30, Alexander Smirnov wrote:
> On 05/27/2018 07:00 PM, Alexander Smirnov wrote:
>> Hi all,
>>
>> testing patches from mailing list I've found the problem with the
>> current next: there are lots of daemons remain running after build is
>> complete (./scripts/ci_build.sh -q).
>>
>> 8<--
>>
>> $ ps ax
>> ...
>> 24785 ?        Ssl    0:00 /usr/bin/qemu-arm-static /usr/sbin/sshd
>> 25085 ?        Ssl    0:00 /usr/bin/qemu-arm-static
>> /usr/bin/dbus-daemon --system
>>   3046 ?        Ssl    0:00 /usr/bin/qemu-arm-static
>> /usr/bin/dbus-daemon --system
>>   4582 ?        Ss     0:00 /usr/bin/dbus-daemon --system
>>   8577 ?        Ssl    0:00 /usr/bin/qemu-arm-static
>> /usr/bin/dbus-daemon --system
>> ...
>>
>> 8<--
>>
> 
> CI server contains tens of dbus processes, so it's not the issue of my
> host.

Likely not noticed by us here as we usually build in containers, and
they tear down those daemons once your build is done.

That said, seems reasonable to restore some daemon startup prevention
then, maybe now with clearer comments why that is needed - I vaguely
recall an internal discussion where the reasons for the existence of
that measures remain open.

Jan

Re: Daemons and deboostrap

[Claudius Heine]

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

Hi,

On Wed, 2018-05-30 at 19:30 +0200, Jan Kiszka wrote:
> On 2018-05-27 21:30, Alexander Smirnov wrote:
> > On 05/27/2018 07:00 PM, Alexander Smirnov wrote:
> > > Hi all,
> > > 
> > > testing patches from mailing list I've found the problem with the
> > > current next: there are lots of daemons remain running after
> > > build is
> > > complete (./scripts/ci_build.sh -q).
> > > 
> > > 8<--
> > > 
> > > $ ps ax
> > > ...
> > > 24785 ?        Ssl    0:00 /usr/bin/qemu-arm-static
> > > /usr/sbin/sshd
> > > 25085 ?        Ssl    0:00 /usr/bin/qemu-arm-static
> > > /usr/bin/dbus-daemon --system
> > >   3046 ?        Ssl    0:00 /usr/bin/qemu-arm-static
> > > /usr/bin/dbus-daemon --system
> > >   4582 ?        Ss     0:00 /usr/bin/dbus-daemon --system
> > >   8577 ?        Ssl    0:00 /usr/bin/qemu-arm-static
> > > /usr/bin/dbus-daemon --system
> > > ...
> > > 
> > > 8<--
> > > 
> > 
> > CI server contains tens of dbus processes, so it's not the issue of
> > my
> > host.
> 
> Likely not noticed by us here as we usually build in containers, and
> they tear down those daemons once your build is done.

I normally don't exit the container after a build so it should be
happening there as well, but it didn't for me.
I might have to spend some time testing with different packages in
order to reproduce this, but I am pretty sure I tried installing
openssh before.

> That said, seems reasonable to restore some daemon startup prevention
> then, maybe now with clearer comments why that is needed - I vaguely
> recall an internal discussion where the reasons for the existence of
> that measures remain open.

Since installing debian via chroot and debootstrap is one of the
official supported ways of doing it, I would suspect that starting
daemons within that environment should be prevented upstream.

Maybe take a look at how the debian-installer handles this?

Cheers,
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

            PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                              Keyserver: hkp://pool.sks-keyservers.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Daemons and deboostrap

[Claudius Heine]

[-- Attachment #1: Type: text/plain, Size: 2858 bytes --]

On Fri, 2018-06-01 at 08:42 +0200, Claudius Heine wrote:
> Hi,
> 
> On Wed, 2018-05-30 at 19:30 +0200, Jan Kiszka wrote:
> > On 2018-05-27 21:30, Alexander Smirnov wrote:
> > > On 05/27/2018 07:00 PM, Alexander Smirnov wrote:
> > > > Hi all,
> > > > 
> > > > testing patches from mailing list I've found the problem with
> > > > the
> > > > current next: there are lots of daemons remain running after
> > > > build is
> > > > complete (./scripts/ci_build.sh -q).
> > > > 
> > > > 8<--
> > > > 
> > > > $ ps ax
> > > > ...
> > > > 24785 ?        Ssl    0:00 /usr/bin/qemu-arm-static
> > > > /usr/sbin/sshd
> > > > 25085 ?        Ssl    0:00 /usr/bin/qemu-arm-static
> > > > /usr/bin/dbus-daemon --system
> > > >   3046 ?        Ssl    0:00 /usr/bin/qemu-arm-static
> > > > /usr/bin/dbus-daemon --system
> > > >   4582 ?        Ss     0:00 /usr/bin/dbus-daemon --system
> > > >   8577 ?        Ssl    0:00 /usr/bin/qemu-arm-static
> > > > /usr/bin/dbus-daemon --system
> > > > ...
> > > > 
> > > > 8<--
> > > > 
> > > 
> > > CI server contains tens of dbus processes, so it's not the issue
> > > of
> > > my
> > > host.
> > 
> > Likely not noticed by us here as we usually build in containers,
> > and
> > they tear down those daemons once your build is done.
> 
> I normally don't exit the container after a build so it should be
> happening there as well, but it didn't for me.
> I might have to spend some time testing with different packages in
> order to reproduce this, but I am pretty sure I tried installing
> openssh before.
> 
> > That said, seems reasonable to restore some daemon startup
> > prevention
> > then, maybe now with clearer comments why that is needed - I
> > vaguely
> > recall an internal discussion where the reasons for the existence
> > of
> > that measures remain open.
> 
> Since installing debian via chroot and debootstrap is one of the
> official supported ways of doing it, I would suspect that starting
> daemons within that environment should be prevented upstream.
> 
> Maybe take a look at how the debian-installer handles this?

I took a look at the debian-installer code and they divert it as well
[1]. So we have to implement something like this as well.

That code is interesting, we might want to copy more than just the
daemon-start-stop divertion process.

Cheers,
Claudius


[1] https://salsa.debian.org/installer-team/debian-installer-utils/blob
/master/chroot-setup.sh#L66

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

            PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                              Keyserver: hkp://pool.sks-keyservers.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]