[Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
** Also affects: open-vm-tools (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Artful) ** Changed in: open-vm-tools (Ubuntu Xenial) Status: Invalid => Triaged ** Changed in: open-vm-tools (Ubuntu Artful) Status: New => Triaged ** Changed in: open-vm-tools (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1750780 Title: Race with local file systems can make open-vm-tools fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756081] [NEW] journald is unable to attribute messages incoming from processes that exited their cgroup
Public bug reported: This is mostly an FYI and a tracker to link Upstream to Ubuntu. Background: I wondered why some of my services are missing just the most interesting "last" messages before dying. Unfortunately I found this is a known race and there seems to be no good fix yet. But I think this is important, so I wanted to make you aware. Especially the last few messages before a service is dying are important. If you see any way to fix this in Ubuntu as an interim solution until upstream has found "the right thing" to eventually solve it that would be great. Upstream issue (many dups onto this): https://github.com/systemd/systemd/issues/2913 One approach that was tried (but not accepted): https://lwn.net/Articles/580150/ ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #2913 https://github.com/systemd/systemd/issues/2913 ** Also affects: systemd via https://github.com/systemd/systemd/issues/2913 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1756081 Title: journald is unable to attribute messages incoming from processes that exited their cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1756081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754472] [NEW] autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there
Public bug reported: The test really seems to be triggered all of the time to resolve a flaky test. That is just not worth the test. But it provides goo coverage, so an override in britney would loose all that. Lets skip the offending test on the arch it is known to be flaky (s390x). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754472 Title: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
For open-vm-tools this issue will only exist with the planned backport of the newer version. Since we will not ship the broken backport as we found it in pre-checks the correct state for open-vm-tools in xenial is invalid. ** Changed in: open-vm-tools (Ubuntu Xenial) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1750780 Title: Race with local file systems can make open-vm-tools fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752705] Re: installation of mysql-server fails because postinst fails to shut down server
ubuntu@b-test:~$ sudo systemd-nspawn -D testmysql --bind /etc/resolv.conf /bin/bash Spawning container testmysql on /home/ubuntu/testmysql. Press ^] three times within 1s to kill container. Host and machine ids are equal (92544cb0ba5946158c7c4f9b57691fe3): refusing to link journals bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell Ok, in there with a shell Ok, it takes a long time but works: Setting up mysql-server-5.7 (5.7.21-1ubuntu1) ... invoke-rc.d: could not determine current runlevel * Stopping MySQL database server mysqld [ OK ] update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service. invoke-rc.d: could not determine current runlevel So this likely needs debug on your system why it fails for you. Adding systemd task for being nspawn related. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1752705 Title: installation of mysql-server fails because postinst fails to shut down server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1752705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
Installed another Xenial and Bionic in vmware to take a deper look. - Xenial (with backported open-vm-tools): affected - Bionic (with the interim fix reverted): no hit in several retries, explanation below Systemd fixed it (via our assumed implicit dependency). In Bionic the PrivateTmp gives it a dependency on systemd-tmpfile-setup.service (seen in systemd analyze, there might be more but not on crit path). This is configured by default to include /var/tmp in /usr/lib/tmpfiles.d/tmp.conf. In regard to your thoughts about later on changing cloud-init ordering that won't help you, as the dependency is there (implicit or explicit doesn't matter). For the xenial case where I reliably hit the issue instead of stracing I cut things short. A service with the following exposes exactly the same error: [Unit] Description=foo DefaultDependencies=no [Service] PrivateTmp=yes ExecStart=/bin/true [Install] WantedBy=multi-user.target So back on Xenial it is privateTmp + too early that breaks it. Xenial vs Bionic critical-chain according to "systemd-analyze critical- chain open.vm-tools.service" Xenial with fix: open-vm-tools.service @3.482s └─local-fs.target @3.460s └─local-fs-pre.target @3.460s └─systemd-remount-fs.service @3.442s +9ms └─system.slice @220ms └─-.slice @204m Xenial without fix: └─run-vmblock\x2dfuse.mount @6.076s +390ms └─sys-fs-fuse-connections.mount @5.510s +375ms └─systemd-modules-load.service @1.996s +75ms └─system.slice @1.984s └─-.slice @1.966s Bionic open-vm-tools.service @3.566s └─systemd-tmpfiles-setup.service @3.421s +100ms └─systemd-journal-flush.service @3.054s +342ms └─systemd-journald.service @825ms +2.219s └─syslog.socket @808ms └─system.slice @621ms └─-.slice @613ms To Summarize, we can: - revert the fix for Bionic (or later) - just make it a sync when convenient down the road, it doesn't hurt for now as it is (almost) the same as the implicit dependency) - add a xenials systemd bug task (probably too complex to fix as -upstream) - until said systemd bug is fixed a backport of open-vm-tools needs this fix ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: open-vm-tools (Ubuntu Xenial) Status: New => Triaged ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1750780 Title: Race with local file systems can make open-vm-tools fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736955] Re: dep8 test systemd-fsckd fails on s390
** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1736955 Title: dep8 test systemd-fsckd fails on s390 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1736955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736955] Re: dep8 test systemd-fsckd fails on s390
** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1736955 Title: dep8 test systemd-fsckd fails on s390 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1736955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
There are many potential affected packages I have no insight, but for nbd this should be fixed since 1:3.14-1 by upstream now providing a native systemd service. That means >=Zesty should be fixed in that regard. Not sure on backporting that - one would need to check the potential further context that needs to go back to Xenial, but that might be the proper solution that one might want to try. ** Also affects: nbd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796633 Importance: Unknown Status: Unknown ** Also affects: util-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nfs-utils (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nbd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: avahi (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: rpcbind (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nbd (Ubuntu Xenial) Status: New => Triaged ** Changed in: nbd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)
Thanks Tom, I agree that loosing the hidden-shells seems to be a regression. And to make the state more clear that this in the current state is considered a an issue of accountservice or lightdm lets mark the other packages won't fix for now. Otherwise everybody assumes "the other will do it". This give a better overview and in general it isn't feasible to fix "all-those" and since there can be high-id system-users added manually by users the issue would still persist even when all those other packages would be fixed. ** Changed in: netqmail (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: libvirt (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: ifmail (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: ceph (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713098] Re: Frequent DEP8 test failures related to ftp
s390x and arm skip the test so all green there isn't worth anything. The others fail in ~30% of the cases I'd say: http://autopkgtest.ubuntu.com/packages/gvfs/artful/ppc64el http://autopkgtest.ubuntu.com/packages/gvfs/artful/i386 http://autopkgtest.ubuntu.com/packages/gvfs/artful/amd64 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1713098 Title: Frequent DEP8 test failures related to ftp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1713098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713098] Re: Frequent DEP8 test failures related to ftp
The errors read like networking or concurrency breaking it. I agree to have the bug to debug and improve the case. For now I re-triggered the one hanging test on artful. The release Team can mark dep8 tests as flaky to skip them blocking a migration, but that would prereq an analysis of the case as an argument. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1713098 Title: Frequent DEP8 test failures related to ftp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1713098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1574566] Re: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1707400 *** https://bugs.launchpad.net/bugs/1707400 ** This bug is no longer a duplicate of bug 1594902 Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit ** This bug has been marked a duplicate of bug 1707400 libvirt-bin doesn't regenerate apparmor cache in postinst -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1574566 Title: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts
** Tags added: triage -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1679435 Title: GNOME Software fails to install .deb packages that trigger debconf prompts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload
Hi, I wanted to notify that the merge of systemd version 234 fixed this bug - it is only in proposed so far, but I checked against that. So we can consider artful done (soon), but it would be great to consider SRUs. ** Changed in: systemd (Ubuntu Artful) Status: New => Fix Released ** Changed in: systemd (Ubuntu Artful) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1702823 Title: Systemd fails to serialize tasks correctly on daemon-reload To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1702823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload
I was able to prove that this fixes my issue around libvirt-lxc loosing containers on restart. It could have an almost random number of other effects that are broken by it and we don't know so I'd highly appreciate considering that fix - even for SRU's actually. But OTOH I need more of a systemd Expert to look at it and consider potential side-effects. A test version can be found in [1] and its ppa [2]. I'll also re-file my Debian bug towards systemd to let them consider it as well. But for Ubuntu atm - please review and consider the debdiff I attach hereby. [1]: https://bileto.ubuntu.com/#/ticket/2857 [2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2857/ ** Patch added: "systemd-bug-1702823-fix-deserialization.debdiff" https://bugs.launchpad.net/systemd/+bug/1702823/+attachment/4910732/+files/systemd-bug-1702823-fix-deserialization.debdiff ** Package changed: libvirt (Debian) => systemd (Debian) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1702823 Title: Systemd fails to serialize tasks correctly on daemon-reload To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1702823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1702823] [NEW] Systemd fails to serialize tasks correctly on daemon-reload
Public bug reported: Hi, I was initially tracking down a libvirt bug [1], but happened to realize it is actually a general systemd issue. >From there I got to file, discuss and test [2]. For now I file the bug to be ablte to do my tests correctly, but if it really fixes the issue I'd like to suggest to fix it in the release - so better file upfront and do even my test patches right. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379 [2]: https://github.com/systemd/systemd/issues/6299. ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: ChristianEhrhardt (paelzer) Status: New ** Affects: libvirt (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #867379 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379 ** Also affects: libvirt (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379 Importance: Unknown Status: Unknown ** Bug watch added: github.com/systemd/systemd/issues #6299 https://github.com/systemd/systemd/issues/6299 ** Also affects: systemd via https://github.com/systemd/systemd/issues/6299 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1702823 Title: Systemd fails to serialize tasks correctly on daemon-reload To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1702823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 696435] Re: wait-for-root fails to detect nbd root
Checking the issue that was referred shows it was handled and fixed in 1. Kernel https://github.com/torvalds/linux/commit/37091fdd831f28a6509008542174ed324dd645bc which is 4.6 and thereby fixed in >=Yakkety. 2. Systemd https://github.com/systemd/systemd/pull/2422 that went into systemd 230 which also means part of >=Yakkety. I'm filing bug tasks for systemd and kernel to check and maybe consider for Xenial ** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => New ** Changed in: nbd (Ubuntu) Status: Confirmed => Invalid ** Also affects: nbd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: nbd (Ubuntu Xenial) ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/696435 Title: wait-for-root fails to detect nbd root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings
> Anything else needed on src:systemd side of things? Hi xnox, Well, in a perfect world and with a time machine to help you could look what in zesty's systemd fixed it to work reliably even with the suboptimal service file. But then you have more important tasks all around you and it is fixed where it was broken. Until then I think "opinion" is more appropriate than "incomplete" - yet at whatever state it is ok to just let it hang around for now. If similar issues come up for other services we might reconsider. ** Changed in: systemd (Ubuntu) Status: Incomplete => Opinion ** Changed in: systemd (Ubuntu Xenial) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1644530 Title: keepalived fails to restart cleanly due to the wrong systemd settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1644530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings
Reported the request to pick up the PIDFile statement to Debian. Linking up the debbug here. ** Bug watch added: Debian Bug tracker #857618 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857618 ** Also affects: keepalived (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857618 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1644530 Title: keepalived fails to restart cleanly due to the wrong systemd settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1644530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings
What I think is happening in our case:
Since no ExecStop= was specified, systemd will send SIGTERM [...]
Details: https://www.freedesktop.org/software/systemd/man/systemd.kill.html#
KillMode is "process" in the service file.
That means "If set to process, only the main process itself is killed."
So in this case it relies on that being forwarded to the child processes.
That takes time.
If not waiting for it to be "complete" the following restart will send the next
SIGTERM and this eliminates the (already in cleanup) main proccess before it
can distribute the TERM to its childs/siblings. This is our error state.
In this broken state
Main PID: 10600 (code=exited, status=0/SUCCESS)
Our mode of KillMode=process might have special handling and kill all of them
(since there is no main to kill). That is the cleanup, which gets it back to
work again.
Since the service files in both (X/Z) cases are the same I wonder if
there is a systemd change which fixes this by some sort of waiting for
the signal to be handled (e.g. waiting for the MainPid to go away on its
own).
Systemd versions:
Xenial: 229-4ubuntu16
Zesty: 232-18ubuntu1
** Description changed:
Because "PIDFile=" directive is missing in the systemd unit file,
keepalived sometimes fails to kill all old processes. The old processes
remain with old settings and cause unexpected behaviors. The detail of
this bug is described in this ticket in upstream:
https://github.com/acassen/keepalived/issues/443.
The official systemd unit file is available since version 1.2.24 by this
commit:
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15
This includes "PIDFile" directive correctly:
PIDFile=/var/run/keepalived.pid
We should go the same way.
I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.
Package: keepalived
Version: 1.2.19-1
===
How to reproduce:
I used the two instances of Ubuntu 16.04.2 on DigitalOcean:
Configurations
--
MASTER server's /etc/keepalived/keepalived.conf:
vrrp_script chk_nothing {
script "/bin/true"
interval 2
}
vrrp_instance G1 {
interface eth1
state BACKUP
priority 100
virtual_router_id 123
unicast_src_ip
unicast_peer {
}
track_script {
chk_nothing
}
}
BACKUP server's /etc/keepalived/keepalived.conf:
vrrp_script chk_nothing {
script "/bin/true"
interval 2
}
vrrp_instance G1 {
interface eth1
state MASTER
priority 200
virtual_router_id 123
unicast_src_ip
unicast_peer {
}
track_script {
chk_nothing
}
}
- Procedures
- --
+ Loop based probing for the Error to exist:
+ --
+ After the setup above start keepalived on both servers:
+ $ sudo systemctl start keepalived.service
+ Then run the following loop
+ $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo
systemctl restart keepalived; sudo systemctl status keepalived | egrep
'Main.*exited'; done; done
+
+ Expected: no error, only time reports
+ Error case: Showing Main PID exited, details below
+
+ Step by Step Procedures
+ ---
1) Start keepalived on both servers
$ sudo systemctl start keepalived.service
2) Restart keepalived on either one
$ sudo systemctl restart keepalived.service
3) Check status and PID
$ systemctl status -n0 keepalived.service
Result
--
0) Before restart
Main PID is 3402 and the subprocesses' PIDs are 3403-3406. So far so
good.
root@ubuntu-2gb-sgp1-01:~# systemctl status -n0 keepalived
● keepalived.service - Keepalive Daemon (LVS and VRRP)
Loaded: loaded (/lib/systemd/system/keepalived.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2017-03-04 01:37:12 UTC; 14min ago
Process: 3402 ExecStart=/usr/sbin/keepalived $DAEMON_ARGS (code=exited,
status=0/SUCCESS)
Main PID: 3403 (keepalived)
Tasks: 3
Memory: 1.7M
CPU: 1.900s
CGroup: /system.slice/keepalived.service
├─3403 /usr/sbin/keepalived
├─3405 /usr/sbin/keepalived
└─3406 /usr/sbin/keepalived
1) First restart
Now Main PID is 3403, which was one of the previous subprocesses and is
actually exited. Something is wrong. Yet, the previous processes are all
exited; we are not likely to see no weird behaviors here.
root@ubuntu-2gb-sgp1-01:~# systemctl restart keepalived
root@ubuntu-2gb-sgp1-01:~# systemctl status -n0 keepalived
● keepalived.service - Keepalive Daemon (LVS and VRRP)
Loaded: loaded (/lib/systemd/system/keepalived.service; enabled; vendor
preset: enabled)
Active:
[Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)
Found more in fidonet and qmail, adding tasks. But the more that are affected the more I think then general solution in lightdm would be the right thing to do. ** Also affects: netqmail (Ubuntu) Importance: Undecided Status: New ** Also affects: fidogate (Ubuntu) Importance: Undecided Status: New ** No longer affects: fidogate (Ubuntu) ** Also affects: ifmail (Ubuntu) Importance: Undecided Status: New ** Changed in: ifmail (Ubuntu) Status: New => Confirmed ** Changed in: netqmail (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1667113] Re: Libvirt Qemu appears in the list of users in Ligthdm and user switecher
The user Objects have an attribute for system accounts: property Boolean SystemAccount Whether or not the account is a system account, such as adm. System accounts aren't returned by ListCachedUsers and should generally be ignored. It also has a shell property, but that (by default) seems to have no impact on listCachedUsers property String Shell, method SetShell(String path) The user's login shell. ListCachedUsers then is what is used by lightdm to fetch the list: method ListCachedUsers() returns: users: an array of paths for the user objects Returns a subset of the users who exist, typically those who have logged in recently, for populating chooser lists such as those used by GDM's greeter. Currently the accountsservice process scans /etc/passwd for users, filters out those with UID values which are below a threshold point to screen out system users, and sorts the rest by the number of times the users in question appear in /var/log/wtmp. Above a certain length, it's expected that the caller will disregard the list and present only an entry field. The entry field always needs to be available because we know that some results may be missing from this list. Best API def I found so far is from sssd: https://fedorahosted.org/sssd/wiki/DesignDocs/AccountsService Call is from lightdm at load_users in common/user-list.c This can be reproduced more easily by a direct dbus call: $ dbus-send --print-reply=literal --system --dest=org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu) Status: New => Confirmed ** Changed in: base-passwd (Ubuntu) Status: New => Invalid ** Summary changed: - Libvirt Qemu appears in the list of users in Ligthdm and user switecher + System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1594902] Re: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit
** Project changed: systemd => systemd (Ubuntu) ** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1594902 Title: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1594902/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file
Adding Linux as it seems (at least) to be related to the kernel and might need a bisect followed by a SRU for Xenial. Also once 4.6 is ready this should be verified and closed on Yakkety. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1602737 Title: PCI RoCE Interface could not be renamed from default name with link file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1602737/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1444958] Re: STC830:Brazos:br311p06: file(s) are deleted from the /tmp after each reboot on Ubuntu OS
The referenced Debian bug was about sanitizing the migration like postinst steps. These fixes of the systemdare in Wily and Xenial due to merges of the package. Eventually we have to conclude that we have a new intended behavior and not really a bug. If you actually want the old behavior the bug holds workarounds provided by Martin Pitt - thanks a lot. For those who want more detail please take a look at http://manpages.ubuntu.com/manpages/utopic/man5/tmpfiles.d.5.html I'm not sure if the correct bug state would be Invalid or Opinion now - IMHO I'm setting invalid, but feel free to change. ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1444958 Title: STC830:Brazos:br311p06: file(s) are deleted from the /tmp after each reboot on Ubuntu OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1444958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
