Re: [Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Martin Pitt [02/06/2014 11:18 PM] Robert C Jennings [2014-02-06 20:57 -]: Fix is included in 20140125 daily build of raring. I presume/hope you mean trusty here :-) Yes, trusty too. :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is added by the cloud image build process and should be resolved in the next build. Fix was committed to lp:~ubuntu-on-ec2/vmbuilder/automated-ec2-builds revision #578 and #579. With this change the getty will only be started if 'stty -F /dev/ttyAMA0' returns without error (device is present). On 02/01/2014 07:39 AM, Martin Pitt wrote: Yes, I never thought of it as an LXC bug in the first place. Whatever installs that job (cloud-init? our cloud image build process?) ought to change the upstart job to only start up if such a device exists in the first place. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJS8/UzAAoJEHQMPZ7t8u1zrjUP/0PUAuQaaGAreZmYW7BZqHL/ gg9Hyi/WcelNTuKf6nsbCdwoQEEEZuTYxfLZSz6M40R8XAyLX53u23YBqab7z5/Z wxPqk+kohRqJVeAG600dqk31N5nwH187wUiu4y7QZkPOQz0U5wZD/hG+MoCRXpNs Al94OuG4EwBeGhY5+7vwpgltvd0JJMXDA4uIAhpd7bUaaiU22gETdhL8reNLw5ls 38Y6H4w43ec8eTF6LHuYeeznUlxUYaiajNW1l0XKxHPKsO1wGBDxOHjz6OmhKK2w AVwf8K6m4GI3EXuyvtEevIZJmeXxluaSkJ54/v8PPCHovcZy0/Fh6T8sNva3h0vO w7r/qPjmDzxQ1iI1Hq8e/LFpJeZeDeGtqiltbtC4hyrNzYAQDP1oxAZKWJihUOLW PKR+3cEp/e7clbfU64A3dvEuLerHiXEZJ7SFuOGH2cShnAnLYZ0MAszeHLZPE5A2 HgmAHmzrq7mABLguGCakF9K2SGK6Xiyd+OS15jPAYuFRyQI3Jw1JGgsfkQD7wf9n GlQoFgsTR6wgucffvFn3NzLxw3Ec3gg0grwdLi+LorR2on8800F4/YK/sU1eaOeS RbyTmBm0sgMJahY/ui4hXQaEyFxjRmRr5NPISf7lRNaBTpgbITN/0bod7oI6sdrc o0ZRYGvowfU9p7RrO4ue =vhas -END PGP SIGNATURE- ** Changed in: cloud-init (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Fix is included in 20140125 daily build of raring. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Thanks for the fix! Robert C Jennings [2014-02-06 20:57 -]: Fix is included in 20140125 daily build of raring. I presume/hope you mean trusty here :-) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
lxc-start-ephemeral doesn't attach to /dev/console but to /dev/tty1 which is why you don't see the boot messsages or that error. Unfortunately there isn't a great deal we can do about this in LXC, the best fix is to change the upstart job to only start with and not- container. A better fix would be to check whether things can be written to the device but that's trickier to do right and obviously the best fix would be to have a device namespace so we wouldn't have that kind of problem to begin with. Closing the lxc task. ** Changed in: lxc (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Yes, I never thought of it as an LXC bug in the first place. Whatever installs that job (cloud-init? our cloud image build process?) ought to change the upstart job to only start up if such a device exists in the first place. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
The problem can be mitigated by deleting /etc/init/ttyAMA0.conf or
editing to contain the following:
# ttyAMA0 - getty
#
# This service maintains a getty on ttyAMA0 from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345] and (
not-container or
container CONTAINER=lxc or
container CONTAINER=lxc-libvirt)
stop on runlevel [!2345]
pre-start script
# getty will not be started if the serial console is not present
stty -F /dev/ttyAMA0 -a 2 /dev/null /dev/null || { stop ; exit 0; }
end script
respawn
script
exec /sbin/getty -L ttyAMA0 115200 vt102
end script
# written by cloud image build process
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Robert C Jennings (rcj)
** Changed in: cloud-init (Ubuntu)
Status: New = In Progress
** Changed in: cloud-init (Ubuntu)
Milestone: None = ubuntu-13.04-month-5
** Changed in: cloud-init (Ubuntu)
Milestone: ubuntu-13.04-month-5 = None
** Changed in: cloud-init (Ubuntu)
Milestone: None = raring-updates
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1273205
Title:
/etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not
exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Martin, Can you confirm the contents of /etc/cloud/build.info? New cloud images have a test to make sure that this sort of thing shouldn't happen. Also I am a bit concerned that this might be an issue with upstart determiniing if its in a container. The previous version should have prevented the job from running within a container. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
** Changed in: cloud-init (Ubuntu) Status: In Progress = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Ah, thanks for pointing out /etc/cloud/build.info. In said chroot that says build_name: server serial: 20131219.1 Note that I created this container last Thursday (2014-01-23), I already wondered why there were a gazillion packages to dist-upgrade right after I created it with sudo lxc-create -t ubuntu-cloud -n trusty-cloud -- -r trusty but I created that on saucy, with trusty's cloud-image-utils (as saucy's doesn't find the armhf images). Perhaps that was the reason why it picked up an ancient cloud image. Is it possible to get a recent one with saucy's lxc-create, or should I upgrade the whole box to current trusty? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Another observation: I still see these messages today after dist- upgrading to container to latest trusty. But *only* with lxc-start, *not* with lxc-start-ephemeral. In the latter case, the job still gets started: $ sudo status ttyAMA0 ttyAMA0 start/running, process 769 but I don't see the spewage. With ps aux|grep ttyAMA I still see the job constantly being respawned, but it doesn't appear at the terminal any more (that might be an LXC quirk/feature/bug, probably unrelated to the cloud image itself). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
