** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed: No
** Changed in: systemd (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed: No such
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation
No, it does now return with 1 too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed: No such file or directory" on
In this strace systemctl now exited with 1 as expected, so we have a
classic heisenbug :-/ Can you confirm that if you run it without strace
it still exits with 0?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Has using -vv any additional effect (because only -v is documented in
the strace manpage)? Anyways, in the attachments is the requested
output.
** Attachment added: "strace.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545707/+attachment/4644822/+files/strace.log
--
You
Please leave the status at incomplete until I actually understand what's
going on here.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Thanks sworddragon. Let's try that then:
sudo SYSTEMD_LOG_LEVEL=debug strace -fvvs1024 -o /tmp/t systemctl
enable tmp.mount
please copy the entire output and attach /tmp/t. I doubt that
this already tells me what's going on, but at least this is easy to do.
--
You received this bug
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed: No
And I thought the return code of 0 is another bug and have created
another report for it (which got already marked as a duplicate of this
bug). Anyways, here is the requested output:
root@ubuntu:~/tmp# find /{etc,lib,run}/systemd -name tmp.mount | xargs ls -l
find: ‘/run/systemd’: No such file or
@dino99: I know, you already said that in comment #18, but for you
"systemctl is-enabled tmp.mount" correctly exits with 1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Tested on 2 xenial install: one fresh, and a wily to xenial dist-
upgrade: get the same result
oem@u64:~$ sudo find /{etc,lib,run}/systemd -name tmp.mount | xargs ls -l
[sudo] password for oem:
total 261428
-rw--- 1 oem oem 267624448 Feb 12 07:42 core
drwxr-xr-x 2 oem oem 4096 Sep 1
# systemctl is-enabled tmp.mount ; echo $?
Failed to get unit file state for tmp.mount: No such file or directory
0
Ouch, so systemctl exiting successfully (with 0) for a nonexisting
tmp.mount is indeed bad, and would cause this bug. dino99 correctly gets
an "1" there, so dino99 and Sworddragon
Here is the requested output:
root@ubuntu:~# systemctl is-enabled tmp.mount ; echo $?
Failed to get unit file state for tmp.mount: No such file or directory
0
root@ubuntu:~# systemctl status tmp.mount
Failed to connect to bus: No such file or directory
root@ubuntu:~# ls -l
oem@u64:~$ sudo dpkg-reconfigure systemd
[sudo] password for oem:
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Scanning the system, tmp.mount is only found into /ust/share/systemd/
oem@u64:~$ ls -la /usr/share/systemd/
total 28
drwxr-xr-x 2 root root 4096 Apr 12 13:08 .
drwxr-xr-x 342 root root 12288 Apr 13 09:22 ..
-rw-r--r-- 1 root root 3564 Apr 12 12:34 kbd-model-map
-rw-r--r-- 1 root root
oem@u64:~$ systemctl is-enabled tmp.mount ; echo $?
Failed to get unit file state for tmp.mount: No such file or directory 1
oem@u64:~$ sudo systemctl status tmp.mount
[sudo] password for oem:
● tmp.mount
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
So this isn't the code path of "Do a one-time migration of the RAMTMP
setting", but the code path of "Re-run systemctl enable for any service
that was enabled when preinst was run", as per the trace in comment 7.
+ read UNIT
+ [ tmp.mount = tmp.mount ]
+ dpkg --compare-versions 229-1ubuntu2 lt-nl
FTR, it's not just about having a /run/systemd/generator/tmp.mount if
you have an fstab entry like "none /tmp/ tmpfs defaults 0 0", because
with that "systemctl --quiet is-enabled tmp.mount" fails and thus
shouldn't be added to was-enabled. So I still cannot reproduce this nor
have an idea what's
** Changed in: systemd (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed: No such file
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Still get it with 229-3ubuntu1 on xenial 64 bits
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed: No
I'm still seeing the issue in this version of systemd.
** Changed in: systemd (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This bug was fixed in the package systemd - 229-2ubuntu1
---
systemd (229-2ubuntu1) xenial; urgency=medium
* Merge with Debian unstable. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
Upgrade
@Michael: Indeed /etc/ will override /run. My gut feeling is that
/etc/fstab should have precedence over /etc/default/rcS, so I guess we
should refine the check to not copy the unit if there already is a
tmp.mount? This can only be done when already running systemd, though.
--
You received this
@pitti: will /etc/systemd/system/tmp.mount override a /tmp mount point
from /etc/fstab (/run vs /etc)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error
Thanks! Much clearer now, and trivially reproducible: Mount /tmp
manually or from /etc/fstab), and try to run "systemctl enable
tmp.mount".
Fixed by http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=c59ff5c9ec6
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
root@ubuntu:~# sed -i '2 s/^/set -x/' /var/lib/dpkg/info/systemd.postinst
root@ubuntu:~# dpkg-reconfigure systemd
+ set -e
+ [ configure = triggered ]
+ dpkg --compare-versions 229-1ubuntu2 lt 214-1
+ dpkg --compare-versions 229-1ubuntu2 lt 218-11~
+ dpkg --compare-versions 229-1ubuntu2 lt
Ah, I thought this would happen if there already was a tmp.mount in
systemd's brain (e. g. from a manual mount or fstab) and then adding the
unit to /etc would cause that. But indeed I cannot reproduce this
either.
So, Sworddragon, please do the steps in comment #1.
** Changed in: systemd
> Ah, so you set RAMTMP=yes in /etc/default/rcS.
This file does contain only commented and empty lines on my system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
An explicit reload should not be necessary for "enable".
I also can't reproduce the problem:
$ cp /usr/share/systemd/tmp.mount /etc/systemd/system/tmp2.mount
$ systemctl enable tmp2.mount
Created symlink from /etc/systemd/system/local-fs.target.wants/tmp2.mount to
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed:
Ah, so you set RAMTMP=yes in /etc/default/rcS. There's a daemon-reload
missing indeed.
Thanks!
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of
The error message appears after the line "systemctl enable tmp.mount".
Manually calling this command does also show the error:
root@ubuntu:~# systemctl enable tmp.mount
Operation failed: No such file or directory
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received
Can you please do this:
sudo sed -i '2 s/^/set -x/' /var/lib/dpkg/info/systemd.postinst
sudo dpkg-reconfigure systemd
and copy the entire output? Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
36 matches
Mail list logo
