Author Topic: systemd not fully working after upgrade to debian stretch  (Read 267 times)

Offline matzh

  • Newbie
  • *
  • Posts: 21
  • Karma: +2/-0
    • View Profile
systemd not fully working after upgrade to debian stretch
« on: August 27, 2017, 05:06:54 pm »
Hi,

Maybe someone here knows his way around well in the systemd tools/mechanism.
Since the upgrade to stretch, it turns out that some services do not start in systemd.
These seem to be all services that either include
  • PrivateTmp=true
  • ProtectHome=true
  • ProtectSystem=full

and maybe others.  It seems to be anything that requires access to or tries to set up protected tmpfs files per user.

I get for
Code: [Select]
$ systemctl status apache2
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2016-11-03 18:18:20 CET; 9 months 23 days ago

Nov 03 18:18:20 cubie2 systemd[1]: Starting The Apache HTTP Server...
Nov 03 18:18:20 cubie2 systemd[1]: apache2.service: Control process exited, code=exited status=226
Nov 03 18:18:20 cubie2 systemd[1]: Failed to start The Apache HTTP Server.
Nov 03 18:18:20 cubie2 systemd[1]: apache2.service: Unit entered failed state.
Nov 03 18:18:20 cubie2 systemd[1]: apache2.service: Failed with result 'exit-code'.
and
Code: [Select]
$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2017-08-27 22:48:39 CEST; 11min ago
     Docs: man:bluetoothd(8)
  Process: 2020 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=226/NAMESPACE)
 Main PID: 2020 (code=exited, status=226/NAMESPACE)
Aug 27 22:48:39 cubie2 systemd[1]: Starting Bluetooth service...
Aug 27 22:48:39 cubie2 systemd[2020]: bluetooth.service: Failed at step NAMESPACE spawning /usr/lib/bluetooth/bluetoothd: Bad file descriptor
Aug 27 22:48:39 cubie2 systemd[1]: bluetooth.service: Main process exited, code=exited, status=226/NAMESPACE
Aug 27 22:48:39 cubie2 systemd[1]: Failed to start Bluetooth service.
Aug 27 22:48:39 cubie2 systemd[1]: bluetooth.service: Unit entered failed state.
Aug 27 22:48:39 cubie2 systemd[1]: bluetooth.service: Failed with result 'exit-code'.

I also noticed the following (not sure if this is a problem)
Code: [Select]
$ systemctl status -- -.mount
● -.mount - Root Mount
   Loaded: error (Reason: No such file or directory)
   Active: active (mounted) since Thu 2016-11-03 18:16:42 CET; 9 months 23 days ago
    Where: /
     What: /dev/mmcblk0p2
   CGroup: /system.slice/-.mount

I can start up apache with apachectl -k start from the commandline and it runs stable.
However, I would like this to work properly.  Any ideas?

Offline rgmhtt

  • Full Member
  • ***
  • Posts: 165
  • Karma: +2/-1
    • View Profile
Re: systemd not fully working after upgrade to debian stretch
« Reply #1 on: August 27, 2017, 08:42:26 pm »
You can get more information with:

systemctl -l status

Or look in the appropriate log files.

I really can't help in detail with debian as I am Centos/Fedora...

But there I use systemd and systemctl fairly regularly.


Offline matzh

  • Newbie
  • *
  • Posts: 21
  • Karma: +2/-0
    • View Profile
Re: systemd not fully working after upgrade to debian stretch
« Reply #2 on: August 28, 2017, 05:52:43 pm »
Thanks.
the -l option to systemctl does not give me any more information, but the "Failed at step NAMESPACE spawning...."
What I noticed it that my /tmp was not mounted separately, as tmp.mount was in /usr/share/systemd/tmp.mount which was not found by systemd (why?)
I copied it to /lib/systemd/system and could mount it properly.
Still getting the same error.

This is probably not the ideal place to find systemd experts.  Any hints where I can post these questions?



Offline rgmhtt

  • Full Member
  • ***
  • Posts: 165
  • Karma: +2/-1
    • View Profile
Re: systemd not fully working after upgrade to debian stretch
« Reply #3 on: August 28, 2017, 07:30:31 pm »
I run Fedora and Centos.  I ask on the Fedora and Centos lists (both the regular and their specific ARM lists).

You are using Debian.  I would hope you have some connection already to those lists, if you are talking about dealing with systemd.  Ah systemd.  one of the services that so many Linux users love to complain about.

But then they want VM support...

Lots of things had to change to better support VMs.