systemd-resolved crashing with “Failed to set up mount namespacing: Invalid argument” &...





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















Problem



I'm trying to investigate this weird error where systemd-resolved is constantly crashing on 2 out of 4 machines. The one thing different with these two problematic machines (that I can think of), is that they are mounting a samba/cifs filesystem exported from machine #3 (on which systemd-resolved is running fine).



How do I get to the bottom of this?



OS



# cat /etc/lsb-release 

DISTRIB_ID=Ubuntu

DISTRIB_RELEASE=18.04

DISTRIB_CODENAME=bionic

DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"



# uname -a

Linux prod-delayed-jobs 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux



# systemd --version

systemd 237

+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid


Relevant journalctl output



Notice the /dev/null is not a device. line in the logs. This is occurring multiple times - during, before, and after systemd-resolved crashes.



Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPREQUEST of [REDACTED-IP-ADDRESS] on eth0 to 172.31.1.1 port 67 (xid=0x730cc4e4)

Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPACK of [REDACTED-IP-ADDRESS] from 172.31.1.1

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopping Network Name Resolution...

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...

Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument

Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...

Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: bound to [REDACTED-IP-ADDRESS] -- renewal in 32497 seconds.

Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument

Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.

Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...

Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument

Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved

Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE

Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.

Feb 12 14:23:22 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.

Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.

Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 3.



/etc/fstab contents - in case this is relevant



UUID=2f54e8e6-ff9c-497a-88ea-ce159f6cd283 /               ext4    discard,errors=remount-ro 0       1

/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0

//[REDACTED]/uploaded_files /home/myuser/shared cifs rw,username=myuser,password=[REDACTED],uid=myuser,gid=myuser 0 0


Few systemd configuration files are pointing to /dev/null



This is the case on all the 4 machines, however only 2 out of these 4 are having trouble with systemd-resolved. Strangely, hostname.service is pointing to /dev/null - wonder why?



lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogd.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootmisc.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkfs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot-bootclean.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks-early.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 fuse.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 halt.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 hostname.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 hwclock.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 killprocs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Apr 12  2018 lvm2.service -> /dev/null

lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm.service -> /dev/null

lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm-waitidle.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 motd.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall-bootclean.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountdevsubfs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountkernfs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs-bootclean.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Jan 16  2018 nfs-common.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 rc.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 rcS.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 reboot.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 rmnologin.service -> /dev/null

lrwxrwxrwx 1 root root    9 Dec  6 11:10 screen-cleanup.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 sendsigs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 single.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd-single.service -> /dev/null

lrwxrwxrwx 1 root root    9 Dec  6 11:07 sudo.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountfs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountnfs.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountroot.service -> /dev/null

lrwxrwxrwx 1 root root    9 Nov 15 21:45 x11-common.service -> /dev/null


/lib/systemd/system



[Unit]

Description=Network Name Resolution

Documentation=man:systemd-resolved.service(8)

Documentation=https://www.freedesktop.org/wiki/Software/systemd/resolved

Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers

Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

DefaultDependencies=no

After=systemd-sysusers.service systemd-networkd.service

Before=network.target nss-lookup.target shutdown.target

Conflicts=shutdown.target

Wants=nss-lookup.target



[Service]

Type=notify

Restart=always

RestartSec=0

ExecStart=!!/lib/systemd/systemd-resolved

WatchdogSec=3min

User=systemd-resolve

CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE

AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE

PrivateTmp=yes

PrivateDevices=yes

ProtectSystem=strict

ProtectHome=yes

ProtectControlGroups=yes

ProtectKernelTunables=yes

ProtectKernelModules=yes

MemoryDenyWriteExecute=yes

RestrictRealtime=yes

RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6

SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount @obsolete @raw-io @reboot @swap





18.04 samba systemd systemd-resolved







share|improve this question





























    0















    Problem



    I'm trying to investigate this weird error where systemd-resolved is constantly crashing on 2 out of 4 machines. The one thing different with these two problematic machines (that I can think of), is that they are mounting a samba/cifs filesystem exported from machine #3 (on which systemd-resolved is running fine).



    How do I get to the bottom of this?



    OS



    # cat /etc/lsb-release 
    
DISTRIB_ID=Ubuntu
    
DISTRIB_RELEASE=18.04
    
DISTRIB_CODENAME=bionic
    
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
    

    
# uname -a
    
Linux prod-delayed-jobs 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
    

    
# systemd --version
    
systemd 237
    
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid


    Relevant journalctl output



    Notice the /dev/null is not a device. line in the logs. This is occurring multiple times - during, before, and after systemd-resolved crashes.



    Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPREQUEST of [REDACTED-IP-ADDRESS] on eth0 to 172.31.1.1 port 67 (xid=0x730cc4e4)
    
Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPACK of [REDACTED-IP-ADDRESS] from 172.31.1.1
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopping Network Name Resolution...
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
    
Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
    
Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
    
Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: bound to [REDACTED-IP-ADDRESS] -- renewal in 32497 seconds.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
    
Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
    
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
    
Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
    
Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
    
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
    
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
    
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
    
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
    
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 3.



    /etc/fstab contents - in case this is relevant



    UUID=2f54e8e6-ff9c-497a-88ea-ce159f6cd283 /               ext4    discard,errors=remount-ro 0       1
    
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
    
//[REDACTED]/uploaded_files /home/myuser/shared cifs rw,username=myuser,password=[REDACTED],uid=myuser,gid=myuser 0 0


    Few systemd configuration files are pointing to /dev/null



    This is the case on all the 4 machines, however only 2 out of these 4 are having trouble with systemd-resolved. Strangely, hostname.service is pointing to /dev/null - wonder why?



    lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogd.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootmisc.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkfs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot-bootclean.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks-early.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 fuse.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 halt.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 hostname.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 hwclock.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 killprocs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Apr 12  2018 lvm2.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm-waitidle.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 motd.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall-bootclean.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountdevsubfs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountkernfs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs-bootclean.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Jan 16  2018 nfs-common.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rc.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rcS.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 reboot.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rmnologin.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Dec  6 11:10 screen-cleanup.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 sendsigs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 single.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd-single.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Dec  6 11:07 sudo.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountfs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountnfs.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountroot.service -> /dev/null
    
lrwxrwxrwx 1 root root    9 Nov 15 21:45 x11-common.service -> /dev/null


    /lib/systemd/system



    [Unit]
    
Description=Network Name Resolution
    
Documentation=man:systemd-resolved.service(8)
    
Documentation=https://www.freedesktop.org/wiki/Software/systemd/resolved
    
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
    
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
    
DefaultDependencies=no
    
After=systemd-sysusers.service systemd-networkd.service
    
Before=network.target nss-lookup.target shutdown.target
    
Conflicts=shutdown.target
    
Wants=nss-lookup.target
    

    
[Service]
    
Type=notify
    
Restart=always
    
RestartSec=0
    
ExecStart=!!/lib/systemd/systemd-resolved
    
WatchdogSec=3min
    
User=systemd-resolve
    
CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
    
AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
    
PrivateTmp=yes
    
PrivateDevices=yes
    
ProtectSystem=strict
    
ProtectHome=yes
    
ProtectControlGroups=yes
    
ProtectKernelTunables=yes
    
ProtectKernelModules=yes
    
MemoryDenyWriteExecute=yes
    
RestrictRealtime=yes
    
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
    
SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount @obsolete @raw-io @reboot @swap





    18.04 samba systemd systemd-resolved







    share|improve this question

























      0












      0








      0








      Problem



      I'm trying to investigate this weird error where systemd-resolved is constantly crashing on 2 out of 4 machines. The one thing different with these two problematic machines (that I can think of), is that they are mounting a samba/cifs filesystem exported from machine #3 (on which systemd-resolved is running fine).



      How do I get to the bottom of this?



      OS



      # cat /etc/lsb-release 
      
DISTRIB_ID=Ubuntu
      
DISTRIB_RELEASE=18.04
      
DISTRIB_CODENAME=bionic
      
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
      

      
# uname -a
      
Linux prod-delayed-jobs 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
      

      
# systemd --version
      
systemd 237
      
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid


      Relevant journalctl output



      Notice the /dev/null is not a device. line in the logs. This is occurring multiple times - during, before, and after systemd-resolved crashes.



      Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPREQUEST of [REDACTED-IP-ADDRESS] on eth0 to 172.31.1.1 port 67 (xid=0x730cc4e4)
      
Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPACK of [REDACTED-IP-ADDRESS] from 172.31.1.1
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopping Network Name Resolution...
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
      
Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
      
Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
      
Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: bound to [REDACTED-IP-ADDRESS] -- renewal in 32497 seconds.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
      
Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
      
Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
      
Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 3.



      /etc/fstab contents - in case this is relevant



      UUID=2f54e8e6-ff9c-497a-88ea-ce159f6cd283 /               ext4    discard,errors=remount-ro 0       1
      
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
      
//[REDACTED]/uploaded_files /home/myuser/shared cifs rw,username=myuser,password=[REDACTED],uid=myuser,gid=myuser 0 0


      Few systemd configuration files are pointing to /dev/null



      This is the case on all the 4 machines, however only 2 out of these 4 are having trouble with systemd-resolved. Strangely, hostname.service is pointing to /dev/null - wonder why?



      lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogd.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootmisc.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot-bootclean.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks-early.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 fuse.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 halt.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 hostname.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 hwclock.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 killprocs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Apr 12  2018 lvm2.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm-waitidle.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 motd.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall-bootclean.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountdevsubfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountkernfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs-bootclean.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Jan 16  2018 nfs-common.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rc.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rcS.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 reboot.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rmnologin.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Dec  6 11:10 screen-cleanup.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 sendsigs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 single.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd-single.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Dec  6 11:07 sudo.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountnfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountroot.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 x11-common.service -> /dev/null


      /lib/systemd/system



      [Unit]
      
Description=Network Name Resolution
      
Documentation=man:systemd-resolved.service(8)
      
Documentation=https://www.freedesktop.org/wiki/Software/systemd/resolved
      
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
      
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
      
DefaultDependencies=no
      
After=systemd-sysusers.service systemd-networkd.service
      
Before=network.target nss-lookup.target shutdown.target
      
Conflicts=shutdown.target
      
Wants=nss-lookup.target
      

      
[Service]
      
Type=notify
      
Restart=always
      
RestartSec=0
      
ExecStart=!!/lib/systemd/systemd-resolved
      
WatchdogSec=3min
      
User=systemd-resolve
      
CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
      
AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
      
PrivateTmp=yes
      
PrivateDevices=yes
      
ProtectSystem=strict
      
ProtectHome=yes
      
ProtectControlGroups=yes
      
ProtectKernelTunables=yes
      
ProtectKernelModules=yes
      
MemoryDenyWriteExecute=yes
      
RestrictRealtime=yes
      
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
      
SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount @obsolete @raw-io @reboot @swap





      18.04 samba systemd systemd-resolved







      share|improve this question














      Problem



      I'm trying to investigate this weird error where systemd-resolved is constantly crashing on 2 out of 4 machines. The one thing different with these two problematic machines (that I can think of), is that they are mounting a samba/cifs filesystem exported from machine #3 (on which systemd-resolved is running fine).



      How do I get to the bottom of this?



      OS



      # cat /etc/lsb-release 
      
DISTRIB_ID=Ubuntu
      
DISTRIB_RELEASE=18.04
      
DISTRIB_CODENAME=bionic
      
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
      

      
# uname -a
      
Linux prod-delayed-jobs 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
      

      
# systemd --version
      
systemd 237
      
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid


      Relevant journalctl output



      Notice the /dev/null is not a device. line in the logs. This is occurring multiple times - during, before, and after systemd-resolved crashes.



      Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPREQUEST of [REDACTED-IP-ADDRESS] on eth0 to 172.31.1.1 port 67 (xid=0x730cc4e4)
      
Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPACK of [REDACTED-IP-ADDRESS] from 172.31.1.1
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopping Network Name Resolution...
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
      
Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
      
Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
      
Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: bound to [REDACTED-IP-ADDRESS] -- renewal in 32497 seconds.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
      
Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
      
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
      
Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
      
Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
      
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 3.



      /etc/fstab contents - in case this is relevant



      UUID=2f54e8e6-ff9c-497a-88ea-ce159f6cd283 /               ext4    discard,errors=remount-ro 0       1
      
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
      
//[REDACTED]/uploaded_files /home/myuser/shared cifs rw,username=myuser,password=[REDACTED],uid=myuser,gid=myuser 0 0


      Few systemd configuration files are pointing to /dev/null



      This is the case on all the 4 machines, however only 2 out of these 4 are having trouble with systemd-resolved. Strangely, hostname.service is pointing to /dev/null - wonder why?



      lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogd.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootmisc.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot-bootclean.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks-early.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 fuse.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 halt.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 hostname.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 hwclock.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 killprocs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Apr 12  2018 lvm2.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm-waitidle.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 motd.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall-bootclean.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountdevsubfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountkernfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs-bootclean.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Jan 16  2018 nfs-common.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rc.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rcS.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 reboot.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rmnologin.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Dec  6 11:10 screen-cleanup.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 sendsigs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 single.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd-single.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Dec  6 11:07 sudo.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountnfs.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountroot.service -> /dev/null
      
lrwxrwxrwx 1 root root    9 Nov 15 21:45 x11-common.service -> /dev/null


      /lib/systemd/system



      [Unit]
      
Description=Network Name Resolution
      
Documentation=man:systemd-resolved.service(8)
      
Documentation=https://www.freedesktop.org/wiki/Software/systemd/resolved
      
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
      
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
      
DefaultDependencies=no
      
After=systemd-sysusers.service systemd-networkd.service
      
Before=network.target nss-lookup.target shutdown.target
      
Conflicts=shutdown.target
      
Wants=nss-lookup.target
      

      
[Service]
      
Type=notify
      
Restart=always
      
RestartSec=0
      
ExecStart=!!/lib/systemd/systemd-resolved
      
WatchdogSec=3min
      
User=systemd-resolve
      
CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
      
AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
      
PrivateTmp=yes
      
PrivateDevices=yes
      
ProtectSystem=strict
      
ProtectHome=yes
      
ProtectControlGroups=yes
      
ProtectKernelTunables=yes
      
ProtectKernelModules=yes
      
MemoryDenyWriteExecute=yes
      
RestrictRealtime=yes
      
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
      
SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount @obsolete @raw-io @reboot @swap





      18.04 samba systemd systemd-resolved




      18.04 samba systemd systemd-resolved






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 13 at 6:23









      Saurabh NandaSaurabh Nanda

      1013




      1013






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117842%2fsystemd-resolved-crashing-with-failed-to-set-up-mount-namespacing-invalid-argu%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117842%2fsystemd-resolved-crashing-with-failed-to-set-up-mount-namespacing-invalid-argu%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          Human spaceflight

          Image
          Human spaceflight From Wikipedia, the free encyclopedia Jump to navigation Jump to search "Space traveler" redirects here. For other uses, see Space traveler (disambiguation). @media all and (max-width:720px){.mw-parser-output .tmulti>.thumbinner{width:100%!important;max-width:none!important}.mw-parser-output .tmulti .tsingle{float:none!important;max-width:none!important;width:100%!important;text-align:center}} Apollo 11 crewmember Buzz Aldrin on the Moon, 1969 International Space Station crewmember Tracy Caldwell Dyson views the Earth, 2010 Space Shuttle Discovery heads into space with a crew aboard, STS-121 in 2006 Inside a space suit on the Canadarm, 1993 Human spaceflight (also referred to as crewed spaceflight or manned spaceflight ) is space travel with a crew or passengers aboard the spacecraft. Spacecraft carrying people may be operated directly, by human crew, or it may be e
          Read more

          Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

          Image
          0 1 What exactly does the error message beginning with E: mean? I assume it has to do with the file structure on Ubuntu-on-Windows, but what exactly? The following package was automatically installed and is no longer required: os-prober Use 'apt-get autoremove' to remove it. The following extra packages will be installed: libxslt1.1 The following NEW packages will be installed: libxslt1.1 xmlstarlet 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 435 kB of archives. After this operation, 1023 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ trusty/main libxslt1.1 amd64 1.1.28-2build1 [145 kB] Get:2 http://archive.ubuntu.com/ubuntu/ trusty/universe xmlstarlet amd64 1.5.0-1 [290 kB]
          Read more

          張江高科駅

          Image
          張江高科駅 ちょうこうこうか Zhangjiang Hi-Tech Park 所在地 中国上海市浦東新区 所属事業者 上海地鉄運営有限公司（上海軌道交通・駅詳細） 上海浦東現代有軌交通有限公司（駅詳細） テンプレートを表示 張江高科駅 各種表記 繁体字： 張江高科站 簡体字： 张江高科站 拼音 ： Zhàngjiāng Gāokē Zhàn 発音： ヂャンジャン ガオクー ヂャン 英文： Zhangjiang Hi-Tech Park Station テンプレートを表示 張江高科駅 （ちょうこうこうか-えき）は中華人民共和国上海市浦東新区に位置する、上海軌道交通2号線の駅である。 なお、張江高科駅前にある張江軌道電車の 張江地鉄駅駅 についてもここで述べる。 目次 1 利用可能な鉄道路線 2 沿革 3 駅構造 3.1 上海軌道交通 3.2 張江軌道電車 4 駅周辺 5 隣の駅 6 注釈 7 関連項目 利用可能な鉄道路線 上海軌道交通 ■ 2号線 上海浦東現代有軌交通有限公司 ■ 張江軌道電車 沿革 高架駅時代の姿 2000年12月27日 - 2号線の駅が高架駅として開業。 2010年 1月1日 - 張江軌道電車の開業に伴い、張江地鉄駅駅（停留所）を設置。 2月13日 - 駅地下化に伴い高架駅の運用停止。 2月24日 - 10日間の閉鎖を経て地下新駅の開業。 2017年2月9日 - リニューアル工事を経て再開業。乗降客の増加に対応し、ホームへのエレベーター、エスカレーターを増設、券売機エリアを拡張した [1] 。 駅構造 上海軌道交通 上海軌道交通 張江高科駅 5号口 ちょうこうこうか Zhangjiang Hi-Tech Park ◄ 竜陽路 (2.60km) (1.61km) 金科路 ► 所在地 中国上海市浦東新区松涛路 祖冲之路 （中国語版） 北緯31度12分11秒 東経121度34分50秒  /  北緯31.2
          Read more