Re: #766216: lxc: can't access console or stop a jessie container running systemd as PID 1
On Sun, 7 Dec 2014, Adam D. Barratt wrote: Is this still relevant after the upload of lxc 1.0.6-5? I can confirm that *this specific* problem, namely #766216 - not beeing able to access the console or to stop the VM has indeed been fixed in 1:1.0.6-5 on a host running up to date jessie with a freshly created jessie VM. There are still a few ugly things happening when starting the container: # lxc-start -n testfoo [...] Failed to open /dev/autofs: No such file or directory Failed to initialize automounter: No such file or directory [FAILED] Failed to set up automount Arbitrary Executable File Formats File System Automount Point. See 'systemctl status proc-sys-fs-binfmt_misc.automount' for details. [...] [FAILED] Failed to start Login Service. but the container startup proceeds to the login prompt and loging in works so the above is - if ever - material for a different bug report. *t ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#770090: systemd: systemctl poweroff doesn't poweroff
Am 18.11.2014 um 21:22 schrieb Robert Latest: Package: systemd Version: 215-5+b1 Severity: important Dear Maintainer, Since the latest aptitude update/upgrade, I can't shut down my computer any more. Whether I do /sbin/poweroff, or /bin/systemctl poweroff, or use the off button in lightm, the system immediately reboots. I have to press the hardware power button for several seconds to force a cold shutdown. This might be a kexec issue, since there were similar bug report where having kexec-tools installed caused a poweroff/shutdown to result in reboot. If you uninstall and purge the kexec-tools package, is the problem gone? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#774214: installation-reports: System startup fails with multiple / multi-device BTRFS mounts
Hi, and thanks for your report. Robert Tomanek deb...@mail.robert.tomanek.org (2014-12-30): Package: installation-reports Severity: important I've installed 2014-12-26 build of debian testing with btrfs as root fs -- so far so good, this worked fine. So that's not really something that should be tracked through the installation-reports pseudopackage. Let's see what we can do about it. Then I've created another btrfs filesystem based on 5x HDD and a number of subvolumes on this filesystem and then added all of them to fstab so that they would be mounted on boot. This is where it stopped working -- some of them could not be mounted automatically, but if I tried mounting them manually they worked fine. The open_ctree message in the logs is bogus I think, filesystem itself is OK. I've fallen back to noauto in fstab. There is a matching entry on arch wiki that describes exactly my issue: goo.gl/JqShSo So the real link is: https://wiki.archlinux.org/index.php/Btrfs#BTRFS:_open_ctree_failed and the relevant contents: | BTRFS: open_ctree failed | | As of November 2014 there seems to be a bug in systemd or mkinitcpio causing the following error on systems with multi-device Btrfs filesystem using the btrfs hook in mkinitcpio.conf: | | BTRFS: open_ctree failed | mount: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error | | In some cases useful info is found in syslog - try dmesg|tail or so. | | You are now being dropped into an emergency shell. | | A workaround is to remove btrfs from the HOOKS array in /etc/mkinitcpio.conf and instead adding btrfs to the MODULES array. Then regenerate the initramfs with mkinitcpio -p linux (adjust the preset if needed) and reboot. | | See the original forums thread and FS#42884 for further information and discussion. Forums thread: https://bbs.archlinux.org/viewtopic.php?id=189845 Bug report: https://bugs.archlinux.org/task/42884 The auto vs. noauto thing makes me want to query systemd people's opinion, so I've added them to Cc. They might need further input from you to tell us whether that's a bug or some kind of misconfiguration. Mraw, KiBi. signature.asc Description: Digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#774214: installation-reports: System startup fails with multiple / multi-device BTRFS mounts
On 2014-12-30 14:51, Cyril Brulebois wrote: Robert Tomanek deb...@mail.robert.tomanek.org (2014-12-30): Package: installation-reports Severity: important I've installed 2014-12-26 build of debian testing with btrfs as root fs -- so far so good, this worked fine. So that's not really something that should be tracked through the installation-reports pseudopackage. Let's see what we can do about it. Apologies for misfiling. The auto vs. noauto thing makes me want to query systemd people's opinion, so I've added them to Cc. They might need further input from you to tell us whether that's a bug or some kind of misconfiguration. I am happy to provide more input, just ask. Regards, r. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#765542: marked as done (systemd: man systemd refers to obsolete command 'systemctl dump')
Your message dated Tue, 30 Dec 2014 16:07:06 +0100 with message-id 20141230150705.gi12...@piware.de and subject line Re: Bug#765542: systemd: man systemd refers to obsolete command 'systemctl dump' has caused the Debian Bug report #765542, regarding systemd: man systemd refers to obsolete command 'systemctl dump' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 215-5+b1 Severity: minor Tags: patch The man page refers to the 'dump' function of systemctl in the SIGUSR2 explanation. The dump function has been moved to 'systemd-analyze dump'. Patch attached to change the wording. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.4 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.20.1-5.11 ii libc6 2.19-11 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-1 ii libgcrypt20 1.6.2-3 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-5+b1 ii sysv-rc 2.88dsf-53.4 ii udev215-5+b1 ii util-linux 2.20.1-5.11 Versions of packages systemd recommends: ii dbus1.8.8-1+b1 ii libpam-systemd 215-5+b1 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/system.conf changed: [Manager] -- no debconf information --- systemd.1.orig 2014-10-15 22:32:40.163864937 -0400 +++ systemd.1.new 2014-10-15 22:33:37.615667214 -0400 @@ -490,7 +490,7 @@ \fBSIGUSR2\fR .RS 4 When this signal is received the systemd manager will log its complete state in human readable form\. The data logged is the same as printed by -\fBsystemctl dump\fR\. +\fBsystemd-analyze dump\fR\. .RE .PP \fBSIGHUP\fR ---End Message--- ---BeginMessage--- Version: 218-1 This got applied in version 218, so fixed in experimental. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)---End Message--- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: reassign 754218 to ifupdown, closing 754218, forcibly merging 771943 754218
Processing commands for cont...@bugs.debian.org:
reassign 754218 ifupdown
Bug #754218 [systemd] boot hangs forever on LSB job raise network interfaces
Bug reassigned from package 'systemd' to 'ifupdown'.
No longer marked as found in versions systemd/215-7 and systemd/204-14.
Ignoring request to alter fixed versions of bug #754218 to the same values
previously set
close 754218
Bug #754218 [ifupdown] boot hangs forever on LSB job raise network interfaces
Marked Bug as done
forcemerge 771943 754218
Bug #771943 {Done: Andrew Shadura andre...@debian.org} [ifupdown] ifupdown:
boot hangs, interface won't raise
Bug #773832 {Done: Andrew Shadura andre...@debian.org} [ifupdown] systemd:
LSB job raise network interfaces hangs with allow-hotplug and no cable
Bug #754218 {Done: Martin Pitt martin.p...@ubuntu.com} [ifupdown] boot hangs
forever on LSB job raise network interfaces
Severity set to 'serious' from 'important'
Marked as fixed in versions ifupdown/0.7.51.
Marked as found in versions ifupdown/0.7.50.
Bug #773832 {Done: Andrew Shadura andre...@debian.org} [ifupdown] systemd:
LSB job raise network interfaces hangs with allow-hotplug and no cable
Merged 754218 771943 773832
thanks
Stopping processing here.
Please contact me if you need assistance.
--
754218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754218
771943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771943
773832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: tagging 773302
Processing commands for cont...@bugs.debian.org: tags 773302 + fixed-upstream Bug #773302 [systemd] systemd: Minor spelling mistake in manpage systemd.unit Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 773302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: tagging 773538
Processing commands for cont...@bugs.debian.org: tags 773538 + pending Bug #773538 [systemd] systemd: journal is quite big compared to rsyslog output Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 773538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: release-notes: Bug#770776: LXC breakage and workarounds when upgrading VMs to jessie
On Sun, 7 Dec 2014, Adam D. Barratt wrote: Is this still relevant after the upload of lxc 1.0.6-5? Yes, it still is. There are still manual steps needed during upgrade. Attached you'll find my second try at a patch to the release notes. If my suggested addition is acceptable and not too far off the mark, then I suggest to apply it *now*. Changes and improvements can be incorporated into the patched release-notes. The reason is, that it took me one month to come back to this issue and I don't know when I'll have the next opportunity to work on this. And I'd rather have the problem documented in the interest of the users. That said, please do criticise, if there's something to improve. So please check, if required criticise and please apply the patch. Thanks you all for contributing and considering and have a wonderful 2015! *t PS: Many thanks to Niels and Holger for their kind and supportive words! This patch is dedicated to you guys!! PPS: Adam and Niels and Daniel, could you please have a look at #774204. If you don't object Daniel, I'd propose to NMU that and ask you release team to have it included in jessie. Please follow up in #774204!diff --git en/upgrading.dbk en/upgrading.dbk index 13b1a30..f7dc09c 100644 --- en/upgrading.dbk +++ en/upgrading.dbk @@ -1136,6 +1136,79 @@ entries. You should use commandvisudo/command for this: /screen /section +section id=issues-lxc +titleLXC/title + +para +The upgrade from wheezy to jessie will migrate your system to +the systemd init system. +/para +para +When upgrading a LXC container, respectively a LXC virtual +machine, this will have different consequences depending on +whether the emphasishost system/emphasis has allready +been upgraded to jessie or not. +/para + +section id=issues-lxc-wheezy-host +titleUpgrading LXC guests running on wheezy hosts/title + +para +If you are upgrading a LXC guest container that is running on a +emphasiswheezy host/emphasis system, then you will need to +prevent the guest from being automatically migrated to systemd. +/para +para +If you don't prevent the system from migrating to systemd, then +you will risk, that your guest system will not be able to boot. +/para +para +This is due to functionality missing in wheezy hosts, that are +required to boot a jessie system with systemd. +/para +para +You prevent the migration via pinning, as described in chapter +xref linked=#systemd-upgrade-default-init-system/. +/para +para +You should be able to switch over to systemd inside the LXC guest +once you have upgraded the emphasishost/emphasis system to jessie. See the next +paragraph for things that need to be adapted on jessie hosts. +/para +/section + +section id=issues-lxc-jessie-host +titleUpgrading LXC guests running on jessie hosts/title + +para +In order to be able to boot LXC guests with systemd, you need +to adapt your LXC container configuration. +/para +para +The container configuration can usually be found in +/para +screen +/var/lib/lxc/replaceableCONTAINER_NAME/replaceable/config +/screen +para +You need to add the following two setting to the configuration: +/para +screen +lxc.autodev = 1 +lxc.kmsg = 0 +/screen +/section + +section id=issues-lxc-further-docu +titleFurther information/title +para +You can find further information on LXC in Debian +ulink url=url-wiki;LXCin the Debian wiki/ulink. +/para +/section + +/section + /section !-- End of 'trouble' section -- /section ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Processed: tagging 773538
Hi Martin, Am 30.12.2014 um 16:39 schrieb Debian Bug Tracking System: Processing commands for cont...@bugs.debian.org: tags 773538 + pending Bug #773538 [systemd] systemd: journal is quite big compared to rsyslog output Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. I see, that you committed a change which limits the journal to 7 days via MaxRetentionSec=7day. First, it has to be noted, that the persistent journal is not enabled by default. Second, I'm not convinced that the current defaults, which are size-based, are buggy and actually need a fix. By limiting the journal to 7 days, we imho unnecessarily make it less useful. I don't see a good reason to not utilize available free disk space. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#732209: (no subject)
Content-Type: multipart/mixed; boundary1764408977== MIME-Version: 1.0 From: Miklos Quartus in...@miklos.info To: Debian Bug Tracking System 732...@bugs.debian.org Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied Message-ID: 20141230213601.24606.52599.reportbug@localhost X-Mailer: reportbug 6.6.1 Date: Tue, 30 Dec 2014 22:36:01 +0100 This is a multi-part MIME message sent by reportbug. --===1764408977== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: libpam-systemd Version: 215-8 Followup-For: Bug #732209 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear GNOME Maintainer, Here's some progress on the bug I am still experiencing in Jessie. I found that this bug can only be reproduced in a GNOME session if the root terminal window is in focus. So to the steps to reproduce the bug - if you have not managed to so far - - slightly changes as below. 1. Get a root terminal window running and make sure it's in focus (in a GNOME session hit the Super key, type 'root ..' in the search bar and hit Enter to the run the app. 2. Run the 'Files' file manager app (not the PCManFM or other) or the 'dconf Editor' app (hit the Super key, type the app name) and once the window is active, do some one simple action (i.e. click on a menu item). 3. Close the application window. 4. Watch the file permission changes - /run/user/1000/dconf/user which effectively locks up your GNOME session. At the moment I don't have any patch or further information as to what might be the root cause leading up to this issue. I am using the latest up-to-date Jessie from official Debian repositories. It is also worth mentioning that I am using the GNOME minimalist installation, I have the 'core-only' as described on https://wiki.debian.org/Gnome . (i.e. I don't have the gnome-desktop-environment package installed, I have the extra stuff :-/). This way I am perfectly happy user of Debian and GNOME. gnome-session: 3.14.0-2 gnome-shell: 3.14.2-3 gnome-core: 1:3.14+3 gnome-desktop-environment: not installed gnome-desktop: not installed Inform me of any progress. Kind regards, - -- Miklos - -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-systemd depends on: ii dbus 1.8.12-3 ii libc6 2.19-13 ii libcap21:2.24-6 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii multiarch-support 2.19-13 ii systemd215-8 ii systemd-sysv 215-8 libpam-systemd recommends no packages. libpam-systemd suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUoxqyAAoJECII8s4/zqDTrKIIALGo5P7P5xsgGweHcxBQr4Zu e6HOiR2Sc91xudDP+Tty/iXAciG01fRi1vrcc6rlAgTa44/+RC5UJTY5Ar8IL7xC G5w7ChYd+y9gWlMHzLAi/eiC37UFW5HQzp1bsvTWI8y9p5l/lWyP7/56eiKIzNEj +6kLK99EJ92qXscC45SFggiT8871d7y9wW52HbFZHoMzsJfPAel57fMDiupvxZut ndO8mSkUDCD8xn6fpks2Vu2PYhP7NO/w6ip2XYHz/axyj51Wz4y2lQnAFgAS6Twk ubzDQeH0ub6iu7ILkoDImuLlCRAYOR09H7ufCOWDhHDJcybpk3fs+qKxVMf6lyA= =4tzM -END PGP SIGNATURE- --===1764408977== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=gnome-shell-errormsg.txt Dec 30 22:13:12 localhost gnome-session[21484]: (gnome-settings-daemon:21555): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. --===1764408977==-- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
