[Touch-packages] [Bug 1430479] Re: "telinit u" under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
** Changed in: upstart (Debian) Status: New => Fix Released -- 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/1430479 Title: "telinit u" under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Status in upstart package in Debian: Fix Released Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with "(EE) Cannot establish any listening sockets" etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: "telinit u" under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
** Bug watch added: Debian Bug tracker #789524 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789524 ** Also affects: upstart (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789524 Importance: Unknown Status: Unknown -- 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/1430479 Title: "telinit u" under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Status in upstart package in Debian: Unknown Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with "(EE) Cannot establish any listening sockets" etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: "telinit u" under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
** Changed in: upstart (Debian) Status: Unknown => New -- 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/1430479 Title: "telinit u" under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Status in upstart package in Debian: New Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with "(EE) Cannot establish any listening sockets" etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: telinit u under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
I've verified that the upgrade works now. -- 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/1430479 Title: telinit u under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with (EE) Cannot establish any listening sockets etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: telinit u under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
That's because perform_reexec() just reexec's argv[0], which used to be /sbin/init. But that just changed pointing from upstart to pointing to systemd. So upstart's function isn't actually conceptually wrong, but perhaps we could run /sbin/upstart instead of argv[0] (which is likely /sbin/init)? -- 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/1430479 Title: telinit u under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: In Progress Status in upstart package in Ubuntu: New Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with (EE) Cannot establish any listening sockets etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: telinit u under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
So we either change upstart's perform_reexec() to run /sbin/upstart, or we change systemd's telinit to not forward an u request to upstart, and simply ignore the reload. The latter would break the intention of glibc's restart though (but it's probably not a big deal). -- 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/1430479 Title: telinit u under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: In Progress Status in upstart package in Ubuntu: New Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with (EE) Cannot establish any listening sockets etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: telinit u under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
Adam points out that we would need to fix that in trusty's and utopic's upstart as well, so let's just work around that in systemd's telinit. ** Changed in: upstart (Ubuntu) Importance: Critical = Medium -- 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/1430479 Title: telinit u under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: In Progress Status in upstart package in Ubuntu: New Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with (EE) Cannot establish any listening sockets etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: telinit u under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
Fixing upstart to do the right thing is probably good anyway, but since one can't go back in time and fix it, that won't solve the upgrade issue. The only way to solve the upgrade issue is to make systemd not forward the request, I imagine. It could potentially make the first umount on reboot after the upgrade unclean, but I can't think of a better way around this. -- 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/1430479 Title: telinit u under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: In Progress Status in upstart package in Ubuntu: New Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with (EE) Cannot establish any listening sockets etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: telinit u under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
http://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?h=ubuntuid=0a5d8124369 ** Changed in: systemd (Ubuntu) Status: In Progress = Fix Committed ** Changed in: upstart (Ubuntu) Status: New = Triaged -- 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/1430479 Title: telinit u under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: Fix Committed Status in upstart package in Ubuntu: Triaged Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with (EE) Cannot establish any listening sockets etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: telinit u under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
This bug was fixed in the package systemd - 219-4ubuntu5 --- systemd (219-4ubuntu5) vivid; urgency=medium * Merge from experimental branch: - /lib/lsb/init-functions.d/40-systemd: Don't ignore systemd unit dependencies in degraded mode. (LP: #1429734) - rules-ubuntu/71-power-switch-proliant.rules: Add support for HP ProLiant m400 Server Cartridge soft powerdown on Linux 3.16. (LP: #1428811) * systemctl: Don't forward telinit u to upstart. This works around upstart's Restart() always reexec'ing /sbin/init on Restart(), even if that changes to point to systemd during the upgrade. This avoids running systemd during a dist-upgrade. (LP: #1430479) -- Martin Pitt martin.p...@ubuntu.com Wed, 11 Mar 2015 11:01:36 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed = Fix Released -- 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/1430479 Title: telinit u under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with (EE) Cannot establish any listening sockets etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430479] Re: telinit u under upstart (upstart's Restart command) with systemd-sysv installed runs systemd
As we have a workaround in systemd now, I untag this to clean up the bug list. ** Tags removed: systemd-boot -- 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/1430479 Title: telinit u under upstart (upstart's Restart command) with systemd- sysv installed runs systemd Status in systemd package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Bug description: I've today had two machines kill my X session during dist-upgrade, and it happened during libc6 postinst. Dmesg shows that systemd got somehow started during the earlier phase of the upgrade. X logs show a failure with (EE) Cannot establish any listening sockets etc.. Adam can fill in the more detailed analysis of what's happening there.. but I think it should be fairly easy to reproduce by installing vivid from an earlier image and dist-upgrading to current, if needed. Reproducer: - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic) - Switch apt sources to vivid - sudo apt install systemd-sysv - sudo telinit u # systemd command, forwards to upstart's /lib/sysvinit/telinit - Or directly: sudo /lib/sysvinit/telinit u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
