Ubuntu 16 unable to create 80-container-host0.network.dpkg-new

[Eugene Shcherban]

When I distro upgrade Ubuntu 16x64 I get:

The following packages will be upgraded:
  libudev1 systemd udev
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 1,046 kB/4,686 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 udev amd64 229-4ubuntu8 [990 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libudev1 amd64 229-4ubuntu8 [56.5 kB]
Fetched 1,046 kB in 1s (977 kB/s)
Reading changelogs... Done
(Reading database ... 122160 files and directories currently installed.)
Preparing to unpack .../systemd_229-4ubuntu8_amd64.deb ...
+ set -e
+ [ upgrade = remove ]
+ dpkg-maintscript-helper rm_conffile /etc/X11/xinit/xinitrc.d/50-systemd-user.sh 228-3~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper rm_conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 228-5~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-journald.conf /etc/systemd/journald.conf 204-1~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-logind.conf /etc/systemd/logind.conf 204-1~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemd-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemctl-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8
Unpacking systemd (229-4ubuntu8) over (229-4ubuntu7) ...
dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb (--unpack):
 unable to create '/lib/systemd/network/80-container-host0.network.dpkg-new' (while processing './lib/systemd/network/80-container-host0.network'): No such file or directory
No apport report written because the error message indicates an issue on the local system
                                                                                         dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for dbus (1.10.6-1ubuntu3) ...
Errors were encountered while processing:
 /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Pitt (pitti)]

Please file bugs with ubuntu-bug; there should already be a crash report with the apt, dmesg, and other interesting logs.

This is most likely due to a corrupted file system or RAM; it could be a bug in dpkg (although very unlikely). Can you reproduce this after a clean boot and "sudo apt-get -f install"?

[Eugene Shcherban (shcherban-ev)]

OK. I went and check fs:

root@rescue:~# fsck -f /dev/xvda1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
cloudimg-rootfs: 578609/2732032 files (0.3% non-contiguous), 4052539/8388608 blocks
root@rescue:~#

then restarted the VPS and attempted apt-get update/upgrade:

-----------------------
root@VPS:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 libpam-systemd : Depends: systemd (= 229-4ubuntu8) but 229-4ubuntu7 is installed
 systemd : Depends: libsystemd0 (= 229-4ubuntu7) but 229-4ubuntu8 is installed
E: Unmet dependencies. Try using -f.

root@VPS:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  systemd
Suggested packages:
  systemd-ui systemd-container
The following packages will be upgraded:
  systemd
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
Need to get 3,639 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu8 [3,639 kB]
Fetched 3,639 kB in 1s (2,835 kB/s)
Reading changelogs... Done
(Reading database ... 122160 files and directories currently installed.)
Preparing to unpack .../systemd_229-4ubuntu8_amd64.deb ...
+ set -e
+ [ upgrade = remove ]
+ dpkg-maintscript-helper rm_conffile /etc/X11/xinit/xinitrc.d/50-systemd-user.sh 228-3~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper rm_conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 228-5~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-journald.conf /etc/systemd/journald.conf 204-1~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-logind.conf /etc/systemd/logind.conf 204-1~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemd-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8
+ dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemctl-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8
Unpacking systemd (229-4ubuntu8) over (229-4ubuntu7) ...
dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb (--unpack):
 unable to create '/lib/systemd/network/80-container-host0.network.dpkg-new' (while processing './lib/systemd/network/80-container-host0.network'): No such file or directory
No apport report written because the error message indicates an issue on the local system
                                                                                         dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
addgroup: The group `systemd-journal' already exists as a system group....

[Adrian Deac (adydeac)]

More details on this bug:
# touch /lib/systemd/network/80-container-host0.network.dpkg-new
touch: cannot touch '/lib/systemd/network/80-container-host0.network.dpkg-new': No such file or directory
# touch /lib/systemd/network/80-container-hodt0.network.dpkg-new
# rm -f /lib/systemd/network/80-container-hodt0.network.dpkg-new
# touch /lib/systemd/network/80-container-host0.network.dpkg-new
touch: cannot touch '/lib/systemd/network/80-container-host0.network.dpkg-new': No such file or directory
# touch /lib/systemd/network/80-container-jost0.network.dpkg-new
# rm -f /lib/systemd/network/80-container-jost0.network.dpkg-new

Are some file names somehow reserved? Or?

[Martin Pitt (pitti)]

Please give me the output of

  ls -l /lib/systemd/network/
  ls -ld /lib/systemd/network/
  strace -vvs1024 touch /lib/systemd/network/80-container-host0.network.dpkg-new

My best guess is that the directory is missing, and for some reason dpkg does not recreate it.

[Adrian Deac (adydeac)]

I thought the same initially, but the directory is there. And I can create any file, except /lib/systemd/network/80-container-host0.network.dpkg-new:

# ls -l /lib/systemd/network/
total 8
-rw-r--r-- 1 root root 0 Sep 16 06:56 80-container-hst0.dpkg-new.a
-rw-r--r-- 1 root root 482 Sep 16 06:41 80-container-ve.network
-rw-r--r-- 1 root root 80 Jul 12 16:28 99-default.link

# ls -ld /lib/systemd/network/
drwxr-xr-x 2 root root 4096 Sep 16 07:15 /lib/systemd/network/

# strace -vvs1024 touch /lib/systemd/network/80-container-host0.network.dpkg-new
[-] Error 0x7a911401 in attaching to process!

# strace touch /lib/systemd/network/80-container-host0.network.dpkg-new
[-] Error 0x7a911401 in attaching to process!

# uname -a
Linux xxxxxxx.xxx 4.4.21-rh35-20160915144431.xenU.x86_64 #1 SMP Thu Sep 15 14:53:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

# mount
/dev/xvda1 on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=3002528k,nr_inodes=750632,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=600796k,mode=700)

[Martin Pitt (pitti)]

# ls -l /lib/systemd/network/

That looks fine. So either that directory is still broken in the file system, or ...

> Linux xxxxxxx.xxx 4.4.21-rh35-20160915144431.xenU.x86_64 #1 SMP Thu Sep

This is not an Ubuntu kernel; some RedHat kernel built for Xen? Might it be possible that there are some SElinux rules which somehow prevent creation of that file? Anything in dmesg after the failed attempt?

> # strace -vvs1024 touch /lib/systemd/network/80-container-host0.network.dpkg-new
> [-] Error 0x7a911401 in attaching to process!

Err, what -- there must be some external security mechanism which prevents that, or indeed just file system corruption. Does "strace true" work?

[Adrian Deac (adydeac)]

No, that is an RimuHosting kernel.

I've switched to an Ubuntu kernel, still the same results:
# grep -i trace /proc/self/status
TracerPid: 0

# uname -a
Linux XXXXXXX.XXX 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:58:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

# strace true
[-] Error 0x7a911401 in attaching to process!

I guess it's compromised?

[Martin Pitt (pitti)]

Is there anything in dmesg after the failed touch or failed strace? Not sure what this could be still, unless the host's Xen kernel behaves that way (although that might only explain the strace, but certainly not the file system malfunction).

[Peter (pwillendrup)]

Hi there,

I can confirm the bug also - the affected system is not a Ubuntu but a Raspbian on armhf:

Reading changelogs... Done
(Reading database ... 138629 files and directories currently installed.)
Preparing to unpack .../systemd_215-17+deb8u5_armhf.deb ...
Unpacking systemd (215-17+deb8u5) over (215-17+deb8u4) ...
dpkg: error processing archive /var/cache/apt/archives/systemd_215-17+deb8u5_armhf.deb (--unpack):
 unable to create `/lib/systemd/network/80-container-host0.network.dpkg-new' (while processing `./lib/systemd/network/80-container-host0.network'): No such file or directory
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
addgroup: The group `systemd-journal' already exists as a system group. Exiting.

My kernel is this one:
Linux xxxxxxxx 4.1.13+ #826 PREEMPT Fri Nov 13 20:13:22 GMT 2015 armv6l GNU/Linux

Does anyone have ideas for a workaround?

[Peter (pwillendrup)]

BTW, I experimented a little:

* 80-container-host0.network.dpkg-new can not be created by e.g. touch
* 80-container-host.network.dpkg-new can
* 80-container-host1.network.dpkg-new can

[Brian Popp (bpopp)]

Having a similar issue with Debian Jessie (8):

error processing archive /var/cache/apt/archives/systemd_215-17+deb8u5_amd64.deb (--unpack):
unable to create `./lib/systemd/network/80-container-host-0.network.dpkg-new' (while processing `./lib/systemd/network/80-container-host0.network'): no such file or directory.

Like others, I've confirmed that I cannot create the above file using touch:

touch: cannot touch `/lib/systemd/network/80-container-host0.network.dpkg-new': No such file or directory

In my case, my system is no longer booting and is dropping into emergency mode with the following in the logs:

systemd[1]: Job dev-sda1.device/start timed out.
systemd[1]: Time out waiting for device dev-sda1.device

Not positive this is related, but it seems likely since all my partitions are mounting correctly and I've confirmed that there are no errors with fsck.

[Brian Popp (bpopp)]

Here's something else a little odd that I noticed. This fails:

touch 80-container-host0

But this works:

touch 80-container-host1

This works:

touch 80-container-host1.network.dpkg-new (notice host1 vs host0)

And then if I do:

mv 80-container-host1.network.dpkg-new 80-container-host0.network.dpkg-new

I get no error, but the file disappears. Never seen anything like this.

[Sebastian Jürges (sjuerges)]

@everyone with the Error 0x7a911401.

Your system has very likely been compromised:
/lib/libgrubd.so file is present and having the following checksums:

MD5 checksum is "300b1066d197ee94a97393c6c79e0f46"

# md5sum /lib/libgrubd.so
300b1066d197ee94a97393c6c79e0f46 /lib/libgrubd.so

SHA256 checksum "a3a5e17e45c5fc27a3dcc4d11b1d6eb67c1726bd1e4dbd873f5238040c6de5ce"

# sha256sum /lib/libgrubd.so
a3a5e17e45c5fc27a3dcc4d11b1d6eb67c1726bd1e4dbd873f5238040c6de5ce /lib/libgrubd.so

Resolution
Move library libgrubd.so to another location and comment reference for this library in /etc/ld.so.preload config:

# mv /lib/libgrubd.so /root
# cat /etc/ld.so.preload
#/lib/libgrubd.so

(via https://kb.plesk.com/en/129639)