** Description changed: Binary package hint: cloud-init Running tests for lucid rc, I came across one system that was not accessible via ssh. The console collected after waiting ended like: | [ 1.036270] Freeing unused kernel memory: 216k freed | [ 1.037531] Write protecting the kernel text: 4288k | [ 1.037892] Write protecting the kernel read-only data: 1324k | init: console-setup main process (62) terminated with status 1 | %G Because this was an ebs root instance, a shutdown was run, and console collected after that. I will attach that full console log. The interesting subsequent output was: | %G[ 240.805451] INFO: task apparmor_parser:182 blocked for more than 120 seconds. | [ 240.805466] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | [ 240.805581] INFO: task mount:209 blocked for more than 120 seconds. | [ 240.805587] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | [ 240.805683] INFO: task flush-8:1:232 blocked for more than 120 seconds. | [ 240.805689] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | init: plymouth main process (44) killed by SEGV signal^M^M | init: plymouth-splash main process (215) terminated with status 2^M^M | Generating locales...^M | en_GB.UTF-8... done^M | Generation complete.^M It appears that something apparmor related blocked for 240 seconds, which ran past my time alloted for boot and ssh connection. The system *did* come up, but in a much longer time frame than normal. instance info: - region: eu-west-1 - ami: ami-8f705afb - arch: i386 - build: 20100420 - root-store: ebs + region: eu-west-1 + ami: ami-8f705afb + instance-type: m1.small + arch: i386 + build: 20100420 + root-store: ebs
-- blocked tasks delay cloud-init for 240 seconds https://bugs.launchpad.net/bugs/567334 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
