Bug#893369: systemd-udevd is killed at startup
Am 22.03.2018 um 10:24 schrieb LEDUQUE Mickaël: > Ah yes. > I'm not sure you'll get much more from my system and logs now, can I > install systemd:amd64 back now ? Please go ahead and install systemd:amd64 again. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#893369: systemd-udevd is killed at startup
Ah yes. I'm not sure you'll get much more from my system and logs now, can I install systemd:amd64 back now ? 2018-03-21 16:08 GMT+01:00 Michael Biebl : > Am 19.03.2018 um 16:36 schrieb LEDUQUE Mickaël: > > Start-Date: 2018-03-15 09:28:21 > > Commandline: apt dist-upgrade > > [..] > > > Remove: bundler:amd64 (1.15.1-1), systemd:amd64 (237-4), > > ruby-bundler:amd64 (1.15.1-1) > > End-Date: 2018-03-15 09:28:29 > > > > Also it seems at some point I had systemd:amd64 237-4 and many other > > packages as 238-2. > > Strangely I find no mention of removing system:amd64 even though > > See above: Remove: ... systemd:amd64 (237-4) > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#893369: systemd-udevd is killed at startup
Am 19.03.2018 um 16:36 schrieb LEDUQUE Mickaël: > Start-Date: 2018-03-15 09:28:21 > Commandline: apt dist-upgrade [..] > Remove: bundler:amd64 (1.15.1-1), systemd:amd64 (237-4), > ruby-bundler:amd64 (1.15.1-1) > End-Date: 2018-03-15 09:28:29 > > Also it seems at some point I had systemd:amd64 237-4 and many other > packages as 238-2. > Strangely I find no mention of removing system:amd64 even though See above: Remove: ... systemd:amd64 (237-4) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#893369: systemd-udevd is killed at startup
Am 19.03.2018 um 09:51 schrieb LEDUQUE Mickaël: > You're right, but honestly, I have no idea how this happened : > > $ dpkg -l systemd > Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder > | > État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements > |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) > ||/ Nom > Version > Architecture Description > +++-=-=-=-=== > ii systemd:i386 > 238-2 > i386 system and service manager I have no idea how this happened either and why apt decided to replace systemd:amd64 with systemd:i386 on an amd64 system. But apparently you are not the only one, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893054 sounds like the user ran into a similar problem. Do you still have the apt logs (check /var/log/apt) which show the installation of systemd:i386 and removal of systemd:amd64? Julian, do you have an idea why something like this can happen? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#893369: systemd-udevd is killed at startup
Is it possible it could be because I put a package (I think it was a systemd package) on hold because apt warned me about a critical bug on systemd or udev about one week ago ? 2018-03-19 9:51 GMT+01:00 LEDUQUE Mickaël : > You're right, but honestly, I have no idea how this happened : > > $ dpkg -l systemd > Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder > | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/ > H=semi-installé/W=attend-traitement-déclenchements > |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) > ||/ Nom > Version Architecture > Description > +++- > =-=- > =-== > > = > ii systemd:i386 > 238-2 i386 > system and service manager > > > 2018-03-18 23:20 GMT+01:00 Michael Biebl : > >> Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël: >> > No I don't think I have one >> > dpkg -l udev only shows udev and64 >> >> what about systemd? i386 or amd64 >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> >
Bug#893369: systemd-udevd is killed at startup
You're right, but honestly, I have no idea how this happened : $ dpkg -l systemd Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Architecture Description +++-=-=-=-=== ii systemd:i386 238-2 i386 system and service manager 2018-03-18 23:20 GMT+01:00 Michael Biebl : > Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël: > > No I don't think I have one > > dpkg -l udev only shows udev and64 > > what about systemd? i386 or amd64 > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#893369: systemd-udevd is killed at startup
Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël: > No I don't think I have one > dpkg -l udev only shows udev and64 what about systemd? i386 or amd64 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#893369: systemd-udevd is killed at startup
No I don't think I have one dpkg -l udev only shows udev and64 2018-03-18 22:39 GMT+01:00 Michael Biebl : > Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël: > > Looks like commenting out > > > > SystemCallArchitectures=native > > > > fixes the issue. > > Does that mean you have a udev:i386 installed on a amd64 system? > > > > If so, that would basically be a duplicate of #869719 > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#893369: systemd-udevd is killed at startup
Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël: > Looks like commenting out > > SystemCallArchitectures=native > > fixes the issue. Does that mean you have a udev:i386 installed on a amd64 system? If so, that would basically be a duplicate of #869719 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#893369: systemd-udevd is killed at startup
Looks like commenting out SystemCallArchitectures=native fixes the issue. 2018-03-18 22:27 GMT+01:00 LEDUQUE Mickaël : > I disabled them all and got a normal startup. > Now I'll try to find the one (or more) that causes the problem. > Thanks. > > 2018-03-18 21:48 GMT+01:00 Michael Biebl : > >> Am 18.03.2018 um 20:38 schrieb Mickaël Leduque: >> > Package: systemd >> > Version: 238-2 >> > Followup-For: Bug #893369 >> > >> > It didn't work so I just added the options in /etc/default/grub. >> > Here are the journal and the systemctl list-jobs output (which is just >> "no jobs"). >> > >> >> Ok, thanks. >> Once you are dropped into the rescue shell, can you try running >> systemd-udevd manually, via >> /lib/systemd/systemd-udevd >> >> If that works, you can try disabling the security features in >> /lib/systemd/system/systemd-udevd.service >> by commenting out the lines >> >> MemoryDenyWriteExecute=yes >> RestrictRealtime=yes >> RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 >> SystemCallArchitectures=native >> LockPersonality=yes >> >> one by one and test if that makes a difference. >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> >
Bug#893369: systemd-udevd is killed at startup
I disabled them all and got a normal startup. Now I'll try to find the one (or more) that causes the problem. Thanks. 2018-03-18 21:48 GMT+01:00 Michael Biebl : > Am 18.03.2018 um 20:38 schrieb Mickaël Leduque: > > Package: systemd > > Version: 238-2 > > Followup-For: Bug #893369 > > > > It didn't work so I just added the options in /etc/default/grub. > > Here are the journal and the systemctl list-jobs output (which is just > "no jobs"). > > > > Ok, thanks. > Once you are dropped into the rescue shell, can you try running > systemd-udevd manually, via > /lib/systemd/systemd-udevd > > If that works, you can try disabling the security features in > /lib/systemd/system/systemd-udevd.service > by commenting out the lines > > MemoryDenyWriteExecute=yes > RestrictRealtime=yes > RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 > SystemCallArchitectures=native > LockPersonality=yes > > one by one and test if that makes a difference. > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#893369: systemd-udevd is killed at startup
Am 18.03.2018 um 20:38 schrieb Mickaël Leduque: > Package: systemd > Version: 238-2 > Followup-For: Bug #893369 > > It didn't work so I just added the options in /etc/default/grub. > Here are the journal and the systemctl list-jobs output (which is just "no > jobs"). > Ok, thanks. Once you are dropped into the rescue shell, can you try running systemd-udevd manually, via /lib/systemd/systemd-udevd If that works, you can try disabling the security features in /lib/systemd/system/systemd-udevd.service by commenting out the lines MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 SystemCallArchitectures=native LockPersonality=yes one by one and test if that makes a difference. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#893369: systemd-udevd is killed at startup
Package: systemd Version: 238-2 Followup-For: Bug #893369 It didn't work so I just added the options in /etc/default/grub. Here are the journal and the systemctl list-jobs output (which is just "no jobs"). -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.117 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.12-3 ii libaudit11:2.8.2-1 ii libblkid12.31.1-0.5 ii libc62.27-2 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.2-1 ii libgcrypt20 1.8.1-4 ii libgpg-error01.28-1 ii libidn11 1.33-2.1 ii libip4tc01.6.2-1 ii libkmod2 25-1 ii liblz4-1 0.0~r131-2+b1 ii liblzma5 5.2.2-1.3 ii libmount12.31.1-0.5 ii libpam0g 1.1.8-3.7 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2+b1 ii libsystemd0 238-2 ii mount2.31.1-0.5 ii procps 2:3.3.12-4 ii util-linux 2.31.1-0.5 Versions of packages systemd recommends: ii dbus1.12.6-2 ii libpam-systemd 238-2 Versions of packages systemd suggests: ii policykit-10.113-2 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.130 ii udev 238-2 -- no debconf information -- Logs begin at Fri 2017-10-06 17:03:19 CEST, end at Sun 2018-03-18 20:32:15 CET. -- mars 18 20:30:14 falkynkip kernel: microcode: microcode updated early to revision 0x1f, date = 2018-02-07 mars 18 20:30:14 falkynkip kernel: Linux version 4.15.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-3)) #1 SMP Debian 4.15.4-1 (2018-02-18) mars 18 20:30:14 falkynkip kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1-amd64 root=UUID=5fe70463-3aae-4be3-ac38-9a92ac404edb ro quiet init=/lib/systemd/systemd mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' mars 18 20:30:14 falkynkip kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 mars 18 20:30:14 falkynkip kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. mars 18 20:30:14 falkynkip kernel: e820: BIOS-provided physical RAM map: mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0x-0x0009d7ff] usable mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0x0009d800-0x0009] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0x000e-0x000f] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0x0010-0x1fff] usable mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0x2000-0x201f] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0x2020-0x40003fff] usable mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0x40004000-0x40004fff] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0x40005000-0xcced8fff] usable mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xcced9000-0xcd7fafff] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xcd7fb000-0xcd884fff] usable mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xcd885000-0xcd923fff] ACPI NVS mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xcd924000-0xce163fff] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xce164000-0xce164fff] usable mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xce165000-0xce1a7fff] ACPI NVS mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xce1a8000-0xcebfbfff] usable mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xcebfc000-0xceff1fff] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xceff2000-0xceff] usable mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xcf80-0xdf9f] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xf800-0xfbff] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xfec0-0xfec00fff] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 0xfed0-0xfed03fff] reserved mars 18 20:30:14 falkynkip kernel: BIOS-e82
Bug#893369: systemd-udevd is killed at startup
Ok, I was more searching for a way to do it from inside grub itself, but this will have to do. 2018-03-18 18:55 GMT+01:00 Michael Biebl : > Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël: > > I'll do all that, thanks. Do you know how I can set a correct keymap in > > the grub "e" text editor ? > > I don't. But this is literally the first google hit regarding that question > https://askubuntu.com/questions/751259/how-to- > change-grub-command-line-grub-shell-keyboard-layout > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#893369: systemd-udevd is killed at startup
Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël: > I'll do all that, thanks. Do you know how I can set a correct keymap in > the grub "e" text editor ? I don't. But this is literally the first google hit regarding that question https://askubuntu.com/questions/751259/how-to-change-grub-command-line-grub-shell-keyboard-layout -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#893369: systemd-udevd is killed at startup
I'll do all that, thanks. Do you know how I can set a correct keymap in the grub "e" text editor ? 2018-03-18 16:57 GMT+01:00 Michael Biebl : > On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?= > wrote: > > Package: systemd > > Version: 238-2 > > Severity: critical > > Justification: breaks the whole system > > > > Dear Maintainer, > > > > After an update and a restart of the system, boot fails. It enters a > loop, where (apparently) systemd-udevd fails to start and is retries for a > certain time. > > After thaat, I am dropped into recovery mode (or failsafe, I don't > remember the word). > > I tried investigating the logs, but I couldn't go very far, I just saw > something that may (or may nt) be related, seccomp logs about systemd-udevd > using a syscall > > but that's an "audit" log so I'm not sure it does anyhting at all. > > See https://freedesktop.org/wiki/Software/systemd/Debugging/ > "If You Can Get a Shell", and attach the journalctl output of such a boot. > Since this affects udev, please also consider adding > udev.log_priority=debug to the kernel command line (see man > kernel-command-line) > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#893369: systemd-udevd is killed at startup
On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?= wrote: > Package: systemd > Version: 238-2 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > After an update and a restart of the system, boot fails. It enters a loop, > where (apparently) systemd-udevd fails to start and is retries for a certain > time. > After thaat, I am dropped into recovery mode (or failsafe, I don't remember > the word). > I tried investigating the logs, but I couldn't go very far, I just saw > something that may (or may nt) be related, seccomp logs about systemd-udevd > using a syscall > but that's an "audit" log so I'm not sure it does anyhting at all. See https://freedesktop.org/wiki/Software/systemd/Debugging/ "If You Can Get a Shell", and attach the journalctl output of such a boot. Since this affects udev, please also consider adding udev.log_priority=debug to the kernel command line (see man kernel-command-line) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#893369: systemd-udevd is killed at startup
Package: systemd Version: 238-2 Severity: critical Justification: breaks the whole system Dear Maintainer, After an update and a restart of the system, boot fails. It enters a loop, where (apparently) systemd-udevd fails to start and is retries for a certain time. After thaat, I am dropped into recovery mode (or failsafe, I don't remember the word). I tried investigating the logs, but I couldn't go very far, I just saw something that may (or may nt) be related, seccomp logs about systemd-udevd using a syscall but that's an "audit" log so I'm not sure it does anyhting at all. -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.117 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.12-3 ii libaudit11:2.8.2-1 ii libblkid12.31.1-0.5 ii libc62.27-2 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.2-1 ii libgcrypt20 1.8.1-4 ii libgpg-error01.28-1 ii libidn11 1.33-2.1 ii libip4tc01.6.2-1 ii libkmod2 25-1 ii liblz4-1 0.0~r131-2+b1 ii liblzma5 5.2.2-1.3 ii libmount12.31.1-0.5 ii libpam0g 1.1.8-3.7 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2+b1 ii libsystemd0 238-2 ii mount2.31.1-0.5 ii procps 2:3.3.12-4 ii util-linux 2.31.1-0.5 Versions of packages systemd recommends: ii dbus1.12.6-2 ii libpam-systemd 238-2 Versions of packages systemd suggests: ii policykit-10.113-2 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.130 ii udev 238-2 -- no debconf information [MASKED] /etc/systemd/system/bootlogs.service -> /lib/systemd/system/bootlogs.service [MASKED] /etc/systemd/system/bootmisc.service -> /lib/systemd/system/bootmisc.service [MASKED] /etc/systemd/system/checkfs.service -> /lib/systemd/system/checkfs.service [MASKED] /etc/systemd/system/checkroot-bootclean.service -> /lib/systemd/system/checkroot-bootclean.service [MASKED] /etc/systemd/system/checkroot.service -> /lib/systemd/system/checkroot.service [MASKED] /etc/systemd/system/halt.service -> /lib/systemd/system/halt.service [MASKED] /etc/systemd/system/hostname.service -> /lib/systemd/system/hostname.service [MASKED] /etc/systemd/system/killprocs.service -> /lib/systemd/system/killprocs.service [MASKED] /etc/systemd/system/motd.service -> /lib/systemd/system/motd.service [MASKED] /etc/systemd/system/mountall-bootclean.service -> /lib/systemd/system/mountall-bootclean.service [MASKED] /etc/systemd/system/mountall.service -> /lib/systemd/system/mountall.service [MASKED] /etc/systemd/system/mountdevsubfs.service -> /lib/systemd/system/mountdevsubfs.service [MASKED] /etc/systemd/system/mountkernfs.service -> /lib/systemd/system/mountkernfs.service [MASKED] /etc/systemd/system/mountnfs-bootclean.service -> /lib/systemd/system/mountnfs-bootclean.service [MASKED] /etc/systemd/system/mountnfs.service -> /lib/systemd/system/mountnfs.service [MASKED] /etc/systemd/system/rc.local.service -> /lib/systemd/system/rc.local.service [MASKED] /etc/systemd/system/reboot.service -> /lib/systemd/system/reboot.service [MASKED] /etc/systemd/system/rmnologin.service -> /lib/systemd/system/rmnologin.service [MASKED] /etc/systemd/system/samba-ad-dc.service -> /lib/systemd/system/samba-ad-dc.service [MASKED] /etc/systemd/system/sendsigs.service -> /lib/systemd/system/sendsigs.service [MASKED] /etc/systemd/system/single.service -> /lib/systemd/system/single.service [MASKED] /etc/systemd/system/umountfs.service -> /lib/systemd/system/umountfs.service [MASKED] /etc/systemd/system/umountnfs.service -> /lib/systemd/system/umountnfs.service [MASKED] /etc/systemd/system/umountroot.service -> /lib/systemd/system/umountroot.service [MASKED] /etc/systemd/system/urandom.service -> /lib/systemd/system/urandom.service [EXTENDED] /lib/systemd/system/rc-local.service -> /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-resolved.service -> /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf 27 overridden configuration files found. Failed to create bus connection: No such file or directory ==> /var/lib/systemd/deb-systemd-helper-enabled/dnsmasq.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/dnsmasq.service ==> /var/lib/systemd/deb-systemd-helper-enabled/resolvcon