Приветы
___ 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: bug 807122 is forwarded to https://github.com/systemd/systemd/issues/2183
Processing commands for cont...@bugs.debian.org: > forwarded 807122 https://github.com/systemd/systemd/issues/2183 Bug #807122 [systemd] systemd-resolved: static dns entries Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/2183'. > thanks Stopping processing here. Please contact me if you need assistance. -- 807122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807122 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
Здравствуйте.
___ 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#808151: systemd: failed to start remount root and kernel file system
Am 17.12.2015 um 13:46 schrieb Frank B. Brokken: > Dear Michael Biebl, you wrote: > >> What happens afterwards? Are you dropped into the rescue shell? > > Afterwards (i.e., after the initial failure message) the system tries to > continue booting, but shows lots of failure messages, eventually grinding to a > halt. No reboot (e.g. ctrl-alt-del) is possible and there's no rescue shell. > >> If not, try to enable the debug shell by adding "systemd.debug-shell" to >> the kernel command line. This will give you a root shell on tty9. > > Unfortunately, it doesn't, since the system halts (I first removed the > automatic reboot on failure). What exactly do you mean with halt? The systems completely locks up so you can't use the keyboard and switch to tty9? That would sound like a kernel problem. > However, during the process I observed that setting systemd.debug-shell and > removing the default 'quiet' specification from grub's /etc/default/grub (so, > now it specifies: > > GRUB_CMDLINE_LINUX_DEFAULT="systemd.debug-shell" > > greatly reduces the chances of a failing boot. Not completely, but > greatly. Still, when rebooting fails there's just the plain halt, w/o a debug > shell. Since removing the quiet also produces a lot more output on the screen, > might my problem not simply be some timing problem? Can you make a screenshot or a video from the boot process with "quiet" removed from the kernel command line. -- 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
Processed: bug 808222 is forwarded to https://github.com/systemd/systemd/issues/2186
Processing commands for cont...@bugs.debian.org: > forwarded 808222 https://github.com/systemd/systemd/issues/2186 Bug #808222 [systemd-container] /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/2186'. > thanks Stopping processing here. Please contact me if you need assistance. -- 808222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808222 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
Bug#808151: systemd: failed to start remount root and kernel file system
Dear Michael Biebl, you wrote: > What happens afterwards? Are you dropped into the rescue shell? Afterwards (i.e., after the initial failure message) the system tries to continue booting, but shows lots of failure messages, eventually grinding to a halt. No reboot (e.g. ctrl-alt-del) is possible and there's no rescue shell. > If not, try to enable the debug shell by adding "systemd.debug-shell" to > the kernel command line. This will give you a root shell on tty9. Unfortunately, it doesn't, since the system halts (I first removed the automatic reboot on failure). However, during the process I observed that setting systemd.debug-shell and removing the default 'quiet' specification from grub's /etc/default/grub (so, now it specifies: GRUB_CMDLINE_LINUX_DEFAULT="systemd.debug-shell" greatly reduces the chances of a failing boot. Not completely, but greatly. Still, when rebooting fails there's just the plain halt, w/o a debug shell. Since removing the quiet also produces a lot more output on the screen, might my problem not simply be some timing problem? -- Frank B. Brokken Center for Information Technology, University of Groningen (+31) 50 363 9281 Public PGP key: http://pgp.surfnet.nl Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA signature.asc Description: PGP 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#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists
Package: systemd-container Version: 227-2 Severity: important File: /usr/bin/systemd-nspawn systemd-nspawn --link-journal=host should accept an existing directory. root@iron:~# systemctl start systemd-nspawn@foo [ everything works ] root@iron:~# systemctl stop systemd-nspawn@foo root@iron:~# systemctl status -l systemd-nspawn@foo ● systemd-nspawn@foo.service - Container foo Loaded: loaded (/lib/systemd/system/systemd-nspawn@.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/systemd-nspawn@.service.d └─smurf.conf Active: failed (Result: exit-code) since Do 2015-12-17 13:00:33 CET; 7s ago Docs: man:systemd-nspawn(1) Process: 12750 ExecStart=/usr/bin/systemd-nspawn --quiet --network-bridge=br0 --network-veth-extra=vb-%i:host443 --keep-unit --boot --link-journal=host --directory=/d/vm/%i --bind=/var/cache (code=exited, status=1/FAILURE) Main PID: 12750 (code=exited, status=1/FAILURE) Status: "Terminating..." Dez 17 13:00:33 iron systemd[1]: Starting Container foo... Dez 17 13:00:33 iron systemd-nspawn[12750]: mount(/d/vm/foo/sys/fs/selinux) failed, ignoring: No such file or directory Dez 17 13:00:33 iron systemd-nspawn[12750]: mount(/d/vm/foo/sys/fs/selinux) failed, ignoring: Invalid argument Dez 17 13:00:33 iron systemd-nspawn[12750]: /etc/localtime is not a symlink, not updating container timezone. Dez 17 13:00:33 iron systemd-nspawn[12750]: Failed to create /var/log/journal/15bfd317d6044649beb2e509acfd0cac: File exists Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Main process exited, code=exited, status=1/FAILURE Dez 17 13:00:33 iron systemd[1]: Failed to start Container foo. Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Unit entered failed state. Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Failed with result 'exit-code'. root@iron:~# ls -l /var/log/journal/15bfd317d6044649beb2e509acfd0cac total 8192 -rw-r-+ 1 root netdev 8388608 Jan 18 2015 system.journal root@iron:~# rm -r /var/log/journal/15bfd317d6044649beb2e509acfd0cac root@iron:~# systemctl start systemd-nspawn@foo [ everything works ] root@iron:~# -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-container depends on: ii libblkid12.25.2-6 ii libbz2-1.0 1.0.6-7+b3 ii libc62.19-18+deb8u1 ii libcap2 1:2.24-8 ii libcurl3-gnutls 7.45.0-1+b1 ii libgcrypt20 1.6.3-2 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libseccomp2 2.1.1-1 ii libselinux1 2.3-2 ii systemd 227-2 ii zlib1g 1:1.2.8.dfsg-2+b1 systemd-container recommends no packages. systemd-container suggests no packages. -- no debconf information ___ 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#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists
Control: severity -1 normal Control: tags -1 upstream Hi Am 17.12.2015 um 13:06 schrieb Matthias Urlichs: > Package: systemd-container > Version: 227-2 > Severity: important > File: /usr/bin/systemd-nspawn > > systemd-nspawn --link-journal=host should accept an existing directory. > Please test with the latest version 228-2 and if the problem still persists, file the bug upstream at https://github.com/systemd/systemd/issues -- 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
Processed: Re: Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists
Processing control commands: > severity -1 normal Bug #808222 [systemd-container] /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists Severity set to 'normal' from 'important' > tags -1 upstream Bug #808222 [systemd-container] /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists Added tag(s) upstream. -- 808222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808222 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: propased patch should be enough
Processing commands for cont...@bugs.debian.org: > tags 804882 - moreinfo Bug #804882 [systemd] fix lsb hook reload for masked services Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 804882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804882 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
Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists
On 17.12.2015 14:59, Michael Biebl wrote: > Control: severity -1 normal > Control: tags -1 upstream > > Hi > > Am 17.12.2015 um 13:06 schrieb Matthias Urlichs: >> Package: systemd-container >> Version: 227-2 >> Severity: important >> File: /usr/bin/systemd-nspawn >> >> systemd-nspawn --link-journal=host should accept an existing directory. >> > Please test with the latest version 228-2 Actually this is from 228-2, I simply forgot to update the header. > and if the problem still > persists, file the bug upstream at > https://github.com/systemd/systemd/issues > > OK, will do. -- -- Matthias Urlichs ___ 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#808151: systemd: failed to start remount root and kernel file system
Dear Michael Biebl, you wrote: > Am 17.12.2015 um 13:46 schrieb Frank B. Brokken: > > halt. No reboot (e.g. ctrl-alt-del) is possible and there's no rescue > > shell> > What exactly do you mean with halt? The systems completely locks up so > you can't use the keyboard and switch to tty9? No, that's not what happens. I mean that doing a reboot using ctrl-alt-del isn't possible. Switching VTs is no problem, but except for VT1 nothing was being shown. But maybe I overlooked things when I sent you the previous reply: see below. > That would sound like a kernel problem. > > might my problem not simply be some timing problem? > > Can you make a screenshot or a video from the boot process with "quiet" > removed from the kernel command line. I did. Not only that, I also tried to reboot again and this time I was able to run the commands you asked before from tty9: systemctl status systemd-analyze dump journalctl -alb This time the debug shell prompt was available at tty9, although booting failed. And in line with my previous findings, systemd-analyze and journalctl weren't available, as they live in /usr/bin, and /usr hadn't been mounted. But after mounting /usr from tty9 and then using the mount command systemd-analyze and journalctl were available, so I also have the output from those commands for you. The output, and the mp4 movie I made during the booting process are a bit too large for the e-mail, but they are available for download/inspection at https://www.icce.rug.nl/systemd/ Cheers, -- Frank B. Brokken Center for Information Technology, University of Groningen (+31) 50 363 9281 Public PGP key: http://pgp.surfnet.nl Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA signature.asc Description: PGP 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#808222: Upstream bug
https://github.com/systemd/systemd/issues/2186 -- -- Matthias Urlichs ___ 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#808151: systemd: failed to start remount root and kernel file system
Am 17.12.2015 um 16:24 schrieb Frank B. Brokken: > This time the debug shell prompt was available at tty9, although booting > failed. And in line with my previous findings, systemd-analyze and journalctl > weren't available, as they live in /usr/bin, and /usr hadn't been mounted. But Well, /usr is mounted by the initramfs these days. So it should already be available when systemd is started. If that fails, this is a bug which needs to be addressed by initramfs-tools (or one of the hook scripts). It wasn't clear so far that /usr hasn't been mounted at all. Is /usr on LVM, RAID, etc? -- 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
Processed: unarchiving 761909
Processing commands for cont...@bugs.debian.org:
> unarchive 761909
Bug #761909 {Done: Martin Pitt } [systemd] systemd does not
unmount nfs shares before bringing down the network interface
Unarchived Bug 761909
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
761909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761909
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
Bug#808151: systemd: failed to start remount root and kernel file system
Am 17.12.2015 um 22:38 schrieb Michael Biebl: > Am 17.12.2015 um 16:24 schrieb Frank B. Brokken: >> This time the debug shell prompt was available at tty9, although booting >> failed. And in line with my previous findings, systemd-analyze and journalctl >> weren't available, as they live in /usr/bin, and /usr hadn't been mounted. >> But > > Well, /usr is mounted by the initramfs these days. So it should already > be available when systemd is started. If that fails, this is a bug which > needs to be addressed by initramfs-tools (or one of the hook scripts). > It wasn't clear so far that /usr hasn't been mounted at all. > > Is /usr on LVM, RAID, etc? I'm a bit confused by those logs. They show that sda5 have been mounted. Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounting ext3 file system using the ext4 subsystem Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) I figure /dev/sda5 is your /usr partition? Just to be sure, please attach ls -la /dev/disk/by-uuid/ If so, I'm honestly puzzled why later on the binaries from /usr/bin are not found. Could you do another try and add "debug" to the kernel command line. Then attach /run/initramfs/initramfs.debug and journalctl -alb (and avoid mounting /usr manually on tty9) Do you have any custom udev rules in /etc/udev/rules.d? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
