[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
I can't fix that in general, as I don't know what causes these invalid rc2.d/ to rc5.d/ links with rcS init scripts. But for /etc/init.d/lvm2 in particular we can avoid running this pointless dummy script at all, I committed a change for this. ** Changed in: systemd (Ubuntu) Status: Triaged = Fix Committed ** Summary changed: - ordering cycles with early boot rcS scripts with inappropriate rc2.d links + ordering cycles with lvm2 init script with inappropriate rc2.d links -- 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/1431107 Title: ordering cycles with lvm2 init script with inappropriate rc2.d links Status in systemd package in Ubuntu: Fix Committed Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
I have the same problem with udev, screen-cleanup and udev-finish daniel@daniel-vaio:~$ grep Default-Start.*S /etc/rc[0-9].d/S0* /etc/rc2.d/S01udev:# Default-Start: S /etc/rc2.d/S02screen-cleanup:# Default-Start: S /etc/rc2.d/S02udev-finish:# Default-Start: S /etc/rc3.d/S01udev:# Default-Start: S /etc/rc3.d/S02screen-cleanup:# Default-Start: S /etc/rc3.d/S02udev-finish:# Default-Start: S /etc/rc4.d/S01udev:# Default-Start: S /etc/rc4.d/S02screen-cleanup:# Default-Start: S /etc/rc4.d/S02udev-finish:# Default-Start: S /etc/rc5.d/S01udev:# Default-Start: S /etc/rc5.d/S02screen-cleanup:# Default-Start: S /etc/rc5.d/S02udev-finish:# Default-Start: S My system sometimes boots ok, sometimes pymouth keeps using CPU after boot, sometimes NetworManagers can't run dnsmasq. -- 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/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
$ systemctl show --no-pager -p After apparmor After=system.slice systemd-journald.socket local-fs.target and: $ systemctl list-dependencies local-fs.target local-fs.target ● ├─-.mount ● ├─boot-efi.mount ● ├─home.mount ● ├─systemd-fsck-root.service ● └─systemd-remount-fs.service I think this is another bug that only shows the same symptoms as this bug. Could you please confirm this, before I open a new bug? ** Attachment added: debug.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+attachment/4346988/+files/debug.txt -- 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/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
Hi Martin, I think I can reproduce the appaprmor failure on every boot: $ systemctl status apparmor.service -l ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since So 2015-03-15 22:42:54 CET; 12h ago Docs: man:systemd-sysv-generator(8) Process: 543 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mär 15 22:42:54 benediktZ50-70 apparmor[543]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mär 15 22:42:54 benediktZ50-70 apparmor[543]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Mär 15 22:42:54 benediktZ50-70 apparmor[543]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mär 15 22:42:54 benediktZ50-70 apparmor[543]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Mär 15 22:42:54 benediktZ50-70 apparmor[543]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mär 15 22:42:54 benediktZ50-70 apparmor[543]: ...fail! Mär 15 22:42:54 benediktZ50-70 systemd[1]: apparmor.service: control process exited, code=exited status=123 Mär 15 22:42:54 benediktZ50-70 systemd[1]: Failed to start LSB: AppArmor initialization. Mär 15 22:42:54 benediktZ50-70 systemd[1]: Unit apparmor.service entered failed state. Mär 15 22:42:54 benediktZ50-70 systemd[1]: apparmor.service failed. However I have only one symlink in rcS: ls -l /etc/rc*/*lvm2 lrwxrwxrwx 1 root root 14 Dez 21 01:18 /etc/rcS.d/S08lvm2 - ../init.d/lvm2 I will now try a debug boot. System: Kubuntu 15.04 -- 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/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type:
[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
No, I only had these link, probably mine is another issue. It may be a disk failure, I'm trying a lot of distros lately. -- 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/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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
Re: [Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
Manglasape [2015-03-12 23:56 -]: Mmmm I'm having a similar issue, but after ls -l /etc/rc*/*lvm2* I have 1rwxrwxrwx 1 root root 14 mar 8 19:43 /etc/rcS.d/S08lvm2- ../init.d/lvm2. I am not sure, does that means that I only have the symlink in rcS.d? Yes, that looks fine then. Which links did you have before? It's terribly worrying that something creates these invalid links, given that /etc/init.d/lvm2's Default-Start: is only S. -- 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/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
That seems to make everything work OK on bootup. Thanks! I have no idea how those symlinks got there. I definitely didn't put them there manually. -- 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/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
Mmmm I'm having a similar issue, but after ls -l /etc/rc*/*lvm2* I have 1rwxrwxrwx 1 root root 14 mar 8 19:43 /etc/rcS.d/S08lvm2- ../init.d/lvm2. I am not sure, does that means that I only have the symlink in rcS.d? Btw I am using Kubuntu vivid. -- 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/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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