@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
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.
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
** Changed in: ubuntu
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623774
Title:
Ubuntu 16 unable to create 80-container-host0.network.dpkg-new
To manage no
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
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) ove
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).
** Package changed: dpkg (Ubuntu) => ubuntu
--
You re
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 XXX.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 0x
# ls -l /lib/systemd/network/
That looks fine. So either that directory is still broken in the file
system, or ...
> Linux xxx.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 SE
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
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.
--
You received this bug noti
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-cont
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 s
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 i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623774
Title:
Ub
15 matches
Mail list logo
