Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
reassign 677712 cryptsetup found 677712 2:1.4.3-2 thanks This is not a bug in upstart, it's a bug in cryptsetup which ships an upstart job with an impossible-to-satisfy start condition (because udev has no upstart job in unstable yet). There is also a false correspondence between the cryptdisks-early upstart job and the init script of the same name; if anything actually has a boot dependency on the init script, the cryptdisks-early job will incorrectly satisfy it because it's called once for each device and startpar will receive an event for each. The lack of udev support for upstart *may* be resolved soon (bug #686378). In the meantime, this is a cryptsetup bug, which should probably be fixed by adding a versioned dependency on udev. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
Hi. Today I tried setup without prompting password from keyboard, and it also fails to start with startpar. With legacy bootordering all works fine. signature.asc Description: This is a digitally signed message part
Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
On Sun, Jul 22, 2012 at 04:35:57PM +0400, Alexander V. Kudrevatykh wrote: Today I tried setup without prompting password from keyboard, and it also fails to start with startpar. With legacy bootordering all works fine. So it could be a dependency problem. Without having a cryptdisks- using system, I can't help debug this really--it needs someone familiar with cryptdisks to figure out what's going wrong and if it's a bug in the LSB header, to fix it there. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
I tried to debug something and found, that cryptdisks are not cause of problem, cause is upstart. After installing sysvinit instead of upstart all works fine. I don't remember why I decided that problem in cryptdisks, may be there is no relation at all. So you are free to close this bug. Thanks. В Вск, 22/07/2012 в 14:02 +0100, Roger Leigh пишет: On Sun, Jul 22, 2012 at 04:35:57PM +0400, Alexander V. Kudrevatykh wrote: Today I tried setup without prompting password from keyboard, and it also fails to start with startpar. With legacy bootordering all works fine. So it could be a dependency problem. Without having a cryptdisks- using system, I can't help debug this really--it needs someone familiar with cryptdisks to figure out what's going wrong and if it's a bug in the LSB header, to fix it there. Thanks, Roger signature.asc Description: This is a digitally signed message part
Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
reassign 677712 upstart thanks On Sun, Jul 22, 2012 at 06:09:24PM +0400, Alexander V. Kudrevatykh wrote: I tried to debug something and found, that cryptdisks are not cause of problem, cause is upstart. After installing sysvinit instead of upstart all works fine. Reassigning to upstart, since this is still a bug. -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
Package: sysvinit-utils Version: 2.88dsf-27 Severity: important after upgrading to 2.88dsf-27 boot stops on cleaning temprorary files... /tmp and not ask password for cryptdisks disabling cryptdisks or switch to legacy boot order fixes problem -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sysvinit-utils depends on: ii libc62.13-33 ii libselinux1 2.1.9-5 sysvinit-utils recommends no packages. Versions of packages sysvinit-utils suggests: pn sash none -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
On Sat, Jun 16, 2012 at 03:00:55PM +0400, Alexander V. Kudrevatykh wrote: Package: sysvinit-utils Version: 2.88dsf-27 Severity: important after upgrading to 2.88dsf-27 boot stops on cleaning temprorary files... /tmp and not ask password for cryptdisks disabling cryptdisks or switch to legacy boot order fixes problem Any idea about what is causing the breakage here? Does cryptdisks have incorrect LSB dependencies? Using legacy boot might correct things, but it's not an acceptable solution given that dependency based booting is the default. Instructions for getting a graph of the dependency tree are here: http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677712: [Pkg-sysvinit-devel] Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
On Sat, 16 Jun 2012, Roger Leigh wrote: On Sat, Jun 16, 2012 at 03:00:55PM +0400, Alexander V. Kudrevatykh wrote: Package: sysvinit-utils Version: 2.88dsf-27 Severity: important after upgrading to 2.88dsf-27 boot stops on cleaning temprorary files... /tmp and not ask password for cryptdisks disabling cryptdisks or switch to legacy boot order fixes problem Any idea about what is causing the breakage here? Does cryptdisks have incorrect LSB dependencies? Does cryptdisks declare its initscript as interactive? My guess is that it needs to have its stdin connected to the controlling terminal to ask for passwords... -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
header for /etc/init.d/cryptdisks-early also attached my depend.boot I guess it started, but can't read stdin/write to stdout, so I can't input password. #! /bin/sh ### BEGIN INIT INFO # Provides: cryptdisks-early # Required-Start:checkroot # Required-Stop: umountroot # Should-Start: udev mdadm-raid # Should-Stop: udev mdadm-raid # X-Start-Before:lvm2 # X-Stop-After: lvm2 # X-Interactive: true # Default-Start: S # Default-Stop: 0 6 # Short-Description: Setup early encrypted block devices. # Description: ### END INIT INFO В Сбт, 16/06/2012 в 19:06 +0100, Roger Leigh пишет: On Sat, Jun 16, 2012 at 03:00:55PM +0400, Alexander V. Kudrevatykh wrote: Package: sysvinit-utils Version: 2.88dsf-27 Severity: important after upgrading to 2.88dsf-27 boot stops on cleaning temprorary files... /tmp and not ask password for cryptdisks disabling cryptdisks or switch to legacy boot order fixes problem Any idea about what is causing the breakage here? Does cryptdisks have incorrect LSB dependencies? Using legacy boot might correct things, but it's not an acceptable solution given that dependency based booting is the default. Instructions for getting a graph of the dependency tree are here: http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot Thanks, Roger TARGETS = mountkernfs.sh udev mountdevsubfs.sh qemu-kvm bootlogd keymap.sh keyboard-setup hwclock.sh hostname.sh hdparm checkroot.sh cryptdisks-early lvm2 mtab.sh kmod checkroot-bootclean.sh cryptdisks checkfs.sh mountall.sh networking urandom ebtables mountall-bootclean.sh procps pppd-dns udev-mtab rpcbind ifscheme nfs-common mountnfs.sh mountnfs-bootclean.sh console-screen.sh console-setup fuse alsa-utils x11-common bootmisc.sh lm-sensors screen-cleanup stop-bootlogd-single INTERACTIVE = udev keymap.sh keyboard-setup checkroot.sh cryptdisks-early cryptdisks checkfs.sh console-screen.sh console-setup udev: mountkernfs.sh mountdevsubfs.sh: mountkernfs.sh udev qemu-kvm: mountkernfs.sh udev bootlogd: mountdevsubfs.sh keymap.sh: mountdevsubfs.sh bootlogd keyboard-setup: mountkernfs.sh keymap.sh udev bootlogd hwclock.sh: mountdevsubfs.sh bootlogd hostname.sh: bootlogd hdparm: mountdevsubfs.sh udev bootlogd checkroot.sh: hwclock.sh mountdevsubfs.sh hostname.sh keymap.sh hdparm bootlogd keyboard-setup cryptdisks-early: checkroot.sh udev lvm2: cryptdisks-early mountdevsubfs.sh udev bootlogd mtab.sh: checkroot.sh kmod: checkroot.sh checkroot-bootclean.sh: checkroot.sh cryptdisks: checkroot.sh cryptdisks-early udev lvm2 checkfs.sh: cryptdisks checkroot.sh mtab.sh lvm2 mountall.sh: checkfs.sh lvm2 networking: mountkernfs.sh mountall.sh urandom: mountall.sh hwclock.sh ebtables: mountall.sh mountall-bootclean.sh: mountall.sh procps: mountkernfs.sh mountall.sh udev bootlogd pppd-dns: mountall.sh udev-mtab: udev mountall.sh rpcbind: networking mountall.sh nfs-common: rpcbind hwclock.sh mountnfs.sh: mountall.sh networking rpcbind nfs-common mountnfs-bootclean.sh: mountall.sh mountnfs.sh console-screen.sh: mountall.sh mountnfs.sh mountnfs-bootclean.sh console-setup: mountall.sh mountnfs.sh mountnfs-bootclean.sh console-screen.sh fuse: mountall.sh mountnfs.sh mountnfs-bootclean.sh alsa-utils: mountall.sh mountnfs.sh mountnfs-bootclean.sh x11-common: mountall.sh mountnfs.sh mountnfs-bootclean.sh bootmisc.sh: mountall.sh mountnfs.sh mountnfs-bootclean.sh udev lm-sensors: mountall.sh mountnfs.sh mountnfs-bootclean.sh screen-cleanup: mountall.sh mountnfs.sh mountnfs-bootclean.sh stop-bootlogd-single: mountall.sh udev console-screen.sh keymap.sh keyboard-setup console-setup cryptdisks cryptdisks-early networking mountkernfs.sh fuse mountnfs.sh mountnfs-bootclean.sh nfs-common rpcbind hwclock.sh checkroot.sh lvm2 checkfs.sh mountdevsubfs.sh ifscheme urandom alsa-utils ebtables hostname.sh x11-common bootmisc.sh mtab.sh mountall-bootclean.sh qemu-kvm procps hdparm bootlogd kmod checkroot-bootclean.sh pppd-dns lm-sensors screen-cleanup udev-mtab signature.asc Description: This is a digitally signed message part
Bug#677712: [Pkg-sysvinit-devel] Bug#677712: sysvinit-utils: startpar not allow to start cryptdisks
Yes, both initscrips from cryptsetup have X-Interactive: true line В Сбт, 16/06/2012 в 15:13 -0300, Henrique de Moraes Holschuh пишет: On Sat, 16 Jun 2012, Roger Leigh wrote: On Sat, Jun 16, 2012 at 03:00:55PM +0400, Alexander V. Kudrevatykh wrote: Package: sysvinit-utils Version: 2.88dsf-27 Severity: important after upgrading to 2.88dsf-27 boot stops on cleaning temprorary files... /tmp and not ask password for cryptdisks disabling cryptdisks or switch to legacy boot order fixes problem Any idea about what is causing the breakage here? Does cryptdisks have incorrect LSB dependencies? Does cryptdisks declare its initscript as interactive? My guess is that it needs to have its stdin connected to the controlling terminal to ask for passwords... signature.asc Description: This is a digitally signed message part
