[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Thanks for reporting this. It is quite an old bug now, and probably did not get
any attention because it was not assigned to a package.
Having said that, I am not sure which is the right package to assign this bug
to. Therefore I am assigning it to cloud-init, as I found a similar type of bug
Thanks for reporting this. It is quite an old bug now, and probably did not get
any attention because it was not assigned to a package.
Having said that, I am not sure which is the right package to assign this bug
to. Therefore I am assigning it to cloud-init, as I found a similar type of bug
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028682
Title:
precise uec builds eat 100% cpu on launch, check-apt and rsyslogd
To manage notifications about this bug go to:
The initial hang for ssh logins may be due to /etc/update-motd.d trying
to dynamically create a new motd and running updates-available. The UEC
images assume there is a host resolvable called ubuntu-
mirrir.localdomain, which is not always necessarily the case. Since
these are typically
I have verified that clearing out most of the dynamic content relying on
Internet-facing connectivity from update-motd.d and adding /sbin/stop
rsyslog to rc.local does solve the bug.
I suspect the problem with rsyslogd spinning at 100% cpu is a regression
from Lucid, where kmsg is only accessible
