[Bug 1359689] Re: cryptsetup password prompt not shown
I upgraded to Ubuntu 15.10 (wily) with the default kernel 4.2.0-22 and this problem disappeared. Let me know if any other information would be helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359689 Title: cryptsetup password prompt not shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205751] Re: package libxml-sax-perl 0.99+dfsg-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2
** Attachment added: "main.log" https://bugs.launchpad.net/ubuntu/+source/libxml-sax-perl/+bug/1205751/+attachment/3752861/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205751 Title: package libxml-sax-perl 0.99+dfsg-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml-sax-perl/+bug/1205751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205751] [NEW] package libxml-sax-perl 0.99+dfsg-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2
Public bug reported: Failure upgrading Ubuntu 10.04 to 12.04 with do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libxml-sax-perl 0.99+dfsg-1ubuntu0.1 ProcVersionSignature: Ubuntu 2.6.32-46.107-server 2.6.32.60+drm33.26 Uname: Linux 2.6.32-46-server x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Fri Jul 26 17:19:57 2013 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 2 MarkForUpload: True PackageArchitecture: all SourcePackage: libxml-sax-perl Title: package libxml-sax-perl 0.99+dfsg-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to precise on 2013-07-28 (0 days ago) ** Affects: libxml-sax-perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205751 Title: package libxml-sax-perl 0.99+dfsg-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml-sax-perl/+bug/1205751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205751] Re: package libxml-sax-perl 0.99+dfsg-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2
** Attachment added: "apt.log" https://bugs.launchpad.net/ubuntu/+source/libxml-sax-perl/+bug/1205751/+attachment/3751710/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205751 Title: package libxml-sax-perl 0.99+dfsg-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml-sax-perl/+bug/1205751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037727] Re: support adding region/availability to mirror selection
I think you mean and not since availability zone names mean different things for different AWS accounts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037727 Title: support adding region/availability to mirror selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1037727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 903422] Re: Mount / Provide access to Android 4 (Ice Cream Sandwich, ICS) MTP devices
I get the same mtp-detect output as acunningham on Samsung Galaxy S3, Ubuntu 12.04. I followed the instructions in the howto in the bug description above. When I attempt to access the mounted directory, it hangs a long time then reports: ls: cannot access /mnt/android: Transport endpoint is not connected /var/log/syslog shows these messages: kernel: [ 5647.472020] usb 2-1.1: reset high-speed USB device number 5 using ehci_hcd S3's are selling like hotcakes and Ubuntu is increasingly popular. It would be super to have them work together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/903422 Title: Mount / Provide access to Android 4 (Ice Cream Sandwich, ICS) MTP devices To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/903422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997371] Re: Create command to add "multiverse" and "-backports" to apt sources
evfool: Agreed. deb-src is not critical for the most common uses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997371 Title: Create command to add "multiverse" and "-backports" to apt sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/997371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997371] Re: Create command to add "multiverse" and "-backports" to apt sources
Robert: The program works for multiverse on Lucid, Oneiric, Precise, though it only adds "deb" and not "deb-src" on Lucid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997371 Title: Create command to add "multiverse" and "-backports" to apt sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/997371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997371] Re: Create command to add "multiverse" and "-backports" to apt sources
Thanks for the tip! software-properties-gtk is nice for a desktop system, but on an Ubuntu server (e.g., EC2 instances) it is not installed by default. On a fresh Ubuntu 12.04 LTS Precise server I would need to give the following extra instructions: sudo apt-get update && sudo apt-get install software-properties-gtk && sudo software-properties-gtk --enable-component multiverse && sudo apt-get update && sudo apt-get install ... This package pulls in: apt-xapian-index dbus-x11 defoma docbook-xml esound-clients esound-common fontconfig fontconfig-config gamin gconf2 gconf2-common ghostscript gksu gnome-keyring gnome-mime-data gsfonts gvfs gvfs-backends hicolor-icon-theme indicator-application launchpad-integration libappindicator0 libarchive1 libart-2.0-2 libasound2 libatasmart4 libatk1.0-0 libatk1.0-data libaudiofile0 libavahi-client3 libavahi-common-data libavahi-common3 libavahi-glib1 libbluetooth3 libbonobo2-0 libbonobo2-common libbonoboui2-0 libbonoboui2-common libcairo-perl libcairo2 libcdio-cdda0 libcdio-paranoia0 libcdio10 libcups2 libcupsimage2 libdatrie1 libdbusmenu-glib1 libdbusmenu-gtk1 libdirectfb-1.2-0 libesd0 libexif12 libfontconfig1 libfontenc1 libgail18 libgamin0 libgconf2-4 libgcr0 libgdu0 libgksu2-0 libglade2-0 libglib-perl libgnome-keyring0 libgnome2-0 libgnome2-canvas-perl libgnome2-common libgnome2-perl libgnome2-vfs-perl libgnomecanvas2-0 libgnomecanvas2-common libgnomeui-0 libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgnomevfs2-extra libgomp1 libgp11-0 libgphoto2-2 libgphoto2-port0 libgs8 libgtk2-perl libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop2-7 libgtop2-common libgudev-1.0-0 libgvfscommon0 libice6 libidl0 libimobiledevice0 libindicator0 libjasper1 libjpeg62 libjson-glib-1.0-0 liblaunchpad-integration1 liblcms1 libltdl7 liblzma1 libmagickcore2 libmagickwand2 libntfs10 libopenobex1 liborbit2 libpam-gnome-keyring libpango-perl libpango1.0-0 libpango1.0-common libpaper-utils libpaper1 libpixman-1-0 libplist1 libpolkit-agent-1-0 libpolkit-backend-1-0 libproxy0 librarian0 libsgutils2-2 libsm6 libsmbclient libsoup-gnome2.4-1 libsoup2.4-1 libstartup-notification0 libsysfs2 libtalloc2 libthai-data libthai0 libtiff4 libts-0.0-0 libusb-1.0-0 libusbmuxd1 libvte-common libvte9 libwbclient0 libxcb-atom1 libxcb-aux0 libxcb-event1 libxcb-render-util0 libxcb-render0 libxcomposite1 libxcursor1 libxdamage1 libxfixes3 libxfont1 libxft2 libxi6 libxinerama1 libxrandr2 libxrender1 libxt6 mtools ntfsprogs obex-data-server policykit-1 policykit-1-gnome psfontmgr python-cairo python-debian python-glade2 python-gtk2 python-xapian rarian-compat scrollkeeper sgml-data shared-mime-info synaptic tsconf ttf-dejavu-core udisks usbmuxd x-ttcidfont-conf x11-common xfonts-encodings xfonts-utils which seems like a lot just to change a few lines in a text file. I believe it is worth reducing this to just one command that is pre- installed on any basic Ubuntu system. Adding multiverse is an extremely common action (especially with AWS users) that should be easy to point folks to. ** Changed in: software-properties (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997371 Title: Create command to add "multiverse" and "-backports" to apt sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/997371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997371] Re: Create command to add "multiverse" and "-backports" to apt sources
** Description changed: Based on a discussion at UDS-Q a simple command is desired to be able to add/enable "multiverse" and/or "-backports" in the apt repositories on a system. Background: Right now, it is trivial to add a PPA to the apt sources using the apt-add-repository command. For example, I can tell somebody on IRC/email/blog to run these commands: - sudo apt-add-repository ppa:awstools-dev/awstools && sudo apt-get - update && sudo apt-get install elbcli + sudo apt-add-repository ppa:awstools-dev/awstools && + sudo apt-get update && + sudo apt-get install elbcli Presto! They have the correct package installed and this works on a number of different Ubuntu releases. Unfortunately, it is much more common to point people to the more popular "multiverse" (and occasionally "-backports") sections of the standard apt repositories, but it is much more difficult to describe how to enable these. For example, to install the ec2-api-tools currently available in multiverse, I have to provide non-standard and confusing instructions like: - # Enable "multiverse" in your apt sources using something like - sudo perl -pi -e 'next if /-backports/; s/^# (deb.* multiverse)$/$1/' /etc/apt/sources.list - # unless you're on an older version of Ubuntu which has a different sources.list format, - # in which case you might need to use something like: - sudo perl -pi -e 's%(universe)$%$1 multiverse%' /etc/apt/sources.list - # then - sudo apt-get update && sudo apt-get install ec2-api-tools + # Enable "multiverse" in your apt sources using something like + sudo perl -pi -e \ + 'next if /-backports/; s/^# (deb.* multiverse)$/$1/' /etc/apt/sources.list + # unless you're on an older version of Ubuntu which has a different sources.list + # format, in which case you might need to use something like: + sudo perl -pi -e 's%(universe)$%$1 multiverse%' /etc/apt/sources.list + # then + sudo apt-get update && + sudo apt-get install ec2-api-tools I would much rather be able to simply say something like: - sudo apt-add-source multiverse && sudo apt-get update && sudo apt- - get install ec2-api-tools + sudo apt-add-source multiverse && + sudo apt-get update && + sudo apt-get install ec2-api-tools (I don't care about the name of the tool. I just want it to be easy to provide in instructions.) In addition to "multiverse" it would be nice to support "-backports" and perhaps "partner". Ideally, this would be available for all active Ubuntu releases, but getting it in going forward would be a good start. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apt 0.8.16~exp12ubuntu10 ProcVersionSignature: User Name 3.2.0-23.36-virtual 3.2.14 Uname: Linux 3.2.0-23-virtual x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Wed May 9 21:50:13 2012 Ec2AMI: ami-a29943cb Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-825ea7eb Ec2Ramdisk: unavailable ProcEnviron: - TERM=xterm - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997371 Title: Create command to add "multiverse" and "-backports" to apt sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/997371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997371] Re: Create command to add "multiverse" and "-backports" to apt sources
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997371 Title: Create command to add "multiverse" and "-backports" to apt sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/997371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997371] [NEW] Create command to add "multiverse" and "-backports" to apt sources
Public bug reported: Based on a discussion at UDS-Q a simple command is desired to be able to add/enable "multiverse" and/or "-backports" in the apt repositories on a system. Background: Right now, it is trivial to add a PPA to the apt sources using the apt-add-repository command. For example, I can tell somebody on IRC/email/blog to run these commands: sudo apt-add-repository ppa:awstools-dev/awstools && sudo apt-get update && sudo apt-get install elbcli Presto! They have the correct package installed and this works on a number of different Ubuntu releases. Unfortunately, it is much more common to point people to the more popular "multiverse" (and occasionally "-backports") sections of the standard apt repositories, but it is much more difficult to describe how to enable these. For example, to install the ec2-api-tools currently available in multiverse, I have to provide non-standard and confusing instructions like: # Enable "multiverse" in your apt sources using something like sudo perl -pi -e \ 'next if /-backports/; s/^# (deb.* multiverse)$/$1/' /etc/apt/sources.list # unless you're on an older version of Ubuntu which has a different sources.list # format, in which case you might need to use something like: sudo perl -pi -e 's%(universe)$%$1 multiverse%' /etc/apt/sources.list # then sudo apt-get update && sudo apt-get install ec2-api-tools I would much rather be able to simply say something like: sudo apt-add-source multiverse && sudo apt-get update && sudo apt-get install ec2-api-tools (I don't care about the name of the tool. I just want it to be easy to provide in instructions.) In addition to "multiverse" it would be nice to support "-backports" and perhaps "partner". Ideally, this would be available for all active Ubuntu releases, but getting it in going forward would be a good start. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apt 0.8.16~exp12ubuntu10 ProcVersionSignature: User Name 3.2.0-23.36-virtual 3.2.14 Uname: Linux 3.2.0-23-virtual x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Wed May 9 21:50:13 2012 Ec2AMI: ami-a29943cb Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-825ea7eb Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997371 Title: Create command to add "multiverse" and "-backports" to apt sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/997371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 939212] Re: AMI created from latest i386 Lucid image fails to boot
Here are a couple posts that reference the issue. It looks like smoser provided a fixed ec2-bundle-vol: https://forums.aws.amazon.com/thread.jspa?threadID=58232 https://lists.ubuntu.com/archives/ubuntu- cloud/2011-January/000477.html It isn't clear if the patch has made it into the official Amazon command line tools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939212 Title: AMI created from latest i386 Lucid image fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/939212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 939212] Re: AMI created from latest i386 Lucid image fails to boot
Chetan: Can you provide the commands you are using to bundle the AMI? ec2-bundle-vol or ec2-bundle-image? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939212 Title: AMI created from latest i386 Lucid image fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/939212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 939212] Re: AMI created from latest i386 Lucid image fails to boot
This is the key error: ALERT! /dev/disk/by-label/cloudimg-rootfs does not exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939212 Title: AMI created from latest i386 Lucid image fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/939212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
Scott: - With the CNAME solution, the requests still go to the internal IP address for standard EC2 instances. - I don't imagine that many non-EC2 people would try to configure their Ubuntu systems to use the EC2 repositories. - Canonical would get charged the same network fees for people outside of EC2 using the S3 solution as using the CNAME solution. - The CNAME method only requires a change to entries in Canonical's DNS servers, no action is required with SRUs and updates to AMIs. The only objection I've heard that makes sense is a concern about the risk of increase in cost from use by non-EC2 instances, but it sounds like Canonical is already willing to take that risk with the S3 solution. This decision doesn't affect me personally. It just seems CNAME is the right approach and I'm not sure why it is not being adopted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
+1 for cloudcontrol's recommendation to use CNAMEs. I've been recommending this to Canonical since we were discussing the initial setup of EC2 dedicated repositories. It would have avoided a couple issues that have happened since and would help prevent future problems as AWS releases new features. Amazon has also recommended this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871966] Re: FQDN written to /etc/hosts causes problems for clustering systems
Though I don't like the current way Oneiric manages /etc/hosts (and submitted related bug #890501) I agree with Scott that it is how Oneiric works on EC2 and changes could cause existing installations to break. In fact, I have automated system code that works around the "bug" which would break if the behavior were fixed. Not horrible for me personally, but I don't know how many might be in a similar situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871966 Title: FQDN written to /etc/hosts causes problems for clustering systems To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/871966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] Re: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1"
*** This bug is a duplicate of bug 854050 *** https://bugs.launchpad.net/bugs/854050 Stefan: Thanks for the clarification. It looks like I've been running 3.0.0-14.23 for 16 days and I haven't seen any further issues. Based on your comment, I'll mark this bug a duplicate of bug #854050. ** This bug has been marked a duplicate of bug 854050 BUG at /build/buildd/linux-2.6.38/mm/swapfile.c:255 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] Re: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1"
I am unable to reproduce the issue, but haven't been running many Oneiric AMIs so it may be something that doesn't happen a high percentage of the time. If you have found a bug in the code and have created a fix for it, it seems a shame to not release it. If you want me to run the new kernel to make sure it does not cause immediate new problems, I'd be happy to test it with my production Oneiric server. Please provide specific instructions on how this would be done in an EC2 instance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] Re: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1"
Is this bug still on track to be fixed? What is the next step required? Should it have somebody assigned? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893400] Re: cloud-init: Output machine usable public ssh host key (for known_hosts)
** Description changed: In bug #892554, Kees Cook (kees) makes a great suggestion that cloud- init could output the public ssh host keys to the console output. This could then be read by automated software outside of the instance and added to a known_hosts file using the IP address and/or hostname that the remote system wishes to use to connect to the instance. As Scott Moser (smoser) points out, the existing ssh host key fingerprints should be left in the output in the current de facto standard format so as to not break any existing software or human processes that check this. The new output should be added using a different set of public ssh host key delimiters (see proposed format below). There is no need to require a cloud-init configuration option; this information should always be output. Extra information in the console output should not interfere with any existing programs as long as it is separate from the existing formatted information. - The simplest way to present the information might be to just print out - the first two fields of all public host keys. For example: + The simplest way to present the information might be to just output the + contents of all public host keys. For example: - cut -f1-2 -d' ' /etc/ssh/ssh_host_*_key.pub + cat /etc/ssh/ssh_host_*_key.pub The client system would query the console output, select one of these ssh host keys, and add it to known_hosts, prepended by the IP address and/or hostnames that it wishes to use to connect to the instance. Here's an example of what this might look like in the console output: -BEGIN PUBLIC SSH HOST KEYS- - ssh-dss B3NzaC1kc3MAAACBAOx12z6/snxt5HWbRZNmvs/hH+5EXsLLKR4XnyH56EQFNmpxGy3O5qBNvNpt4GejLmFR6TJdMANwFhkOfUkLcotTpgm+z3nA4wFUZt23o2CjYvqHSx5pOON390XM6xHhXzlGlkip5XUVM4flNhwQNAvt+9bo3//OTtXEZ1ZZ2M8bFQDiJIlHJxNS2jOsiHIsm5g3Vl5JuwAAAIEAiZXdnPnupHa5EvqAmaa0Gdzqp1mcRm7a/ovQ/Oko/IByF0OqAEZtb3VevUOoC1HFBoYfcP1kRKdey/W7TyLJPYWt/ZuMdNmZSuPZt7U99WkRt+sGfOlTc2PnxbKzbC+dqcBpuVvjy7AJEngucUJ8lykrpR30Fo538KkSHcITf+QAAACBAONcYr7hoksk3BhtvxFKjXoqcwBiDxAuj+aq90oWsenWfStuOO84eg1tJhZNp0VFv9mICevICoY4P+3ZjD7SvTdq5Xk3Uw4wabgFE4rBwS4XrZMA9+O9/S8+b20h+pQSbfwZIZiULTjBP2I89acPExhmrApSpZ+ByqB3HvnKawG+ - ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= - ssh-rsa B3NzaC1yc2EDAQABAAABAQC0I3L8UiDoF4LkzpJNHBDM2w9JFE6CbvmAQgW6+czbDOwvrFxQU2rw2HLLUOn+Z2WCE5AJSY7E7pxCrDo1v27hkVgaM6KqWks74vYxIkqfGCyf31y1N8QrmVCsAC74KFp9rhwP0uHmrN8XUIYFik8MoNphf+2aKWieJdZtzQGQ22mNNKDkP1yX3Uvb1QI+8d770dcIqr61AwkUBQgPgPyeii8W7r2+nq1lNQEnYts0N+13+40lEShnrRtsdKY6diEVs2uQId7VWw04lXOzWGi8oSWlunDWyRCQPtfvBFQtJ8AsivyZjmBuN9VJSDHLY1EQhXayygKfi6u6GKFVLZmd + ssh-dss B3NzaC1kc3MAAACBAOx12z6/snxt5HWbRZNmvs/hH+5EXsLLKR4XnyH56EQFNmpxGy3O5qBNvNpt4GejLmFR6TJdMANwFhkOfUkLcotTpgm+z3nA4wFUZt23o2CjYvqHSx5pOON390XM6xHhXzlGlkip5XUVM4flNhwQNAvt+9bo3//OTtXEZ1ZZ2M8bFQDiJIlHJxNS2jOsiHIsm5g3Vl5JuwAAAIEAiZXdnPnupHa5EvqAmaa0Gdzqp1mcRm7a/ovQ/Oko/IByF0OqAEZtb3VevUOoC1HFBoYfcP1kRKdey/W7TyLJPYWt/ZuMdNmZSuPZt7U99WkRt+sGfOlTc2PnxbKzbC+dqcBpuVvjy7AJEngucUJ8lykrpR30Fo538KkSHcITf+QAAACBAONcYr7hoksk3BhtvxFKjXoqcwBiDxAuj+aq90oWsenWfStuOO84eg1tJhZNp0VFv9mICevICoY4P+3ZjD7SvTdq5Xk3Uw4wabgFE4rBwS4XrZMA9+O9/S8+b20h+pQSbfwZIZiULTjBP2I89acPExhmrApSpZ+ByqB3HvnKawG+ root@ip-10-32-30-193 + ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= root@ip-10-32-30-193 + ssh-rsa B3NzaC1yc2EDAQABAAABAQC0I3L8UiDoF4LkzpJNHBDM2w9JFE6CbvmAQgW6+czbDOwvrFxQU2rw2HLLUOn+Z2WCE5AJSY7E7pxCrDo1v27hkVgaM6KqWks74vYxIkqfGCyf31y1N8QrmVCsAC74KFp9rhwP0uHmrN8XUIYFik8MoNphf+2aKWieJdZtzQGQ22mNNKDkP1yX3Uvb1QI+8d770dcIqr61AwkUBQgPgPyeii8W7r2+nq1lNQEnYts0N+13+40lEShnrRtsdKY6diEVs2uQId7VWw04lXOzWGi8oSWlunDWyRCQPtfvBFQtJ8AsivyZjmBuN9VJSDHLY1EQhXayygKfi6u6GKFVLZmd root@ip-10-32-30-193 -END PUBLIC SSH HOST KEYS- And here's an example of what the client system might add to known_hosts: 50.16.12.209,ec2-50-16-12-209.compute-1.amazonaws.com ecdsa- sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= + root@ip-10-32-30-193 or with hashing: |1|q0CnRd/EVpfAXEVMAi7fqx0lFaI=|8BrFOu2+GGRMKDS+1WiVG8xpwt0= ecdsa- sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= + root@ip-10-32-30-193 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 22 00:12:40 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unkno
[Bug 893400] Re: cloud-init: Output machine usable public ssh host key (for known_hosts)
I've ammended the original example to use "cat" instead of "cut" as it looks like the specific number of fields in the key may vary for some older formats (rsa1) and it removes the objection that I invented anything. I had been hoping to exclude the comment field, but agree it's not worth the effort/risk. The man page for sshd(8) documents the format for /etc/ssh/ssh_known_hosts and ~/.ssh/known_hosts in the "SSH_KNOWN_HOSTS FILE FORMAT" section. It includes the paragraphs: Bits, exponent, and modulus are taken directly from the RSA host key; they can be obtained, for example, from /etc/ssh/ssh_host_key.pub. The optional comment field continues to the end of the line, and is not used. and:: [generate lines in known_hosts] by a script, ssh-keyscan(1) or by taking /etc/ssh/ssh_host_key.pub and adding the host names at the front. I suppose you could copy the information out of these files using ssh- keygen, but it converts the key to a different format. I lean towards copying the public key file directly because: - It's easier to find and manipulate single lines in the console output, instead of the multi-line output of ssh-keygen. - The public key file contains exactly the format that we will drop into known_hosts, instead of having to convert the output of ssh-keygen back into something usable. (I'm not even sure what tool you use to do that, though on experimentation it looks like it's a process of cutting out headers, reassembling lines and adding the appropriate keytype string.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893400 Title: cloud-init: Output machine usable public ssh host key (for known_hosts) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/893400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 892554] Re: SSH keys summary does not report ECDSA key
Love the known_hosts suitable output format idea! It doesn't even need to be an option. Split that off into bug #893400. The current ticket can remain for adding the ECDSA ssh key fingerprint. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892554 Title: SSH keys summary does not report ECDSA key To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/892554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893400] Re: cloud-init: Output machine usable public ssh host key (for known_hosts)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893400 Title: cloud-init: Output machine usable public ssh host key (for known_hosts) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/893400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893400] [NEW] cloud-init: Output machine usable public ssh host key (for known_hosts)
Public bug reported: In bug #892554, Kees Cook (kees) makes a great suggestion that cloud- init could output the public ssh host keys to the console output. This could then be read by automated software outside of the instance and added to a known_hosts file using the IP address and/or hostname that the remote system wishes to use to connect to the instance. As Scott Moser (smoser) points out, the existing ssh host key fingerprints should be left in the output in the current de facto standard format so as to not break any existing software or human processes that check this. The new output should be added using a different set of public ssh host key delimiters (see proposed format below). There is no need to require a cloud-init configuration option; this information should always be output. Extra information in the console output should not interfere with any existing programs as long as it is separate from the existing formatted information. The simplest way to present the information might be to just print out the first two fields of all public host keys. For example: cut -f1-2 -d' ' /etc/ssh/ssh_host_*_key.pub The client system would query the console output, select one of these ssh host keys, and add it to known_hosts, prepended by the IP address and/or hostnames that it wishes to use to connect to the instance. Here's an example of what this might look like in the console output: -BEGIN PUBLIC SSH HOST KEYS- ssh-dss B3NzaC1kc3MAAACBAOx12z6/snxt5HWbRZNmvs/hH+5EXsLLKR4XnyH56EQFNmpxGy3O5qBNvNpt4GejLmFR6TJdMANwFhkOfUkLcotTpgm+z3nA4wFUZt23o2CjYvqHSx5pOON390XM6xHhXzlGlkip5XUVM4flNhwQNAvt+9bo3//OTtXEZ1ZZ2M8bFQDiJIlHJxNS2jOsiHIsm5g3Vl5JuwAAAIEAiZXdnPnupHa5EvqAmaa0Gdzqp1mcRm7a/ovQ/Oko/IByF0OqAEZtb3VevUOoC1HFBoYfcP1kRKdey/W7TyLJPYWt/ZuMdNmZSuPZt7U99WkRt+sGfOlTc2PnxbKzbC+dqcBpuVvjy7AJEngucUJ8lykrpR30Fo538KkSHcITf+QAAACBAONcYr7hoksk3BhtvxFKjXoqcwBiDxAuj+aq90oWsenWfStuOO84eg1tJhZNp0VFv9mICevICoY4P+3ZjD7SvTdq5Xk3Uw4wabgFE4rBwS4XrZMA9+O9/S8+b20h+pQSbfwZIZiULTjBP2I89acPExhmrApSpZ+ByqB3HvnKawG+ ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= ssh-rsa B3NzaC1yc2EDAQABAAABAQC0I3L8UiDoF4LkzpJNHBDM2w9JFE6CbvmAQgW6+czbDOwvrFxQU2rw2HLLUOn+Z2WCE5AJSY7E7pxCrDo1v27hkVgaM6KqWks74vYxIkqfGCyf31y1N8QrmVCsAC74KFp9rhwP0uHmrN8XUIYFik8MoNphf+2aKWieJdZtzQGQ22mNNKDkP1yX3Uvb1QI+8d770dcIqr61AwkUBQgPgPyeii8W7r2+nq1lNQEnYts0N+13+40lEShnrRtsdKY6diEVs2uQId7VWw04lXOzWGi8oSWlunDWyRCQPtfvBFQtJ8AsivyZjmBuN9VJSDHLY1EQhXayygKfi6u6GKFVLZmd -END PUBLIC SSH HOST KEYS- And here's an example of what the client system might add to known_hosts: 50.16.12.209,ec2-50-16-12-209.compute-1.amazonaws.com ecdsa- sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= or with hashing: |1|q0CnRd/EVpfAXEVMAi7fqx0lFaI=|8BrFOu2+GGRMKDS+1WiVG8xpwt0= ecdsa- sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 22 00:12:40 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893400 Title: cloud-init: Output machine usable public ssh host key (for known_hosts) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/893400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
Scott: Your suggested approach works for me even though I can't find any documentation on how this is supposed to work. Everything I read says that 127.0.1.1 should be the canonical hostname of the instance. Do you happen to have any pointers to the information you are alluding to with IPv6 and 127.0.1.2? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890501 Title: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
** Changed in: cloud-init (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890501 Title: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
Scott: Learn something new every day. I will give this a try. ** Changed in: cloud-init (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890501 Title: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890501] [NEW] EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
Public bug reported: cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like: 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233 I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say: 127.0.1.1 myhost.example.com myhost BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run. The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone. If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value. Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same. See also #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 15 00:17:46 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t1.micro Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890501 Title: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890501 Title: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
** Description changed: cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like: - 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233 + 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233 I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say: - 127.0.1.1 myhost.example.com myhost + 127.0.1.1 myhost.example.com myhost BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run. The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone. If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value. Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same. - See also #371936 where a similar bug was fixed back in 2009. Figure out - if there is some reason that this part of the system is fragile and + See also bug #371936 where a similar bug was fixed back in 2009. Figure + out if there is some reason that this part of the system is fragile and prone to breaking. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 15 00:17:46 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t1.micro Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking - something like: + When running an EC2 instance on Ubuntu 11.10 Oneiric, cloud-init sets up + /etc/hosts with a default value for 127.0.1.1 looking something like: 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233 I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say: 127.0.1.1 myhost.example.com myhost BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run. The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone. If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value. Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same. See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 15 00:17:46 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t1.micro Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably
[Bug 365233] Re: Provide Ubuntu EC2 kernels with 1000Hz timer (for VOIP/Asterisk)
I (original requester) suggest the status of this wishlist item be changed to "wontfix" now that there is a way for users to build their own kernels on EC2. Canonical does not need to support multiple kernels with different frequencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/365233 Title: Provide Ubuntu EC2 kernels with 1000Hz timer (for VOIP/Asterisk) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-on-ec2/+bug/365233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/884320/+attachment/2580467/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/884320/+attachment/2580468/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/884320/+attachment/2580466/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/884320/+attachment/2580465/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/884320/+attachment/2580464/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] Re: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1"
apport information ** Tags added: apport-collected ** Description changed: I started a new EC2 instance of Ubuntu 11.10 Oneiric using ami-a7f539ce in us-east-1. About two days later, it became non-responsive to ssh, http, etc. I found the following kernel oops stack trace in /var/log/syslog. I stopped/started the instance to get it running again, so the attached reports may not be the exact hardware on which it failed. - Oct 31 13:44:25 a111 kernel: [145151.54] BUG: unable to handle kernel paging request at f57ba9a1 Oct 31 13:44:25 a111 kernel: [145151.542248] IP: [] swap_count_continued.isra.17+0x190/0x1b0 Oct 31 13:44:25 a111 kernel: [145151.542268] *pdpt = 21498027 *pde = 009ba067 *pte = Oct 31 13:44:25 a111 kernel: [145151.542287] Oops: 0002 [#1] SMP Oct 31 13:44:25 a111 kernel: [145151.542299] Modules linked in: xt_multiport iptable_filter ip_tables x_tables xfs acpiphp Oct 31 13:44:25 a111 kernel: [145151.542333] Oct 31 13:44:25 a111 kernel: [145151.542340] Pid: 5942, comm: apache2 Not tainted 3.0.0-12-virtual #20-Ubuntu Oct 31 13:44:25 a111 kernel: [145151.542356] EIP: 0061:[] EFLAGS: 00010246 CPU: 0 Oct 31 13:44:25 a111 kernel: [145151.542365] EIP is at swap_count_continued.isra.17+0x190/0x1b0 Oct 31 13:44:25 a111 kernel: [145151.542374] EAX: f57ba9a1 EBX: 09a1 ECX: ec6330c0 EDX: 003e Oct 31 13:44:25 a111 kernel: [145151.542384] ESI: ecc500a0 EDI: 003e EBP: e1497d60 ESP: e1497d50 Oct 31 13:44:25 a111 kernel: [145151.542394] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 Oct 31 13:44:25 a111 kernel: [145151.542402] Process apache2 (pid: 5942, ti=e1496000 task=e1fed940 task.ti=e1496000) Oct 31 13:44:25 a111 kernel: [145151.542413] Stack: Oct 31 13:44:25 a111 kernel: [145151.542419] ed3e55e0 eae82300 000239a1 fff4 e1497d90 c02162ed 0001 9375b045 Oct 31 13:44:25 a111 kernel: [145151.542449] 8000 d30f6068 003e edc31000 3e400194 000239a1 e149c070 Oct 31 13:44:25 a111 kernel: [145151.542479] e1497d9c c0218bec 00100073 e1497e28 c0207483 9375b045 8000 e1fed940 Oct 31 13:44:25 a111 kernel: [145151.542509] Call Trace: Oct 31 13:44:25 a111 kernel: [145151.542519] [] __swap_duplicate+0xcd/0x130 Oct 31 13:44:25 a111 kernel: [145151.542530] [] swap_duplicate+0x1c/0x50 Oct 31 13:44:25 a111 kernel: [145151.542541] [] copy_pte_range+0x373/0x480 Oct 31 13:44:25 a111 kernel: [145151.542552] [] copy_page_range+0x15f/0x2d0 Oct 31 13:44:25 a111 kernel: [145151.542565] [] dup_mmap+0x1d8/0x310 Oct 31 13:44:25 a111 kernel: [145151.542575] [] dup_mm+0xd5/0x220 Oct 31 13:44:25 a111 kernel: [145151.542586] [] ? sched_autogroup_fork+0x51/0x80 Oct 31 13:44:25 a111 kernel: [145151.542598] [] copy_mm+0x7b/0xc8 Oct 31 13:44:25 a111 kernel: [145151.542609] [] copy_process.part.27+0x56d/0xba0 Oct 31 13:44:25 a111 kernel: [145151.542620] [] copy_process+0x7e/0x90 Oct 31 13:44:25 a111 kernel: [145151.542631] [] do_fork+0xb2/0x2d0 Oct 31 13:44:25 a111 kernel: [145151.542642] [] ? _raw_spin_lock+0xd/0x10 Oct 31 13:44:25 a111 kernel: [145151.542655] [] ? do_fcntl+0x224/0x2c0 Oct 31 13:44:25 a111 kernel: [145151.542667] [] sys_clone+0x34/0x40 - ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-virtual 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 2011-10-31 16:16 seq crw-rw 1 root audio 116, 33 2011-10-31 16:16 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.23-0ubuntu3 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory CurrentDmesg: [ 21.269721] ip_tables: (C) 2000-2006 Netfilter Core Team Date: Mon Oct 31 16:43:14 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: c1.medium Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 2011-10-31 16:16 seq + crw-rw 1 root audio 116, 33 2011-10-31 16:16 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 1.23-0ubuntu3 + Architecture: i386 + ArecordDevices: Error: [Errno 2] No such file or directory + CurrentDmesg: [ 21.269721] ip_tables: (C) 2000-2006 Netfilter Core Team + DistroRelease: Ubuntu 11.10 + Ec2AMI: ami
[Bug 884320] Re: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1"
** Description changed: I started a new EC2 instance of Ubuntu 11.10 Oneiric using ami-a7f539ce in us-east-1. About two days later, it became non-responsive to ssh, http, etc. - I found the following kernel oops stack trace in /var/log/syslog: + I found the following kernel oops stack trace in /var/log/syslog. + + I stopped/started the instance to get it running again, so the attached + reports may not be the exact hardware on which it failed. - Oct 31 13:44:25 a111 kernel: [145151.54] BUG: unable to handle kernel paging request at f57ba9a1 Oct 31 13:44:25 a111 kernel: [145151.542248] IP: [] swap_count_continued.isra.17+0x190/0x1b0 - Oct 31 13:44:25 a111 kernel: [145151.542268] *pdpt = 21498027 *pde = 009ba067 *pte = - Oct 31 13:44:25 a111 kernel: [145151.542287] Oops: 0002 [#1] SMP + Oct 31 13:44:25 a111 kernel: [145151.542268] *pdpt = 21498027 *pde = 009ba067 *pte = + Oct 31 13:44:25 a111 kernel: [145151.542287] Oops: 0002 [#1] SMP Oct 31 13:44:25 a111 kernel: [145151.542299] Modules linked in: xt_multiport iptable_filter ip_tables x_tables xfs acpiphp - Oct 31 13:44:25 a111 kernel: [145151.542333] - Oct 31 13:44:25 a111 kernel: [145151.542340] Pid: 5942, comm: apache2 Not tainted 3.0.0-12-virtual #20-Ubuntu + Oct 31 13:44:25 a111 kernel: [145151.542333] + Oct 31 13:44:25 a111 kernel: [145151.542340] Pid: 5942, comm: apache2 Not tainted 3.0.0-12-virtual #20-Ubuntu Oct 31 13:44:25 a111 kernel: [145151.542356] EIP: 0061:[] EFLAGS: 00010246 CPU: 0 Oct 31 13:44:25 a111 kernel: [145151.542365] EIP is at swap_count_continued.isra.17+0x190/0x1b0 Oct 31 13:44:25 a111 kernel: [145151.542374] EAX: f57ba9a1 EBX: 09a1 ECX: ec6330c0 EDX: 003e Oct 31 13:44:25 a111 kernel: [145151.542384] ESI: ecc500a0 EDI: 003e EBP: e1497d60 ESP: e1497d50 Oct 31 13:44:25 a111 kernel: [145151.542394] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 Oct 31 13:44:25 a111 kernel: [145151.542402] Process apache2 (pid: 5942, ti=e1496000 task=e1fed940 task.ti=e1496000) Oct 31 13:44:25 a111 kernel: [145151.542413] Stack: Oct 31 13:44:25 a111 kernel: [145151.542419] ed3e55e0 eae82300 000239a1 fff4 e1497d90 c02162ed 0001 9375b045 Oct 31 13:44:25 a111 kernel: [145151.542449] 8000 d30f6068 003e edc31000 3e400194 000239a1 e149c070 Oct 31 13:44:25 a111 kernel: [145151.542479] e1497d9c c0218bec 00100073 e1497e28 c0207483 9375b045 8000 e1fed940 Oct 31 13:44:25 a111 kernel: [145151.542509] Call Trace: Oct 31 13:44:25 a111 kernel: [145151.542519] [] __swap_duplicate+0xcd/0x130 Oct 31 13:44:25 a111 kernel: [145151.542530] [] swap_duplicate+0x1c/0x50 Oct 31 13:44:25 a111 kernel: [145151.542541] [] copy_pte_range+0x373/0x480 Oct 31 13:44:25 a111 kernel: [145151.542552] [] copy_page_range+0x15f/0x2d0 Oct 31 13:44:25 a111 kernel: [145151.542565] [] dup_mmap+0x1d8/0x310 Oct 31 13:44:25 a111 kernel: [145151.542575] [] dup_mm+0xd5/0x220 Oct 31 13:44:25 a111 kernel: [145151.542586] [] ? sched_autogroup_fork+0x51/0x80 Oct 31 13:44:25 a111 kernel: [145151.542598] [] copy_mm+0x7b/0xc8 Oct 31 13:44:25 a111 kernel: [145151.542609] [] copy_process.part.27+0x56d/0xba0 Oct 31 13:44:25 a111 kernel: [145151.542620] [] copy_process+0x7e/0x90 Oct 31 13:44:25 a111 kernel: [145151.542631] [] do_fork+0xb2/0x2d0 Oct 31 13:44:25 a111 kernel: [145151.542642] [] ? _raw_spin_lock+0xd/0x10 Oct 31 13:44:25 a111 kernel: [145151.542655] [] ? do_fcntl+0x224/0x2c0 Oct 31 13:44:25 a111 kernel: [145151.542667] [] sys_clone+0x34/0x40 - ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-virtual 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 2011-10-31 16:16 seq crw-rw 1 root audio 116, 33 2011-10-31 16:16 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.23-0ubuntu3 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory CurrentDmesg: [ 21.269721] ip_tables: (C) 2000-2006 Netfilter Core Team Date: Mon Oct 31 16:43:14 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: c1.medium Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ub
[Bug 884320] Re: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1"
** Description changed: I started a new EC2 instance of Ubuntu 11.10 Oneiric using ami-a7f539ce in us-east-1. - About two days later, it became non-responsive + About two days later, it became non-responsive to ssh, http, etc. - I found the attached kernel stack trace in /var/log/syslog + I found the following kernel oops stack trace in /var/log/syslog: + + - + Oct 31 13:44:25 a111 kernel: [145151.54] BUG: unable to handle kernel paging request at f57ba9a1 + Oct 31 13:44:25 a111 kernel: [145151.542248] IP: [] swap_count_continued.isra.17+0x190/0x1b0 + Oct 31 13:44:25 a111 kernel: [145151.542268] *pdpt = 21498027 *pde = 009ba067 *pte = + Oct 31 13:44:25 a111 kernel: [145151.542287] Oops: 0002 [#1] SMP + Oct 31 13:44:25 a111 kernel: [145151.542299] Modules linked in: xt_multiport iptable_filter ip_tables x_tables xfs acpiphp + Oct 31 13:44:25 a111 kernel: [145151.542333] + Oct 31 13:44:25 a111 kernel: [145151.542340] Pid: 5942, comm: apache2 Not tainted 3.0.0-12-virtual #20-Ubuntu + Oct 31 13:44:25 a111 kernel: [145151.542356] EIP: 0061:[] EFLAGS: 00010246 CPU: 0 + Oct 31 13:44:25 a111 kernel: [145151.542365] EIP is at swap_count_continued.isra.17+0x190/0x1b0 + Oct 31 13:44:25 a111 kernel: [145151.542374] EAX: f57ba9a1 EBX: 09a1 ECX: ec6330c0 EDX: 003e + Oct 31 13:44:25 a111 kernel: [145151.542384] ESI: ecc500a0 EDI: 003e EBP: e1497d60 ESP: e1497d50 + Oct 31 13:44:25 a111 kernel: [145151.542394] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 + Oct 31 13:44:25 a111 kernel: [145151.542402] Process apache2 (pid: 5942, ti=e1496000 task=e1fed940 task.ti=e1496000) + Oct 31 13:44:25 a111 kernel: [145151.542413] Stack: + Oct 31 13:44:25 a111 kernel: [145151.542419] ed3e55e0 eae82300 000239a1 fff4 e1497d90 c02162ed 0001 9375b045 + Oct 31 13:44:25 a111 kernel: [145151.542449] 8000 d30f6068 003e edc31000 3e400194 000239a1 e149c070 + Oct 31 13:44:25 a111 kernel: [145151.542479] e1497d9c c0218bec 00100073 e1497e28 c0207483 9375b045 8000 e1fed940 + Oct 31 13:44:25 a111 kernel: [145151.542509] Call Trace: + Oct 31 13:44:25 a111 kernel: [145151.542519] [] __swap_duplicate+0xcd/0x130 + Oct 31 13:44:25 a111 kernel: [145151.542530] [] swap_duplicate+0x1c/0x50 + Oct 31 13:44:25 a111 kernel: [145151.542541] [] copy_pte_range+0x373/0x480 + Oct 31 13:44:25 a111 kernel: [145151.542552] [] copy_page_range+0x15f/0x2d0 + Oct 31 13:44:25 a111 kernel: [145151.542565] [] dup_mmap+0x1d8/0x310 + Oct 31 13:44:25 a111 kernel: [145151.542575] [] dup_mm+0xd5/0x220 + Oct 31 13:44:25 a111 kernel: [145151.542586] [] ? sched_autogroup_fork+0x51/0x80 + Oct 31 13:44:25 a111 kernel: [145151.542598] [] copy_mm+0x7b/0xc8 + Oct 31 13:44:25 a111 kernel: [145151.542609] [] copy_process.part.27+0x56d/0xba0 + Oct 31 13:44:25 a111 kernel: [145151.542620] [] copy_process+0x7e/0x90 + Oct 31 13:44:25 a111 kernel: [145151.542631] [] do_fork+0xb2/0x2d0 + Oct 31 13:44:25 a111 kernel: [145151.542642] [] ? _raw_spin_lock+0xd/0x10 + Oct 31 13:44:25 a111 kernel: [145151.542655] [] ? do_fcntl+0x224/0x2c0 + Oct 31 13:44:25 a111 kernel: [145151.542667] [] sys_clone+0x34/0x40 + - ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-virtual 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 2011-10-31 16:16 seq - crw-rw 1 root audio 116, 33 2011-10-31 16:16 timer + total 0 + crw-rw 1 root audio 116, 1 2011-10-31 16:16 seq + crw-rw 1 root audio 116, 33 2011-10-31 16:16 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.23-0ubuntu3 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory CurrentDmesg: [ 21.269721] ip_tables: (C) 2000-2006 Netfilter Core Team Date: Mon Oct 31 16:43:14 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: c1.medium Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable Lspci: - + Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/li
[Bug 884320] Re: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1"
** Attachment added: "stack-trace.txt" https://bugs.launchpad.net/bugs/884320/+attachment/2580430/+files/stack-trace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884320] [NEW] EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1"
Public bug reported: I started a new EC2 instance of Ubuntu 11.10 Oneiric using ami-a7f539ce in us-east-1. About two days later, it became non-responsive I found the attached kernel stack trace in /var/log/syslog ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-virtual 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 2011-10-31 16:16 seq crw-rw 1 root audio 116, 33 2011-10-31 16:16 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.23-0ubuntu3 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory CurrentDmesg: [ 21.269721] ip_tables: (C) 2000-2006 Netfilter Core Team Date: Mon Oct 31 16:43:14 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: c1.medium Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug ec2-images i386 oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884320 Title: EC2 oneiric "BUG: unable to handle kernel paging request at f57ba9a1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876168] Re: EC2 Oneiric ssh "no-pty" triggers "PTY allocation request failed on channel 0"
Closing as invalid. I wasn't testing correctly with a non-pty ssh. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876168 Title: EC2 Oneiric ssh "no-pty" triggers "PTY allocation request failed on channel 0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/876168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876168] Re: EC2 Oneiric ssh "no-pty" triggers "PTY allocation request failed on channel 0"
This may also be a problem on non-EC2 Oneiric; I have no way of testing that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876168 Title: EC2 Oneiric ssh "no-pty" triggers "PTY allocation request failed on channel 0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/876168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876168] [NEW] EC2 Oneiric ssh "no-pty" triggers "PTY allocation request failed on channel 0"
Public bug reported: When I start a standard Ubuntu 11.10 Oneiric instance (ami-a7f539ce) on Amazon EC2 I can ssh in just fine with the default .ssh/authorized_keys file. If I prefix the ssh key in .authorized_keys with the option "no-pty " then attempts to ssh fail with the error: PTY allocation request failed on channel 0 This worked fine on previous versions of Ubuntu but the behavior seems to have changed in Oneiric. This failure means that the gitolite package is not working on Ubuntu 11.10 Oneiric as it uses no-pty in the ssh authorized_keys file. Here's a sample of the $HOME/.ssh/authorized_keys file that fails: no-pty ssh-rsa B3NzaC1yc2EBIwAAAQEA6rn8cl41CkzaH4ZBhczOJZaR4xBBDI1Kelc2ivzVvCBTHcdJRWpDd5I5hY5W9qke9Tm4fH3KaUVndlcP0ORGvS3PAL4lTpkS4D4goMEFrwMO8BG0NoE8sf2U/7gaUkdcrDC7jzKYdwleRCI3uibNXiSdeG6RotClAAp7pMflDVp5WjjECDZ+8Jzs2wasdTwQYPhiWSiNcfbfS97QdtROf0AcoPWElZAgmabaDFBlvvzcqxQRjNp/zbpkFHZBSKp+Sm4+WsRuLu6TDe9lb2Ps0xvBp1FTHlJRUVKP2yeZbVioKnOsXcjLfoJ9TEL7EMnPYinBMIE3kAYw3FzZZFeX3Q== ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: ssh (not installed) ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Mon Oct 17 02:54:57 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: m1.small Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 oneiric ** Summary changed: - ec2 oneiric ssh "no-pty" triggers "PTY allocation request failed on channel 0" + EC2 Oneiric ssh "no-pty" triggers "PTY allocation request failed on channel 0" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876168 Title: EC2 Oneiric ssh "no-pty" triggers "PTY allocation request failed on channel 0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/876168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824947] Re: EC2 apt repository DNS resolution on VPC instances
Sorry, I should have been clear in the original bug report that I was submitting it on behalf of Amazon and another customer and did not experience it myself on that particular instance or AMI. Also, I'm not sure that "lack of a public IP" address as described in #615545 is sufficient to determine if you are in VPC now-a-days. When VPC was launched, all instances were entirely private, but Amazon later released the ability for a VPC instance to have a public IP address with direct Internet access as an optional feature depending on the customer's security policies. Modifying Canonical's DNS seems like the best approach to support current and future AWS services and features. Using a CNAME to an Elastic IP Address transfers the burden to Amazon for determining how the instance should access the apt repository (internal or external). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824947 Title: EC2 apt repository DNS resolution on VPC instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824947] Re: EC2 apt repository DNS resolution on VPC instances
Amazon recommends fixing this through DNS instead of through software on the instance. Instead of resolving eu-west-1.ec2.archive.ubuntu.com directly to an A record of the internal IP address starting with "10.", Canonical should change it to resolve to a CNAME of the external elastic IP address hostname (e.g., ec2-NNN-NNN-NNN-NNN.compute-1.amazonaws.com) This will resolve to the internal "10." IP address for normal EC2 instances saving performance and cost, and will resolve to the external elastic IP address for VPC EC2 instances. Making this change not only clears up the issue with VPC, but any other future situation where an EC2 instance cannot access "10." IP addresses and EC2 DNS points it to the external IP address of the apt repository. This approach also makes it easier for Canonical when the apt repository instance gets a new internal IP address (e.g., stop/start, failure). Canonical would simply reassociate the elastic IP address with the new/restarted instance and all DNS would resolve to the correct new IP address without Canonical making any changes to their DNS servers. If Canonical is concerned about the EC2 apt repositories being accessed from outside of EC2 (I wouldn't be, but it's your choice), Amazon recommends the following: "To protect the rep from being accessed outside of AWS, lockdown the security group rules to allow only traffic from the public AWS IP ranges (https://forums.aws.amazon.com/ann.jspa?annID=1097) and to the 10. network." Here is a github repository that keeps up to date lists of the EC2 IP address ranges in a format that is easy to parse: https://github.com/garnaat/missingcloud -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824947 Title: EC2 apt repository DNS resolution on VPC instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824947] Re: EC2 apt repository DNS resolution on VPC instances
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824947 Title: EC2 apt repository DNS resolution on VPC instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824947] [NEW] EC2 apt repository DNS resolution on VPC instances
Public bug reported: DNS names like eu-west-1.ec2.archive.ubuntu.com (apt repository for eu- west-1 on EC2) are currently resolving to private IP addresses (e.g., "10."). An EC2 instance running in VPC cannot access these repositories. More details and possible fixes at: https://forums.aws.amazon.com/thread.jspa?threadID=73379 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cloud-init 0.6.1-0ubuntu8 ProcVersionSignature: User Name 2.6.38-8.42-virtual 2.6.38.2 Uname: Linux 2.6.38-8-virtual i686 Architecture: i386 Date: Fri Aug 12 03:19:39 2011 Ec2AMI: ami-06ad526f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824947 Title: EC2 apt repository DNS resolution on VPC instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798505] Re: Tighten permissions on root@ ssh with EC2/UEC images
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798505 Title: Tighten permissions on root@ ssh with EC2/UEC images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/798505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798505] [NEW] Tighten permissions on root@ ssh with EC2/UEC images
Public bug reported: Binary package hint: cloud-init The EC2/UEC images currently allow users to ssh to root@ but do not give the user shell access. Instead, a helpful message is displayed to the user explaining they need to ssh to ubuntu@ and they are disconnected after 10 seconds. This is done with the following prefix in /root/.ssh/authorized_keys: command="echo 'Please login as the user \"ubuntu\" rather than the user \"root\".';echo;sleep 10" ssh-rsa ... The goal here is to prevent the user from having any serious access at all through root@ and to just be a helpful pointer for people who assume all EC2 AMIs are set up to allow ssh to root@ Users may change the ssh keys associated with /home/ubuntu/.ssh/authorized_keys and not know about or forget about the fact that there is some access also granted through /root/.ssh/authorized_keys The way that the /root/.ssh/authorized_keys file is currently implemented, an authorized user is blocked from shell access, but is granted some other permissions like doing port forwarding through the instance to anywhere that instance can connect. Hosts it connects to would also perceive the connection as coming from the instance. These additional permissions should be blocked in /root/.ssh/authorized_keys by adding qualifiers like: no-port-forwarding,no-agent-forwarding,no-X11-forwarding,no-pty These particular directives are based on best practices using subversion command= with ssh. The resulting prefix would then look like: command="echo 'Please login as the user \"ubuntu\" rather than the user \"root\".';echo;sleep 10",no-port-forwarding,no-agent- forwarding,no-X11-forwarding,no-pty ssh-rsa ... See the "command=" section in "man authorized_keys" for more details. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cloud-init 0.6.1-0ubuntu8 ProcVersionSignature: User Name 2.6.38-8.42-virtual 2.6.38.2 Uname: Linux 2.6.38-8-virtual i686 Architecture: i386 Date: Fri Jun 17 02:08:02 2011 Ec2AMI: ami-06ad526f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798505 Title: Tighten permissions on root@ ssh with EC2/UEC images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/798505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787802] Re: Update Manager halts waiting for response to apt-listchanges hidden under Details
Changing status to "Confirmed" because others have indicated they are having the same problem. ** Changed in: apt-listchanges (Ubuntu) Status: New => Confirmed ** Summary changed: - Update Manager halts waiting for response to apt-listchanges hidden under Details + Update Manager hangs waiting for response to apt-listchanges hidden under Details -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787802 Title: Update Manager hangs waiting for response to apt-listchanges hidden under Details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/787802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787802] Re: Update Manager halts waiting for response to apt-listchanges hidden under Details
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787802 Title: Update Manager halts waiting for response to apt-listchanges hidden under Details -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787802] [NEW] Update Manager halts waiting for response to apt-listchanges hidden under Details
Public bug reported: Binary package hint: apt-listchanges I have installed the package apt-listchanges. The Update Manager prompts me to upgrade some packages and I accept. The Update Manager starts the upgrade and then hangs. The only way to continue is to have enough knowledge to do the following: a. Recognize that the Update Manager has stopped the upgrade. b. Click "Details" to open up the terminal output and see the apt- listchanges log. c. Press "q" to exit out of the apt-listchanges pager. This sequence would be unknown to many new Ubuntu users who might have installed apt-listchanges thinking it looks like a useful package. There are a few problems here: 1. Update Manager is giving no indication that it is waiting for a response inside of the Details panel 2. The contents of the Details panel is hidden. This is fine when it's just technical output, but when waiting for input it needs to be open. 3. New Ubuntu users would have no idea that they need to press "q" to quite the apt-listchanges pager and continue the upgrade. I'm not sure what the best solution would be, but perhaps apt- listchanges could simply email the changes when it is run inside of the Upgrade Manager instead of waiting for a response from a user who cannot see it. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: apt-listchanges 2.85.6ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue May 24 13:44:44 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110415) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt-listchanges UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt-listchanges (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787802 Title: Update Manager halts waiting for response to apt-listchanges hidden under Details -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768625] Re: user prompted for sudo changes on upgrade in ec2/uec image
Since "UEC" is a specific product and this is used with both UEC and EC2, should the name be more generic like "cloud" instead of "uec"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768625 Title: user prompted for sudo changes on upgrade in ec2/uec image -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768683] Re: Natty forgets "Make Caps Lock an additional Ctrl"
I have no idea what package this falls into. I'm sure it's miscategorized right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768683 Title: Natty forgets "Make Caps Lock an additional Ctrl" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768683] Re: Natty forgets "Make Caps Lock an additional Ctrl"
** Package changed: console-setup (Ubuntu) => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768683 Title: Natty forgets "Make Caps Lock an additional Ctrl" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768683] [NEW] Natty forgets "Make Caps Lock an additional Ctrl"
Public bug reported: Binary package hint: console-setup I have checked "Make Caps Lock an additional Ctrl" but Natty occasionally forgets this and the Caps Lock key suddenly functions as a Caps Lock key. To fix this I have to go into the keyboard preferences to uncheck and then recheck "Make Caps Lock an additional Ctrl". I haven't figured out yet if there are any actions I take that can reliably reproduce this. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: keyboard-configuration 1.57ubuntu20 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Apr 21 16:41:52 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110415) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768683 Title: Natty forgets "Make Caps Lock an additional Ctrl" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745930] Re: cloud-init timeout waiting for metadata service on EC2
On second glance, cloud-init may actually be retrying the connection and the problem is that sometimes it takes longer than the current number of retries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745930 Title: cloud-init timeout waiting for metadata service on EC2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745930] Re: cloud-init timeout waiting for metadata service on EC2
In my experience in 2008-2009, just because networking is up on an EC2
instance does not mean that 169.254.169.254 is going to accept
connections and requests for meta-data and user-data. You need to wait
for this to become available. I had code to do this in Ubuntu AMIs I
built back then.
perl -MIO::Socket::INET -e 'until(new
IO::Socket::INET("169.254.169.254:80")){sleep 1}'
I used to think I was waiting for networking to come up, but it became
clear that the meta-data service was not listening even some times when
networking was working and I had a local IP address on the instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740658] Re: kernels compiled with"CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y" lead to weird clock drifts on some CPUs. This may up ending in DOS
** Also affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740658 Title: kernels compiled with"CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y" lead to weird clock drifts on some CPUs. This may up ending in DOS -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720440] Re: /etc/hosts is updated based on /etc/cloud/templates/hosts.tmpl
I would like to see a solution like the following for this and other files generated at startup (e.g., apt sources): If the user has not modified the file since it was created from a template, then the system should feel free to continue maintaining that file by regenerating it from the template on reboot, instance stop/start, booting of a new instance of an AMI based on an old instance, etc. This could be done by saving a hash or signature of the file after generating it from the template. If the signature no longer matches, then the file should not be overwritten again, but if the signature still matches, then the system should update the file to match the current environment (IP addresses, EC2 region, etc.). I think this solves most of the problems that folks are experiencing with the files not being maintained, while not creating the problems that would be experienced by users who want to manage their own files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/720440 Title: /etc/hosts is updated based on /etc/cloud/templates/hosts.tmpl -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 634487] Re: t1.micro instance hangs when installing sun java
Vlad: Off topic for the bug, but see: http://alestic.com/2009/06/ec2 -elastic-ip-internal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/634487 Title: t1.micro instance hangs when installing sun java -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506981] Re: ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another
ProRunner: Is there an emoticon for sticking your tongue out at somebody? :) -- ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another https://bugs.launchpad.net/bugs/506981 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662679] Re: EC2 kernel panic at boot with 34GB RAM
*** This bug is a duplicate of bug 651370 *** https://bugs.launchpad.net/bugs/651370 ** This bug has been marked a duplicate of bug 651370 ec2 kernel crash invalid opcode [#1] * You can subscribe to bug 651370 by following this link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651370/+subscribe -- EC2 kernel panic at boot with 34GB RAM https://bugs.launchpad.net/bugs/662679 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662679] Re: EC2 kernel panic at boot with 34GB RAM
*** This bug is a duplicate of bug 651370 *** https://bugs.launchpad.net/bugs/651370 Confirmed with my AWS account using same AMI in eu-west-1 and m2.2xlarge. Console log attached. ** Changed in: ec2-api-tools (Ubuntu) Status: New => Confirmed ** Attachment added: "console.log" https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/662679/+attachment/1728350/+files/console.log ** Changed in: ec2-api-tools (Ubuntu) Status: Confirmed => New ** Tags added: ec2-images ** Also affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-ec2 (Ubuntu) Status: New => Confirmed ** Changed in: ec2-api-tools (Ubuntu) Status: New => Invalid -- EC2 kernel panic at boot with 34GB RAM https://bugs.launchpad.net/bugs/662679 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506981] Re: ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another
ProRunner: You are adding a comment to a closed ticket, so it there is likely no action going to be take on it. I have created bug #672417 to which you are welcome to subscribe. -- ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another https://bugs.launchpad.net/bugs/506981 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672417] [NEW] Correct grammar, punctuation in root authorized_keys message on EC2
Public bug reported: Binary package hint: cloud-init Attempting to log in to the "root" user on an Ubuntu AMI returns the message: Please login as the ubuntu user rather than root user. This has two minor problems: 1. There is a missing "the" before the word "root". 2. Adding quotes around the usernames would reduce confusion (see https://bugs.launchpad.net/ubuntu/+source/ec2-init/+bug/506981/comments/7) Proposed new messaging: Please login as the user "ubuntu" rather than the user "root". or Please login as the "ubuntu" user rather than the "root" user. The first one is slightly clearer to me, but both get the message across. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ec2-init (not installed) ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Sun Nov 7 18:27:51 2010 Ec2AMI: ami-508c7839 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1b Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 maverick -- Correct grammar, punctuation in root authorized_keys message on EC2 https://bugs.launchpad.net/bugs/672417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665235] Re: attaching a volume to maverick instance may boot off it
EBS volumes and snapshots create this sort of problem regularly for me, generally with conflicting duplicate XFS UIDs which I have to override. The best solution for EC2 AMIs may be to always accept that /dev/sda1 is the boot disk. -- attaching a volume to maverick instance may boot off it https://bugs.launchpad.net/bugs/665235 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664083] Re: package missing ec2-describe-tags
*** This bug is a duplicate of bug 649742 *** https://bugs.launchpad.net/bugs/649742 This is simply a software version issue. The ec2-describe-tags is in the ec2-api-tools version 1.3-57419, but that version is not available on Ubuntu 10.04 at this time. The latest version on Ubuntu 10.04 is 1.3-46266 which correctly does not include ec2-describe-tags. This bug might be replaced by a request to upgrade the ec2-api-tools software package on Ubuntu 10.04. -- package missing ec2-describe-tags https://bugs.launchpad.net/bugs/664083 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588702] Re: instance went straight to terminated
I suspect that this may possibly be caused by an occasional (rare) EC2 glitch. If it doesn't happen regularly to multiple people, then it may not be worth investigating. EC2 instances are not infallible and users should be designing their architectures to survive the occasional failed instance. I used to see straight to terminated more from EC2 a couple years back, but the incidence has dramatically reduced to near zero. -- instance went straight to terminated https://bugs.launchpad.net/bugs/588702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574910] Re: High load averages on Lucid while idling
Rod: I think you are probably experiencing something completely unrelated to the bug identified in this launchpad report. It might be worth moving the conversation to a different bug or a different venue. If you are using ec2-consistent-snapshot to initiate your EBS snapshots (freezing an XFS file system) please see if the info in the following thread helps: http://groups.google.com/group/ec2ubuntu/browse_thread/thread/3aea02f7842d73e4/d1bd59ade2dbd36f -- High load averages on Lucid while idling https://bugs.launchpad.net/bugs/574910 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413953] Re: USB modem disconnect on Jaunty (uhci_hcd: host system error, PCI problems?)
Fabio: Thanks for following up. Unfortunately for this bug, I have since cancelled my US$60/mo 5GB limit Verizon USB modem and have switched to a US$30/mo unlimited 8 device hotspot integrated with my HTC EVO 4G Android phone on Sprint. I won't be able to perform further tests to see if the bug has been resolved or not. If nobody else is able to reproduce it, then I suppose it might as well be closed. -- USB modem disconnect on Jaunty (uhci_hcd: host system error, PCI problems?) https://bugs.launchpad.net/bugs/413953 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557483] Re: EC2 instance went straight to terminated i386/c1.medium
** Summary changed: - instance went straight to terminated i386/c1.medium + EC2 instance went straight to terminated i386/c1.medium -- EC2 instance went straight to terminated i386/c1.medium https://bugs.launchpad.net/bugs/557483 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597387] Re: pv-ops kernel only works in 3 of 4 zones in EC2
** Summary changed: - pv-ops kernel only works in 3 or 4 zones in EC2 + pv-ops kernel only works in 3 of 4 zones in EC2 ** Description changed: This bug is to track the state of using a pv-ops kernel on EC2 for Maverick. Currently the Maverick kernel when built with pv-ops and legacy patching - can be run on 3 out of 4 EC2 zone in us-east. + can be run on 3 out of 4 EC2 zone in us-east-1. ** Tags added: ec2-images -- pv-ops kernel only works in 3 of 4 zones in EC2 https://bugs.launchpad.net/bugs/597387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598325] Re: Build test 1000Hz Maverick kernel for Amazon EC2
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/50874648/Dependencies.txt -- Build test 1000Hz Maverick kernel for Amazon EC2 https://bugs.launchpad.net/bugs/598325 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598325] [NEW] Build test 1000Hz Maverick kernel for Amazon EC2
Public bug reported: Please build a 1000Hz Maverick kernel on Amazon EC2 for testing with VOIP applications like Asterisk. I have a client who has been running Asterisk on 64-bit Ubuntu 10.04 Lucid on Amazon EC2 and is experiencing problems with choppy voice quality with the 100Hz Lucid kernel on EC2. Others run Asterisk and Freeswitch successfully on EC2 using Amazon's 1000Hz kernel, which unfortunately is too old to work with Ubuntu Lucid (2.6.18). We would like to test Asterisk against a modern Ubuntu 1000Hz kernel on EC2. I chatted with jjohansen who thought that this probably would not be possible for the Lucid kernel, and asked me to submit this request against Maverick. Ideally, the 1000Hz Maverick kernel could also be backported to run with Lucid on EC2. I'm told this should be possible as demonstrated in https://edge.launchpad.net/~kernel-ppa/+archive/ppa For this test, the initial request is isolated to 64-bit architecture in the us-east-1 region, though it's perfectly fine for others to be published if that's easy. If the Asterisk tests show a significant improvement in VOIP quality, there would probably be sufficient demand for an additional series of supported 1000Hz kernels on EC2 to support this type of application. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.32-305-ec2 2.6.32-305.9 ProcVersionSignature: User Name 2.6.32-305.9-ec2 2.6.32.11+drm33.2 Uname: Linux 2.6.32-305-ec2 x86_64 Architecture: amd64 Date: Thu Jun 24 23:53:14 2010 Ec2AMI: ami-9351b8fa Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.large Ec2Kernel: aki-255eb74c Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-ec2 ** Affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images maverick -- Build test 1000Hz Maverick kernel for Amazon EC2 https://bugs.launchpad.net/bugs/598325 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598314] Re: bash_completion error messages on initial login to fresh Maverick instance on Amazon EC2
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/50874398/Dependencies.txt -- bash_completion error messages on initial login to fresh Maverick instance on Amazon EC2 https://bugs.launchpad.net/bugs/598314 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598314] [NEW] bash_completion error messages on initial login to fresh Maverick instance on Amazon EC2
Public bug reported: I created a brand new copy of the official Maverick alpha-1, 64-bit, us-east-1 AMI for Amazon EC2. 099720109477/ebs/ubuntu-images-milestone/ubuntu-maverick-alpha1-amd64-server-20100601 On ssh login, the following error messages spewed out before the command line prompt: -bash: /etc/bash_completion.d/apt: line 32: syntax error near unexpected token `;' -bash: /etc/bash_completion.d/apt: line 32: `2> /dev/null ); $( apt-cache --no-generate pkgnames "lib$cur" \' -bash: /etc/bash_completion.d/apt: line 33: syntax error near unexpected token `)' -bash: /etc/bash_completion.d/apt: line 33: `2> /dev/null); )' ubu...@domu-12-31-39-0b-04-11:~$ ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.32-305-ec2 2.6.32-305.9 ProcVersionSignature: User Name 2.6.32-305.9-ec2 2.6.32.11+drm33.2 Uname: Linux 2.6.32-305-ec2 x86_64 Architecture: amd64 Date: Thu Jun 24 23:43:50 2010 Ec2AMI: ami-9351b8fa Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.large Ec2Kernel: aki-255eb74c Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-ec2 ** Affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images maverick -- bash_completion error messages on initial login to fresh Maverick instance on Amazon EC2 https://bugs.launchpad.net/bugs/598314 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554431] Re: Bluetooth is disabled. Pressing "Turn on bluetooth" not working
One reboot fixed the problem on my system (so that bluetooth is now enabled and on), but this issue should still be corrected so that new Ubuntu users do not run into a big "Turn on bluetooth" button that does not work. -- Bluetooth is disabled. Pressing "Turn on bluetooth" not working https://bugs.launchpad.net/bugs/554431 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554431] Re: Bluetooth is disabled. Pressing "Turn on bluetooth" not working
I just had the same problem on a fairly new installation of Ubuntu 10.04 Lucid on a Dell Latitude E6500. I'm not sure that "two reboots" is an acceptable workaround for the general public. ** Changed in: bluez (Ubuntu) Status: Invalid => Confirmed -- Bluetooth is disabled. Pressing "Turn on bluetooth" not working https://bugs.launchpad.net/bugs/554431 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583542] Re: ssh server doesn't start when irrelevant filesystems are not available
This is especially important for remotely controlled servers which have no console access (e.g., Amazon EC2). -- ssh server doesn't start when irrelevant filesystems are not available https://bugs.launchpad.net/bugs/583542 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557713] Re: 239.283990] BUG: scheduling while atomic: swapper/0/0x10010000
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/43395482/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/43395483/AplayDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/43395484/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/43395485/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/43395486/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.1.txt" http://launchpadlibrarian.net/43395487/Card0.Codecs.codec.1.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/43395488/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/43395489/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/43395490/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/43395491/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/43395492/Lsusb.txt ** Attachment added: "OopsText.txt" http://launchpadlibrarian.net/43395493/OopsText.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/43395494/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/43395495/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/43395496/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/43395497/ProcModules.txt ** Attachment added: "RfKill.txt" http://launchpadlibrarian.net/43395498/RfKill.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/43395499/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/43395500/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/43395501/WifiSyslog.txt -- 239.283990] BUG: scheduling while atomic: swapper/0/0x1001 https://bugs.launchpad.net/bugs/557713 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557713] [NEW] 239.283990] BUG: scheduling while atomic: swapper/0/0x10010000
Public bug reported: Brand new install of Intrepid desktop on a Dell Latitude D820. No idea what caused the error, but it prompted me to submit this report. No idea if it's a duplicate of the many others that look similar. Let me know if you'd like me to try anything. This computer is not going to be used for much in the short term so I can reinstall or follow any specific set of steps you'd like. ProblemType: KernelOops DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-19-generic 2.6.32-19.28 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erich 1453 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801cc,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 12 Simple ctrls : 7 Date: Wed Apr 7 16:25:06 2010 Failure: oops Frequency: Once a day. HibernationDevice: RESUME=/dev/sda5 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1) MachineType: Dell Inc. Latitude D820 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=0d70a4e2-bfa4-4490-a8e8-f4bf9e5d0060 ro quiet splash RelatedPackageVersions: linux-firmware 1.33 SourcePackage: linux Title: 239.283990] BUG: scheduling while atomic: swapper/0/0x1001 dmi.bios.date: 04/02/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0GF470 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/02/2007:svnDellInc.:pnLatitudeD820:pvr:rvnDellInc.:rn0GF470:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D820 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops lucid needs-upstream-testing regression-potential -- 239.283990] BUG: scheduling while atomic: swapper/0/0x1001 https://bugs.launchpad.net/bugs/557713 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 502490] Re: ec2-init overwrites user/vmbuilder provided /etc/apt/sources.list
Scott: Is this fixed in Karmic or just Lucid? -- ec2-init overwrites user/vmbuilder provided /etc/apt/sources.list https://bugs.launchpad.net/bugs/502490 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438035] Re: Latest gdm doesn't read ~/.xsessionrc with ecryptfs anymore
Is the experienced problem related to bug 475090? -- Latest gdm doesn't read ~/.xsessionrc with ecryptfs anymore https://bugs.launchpad.net/bugs/438035 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 524562] Re: cloud-init cloud-config-mounts can add duplicate fstab entries
I don't think that "uniq -u" does what is needed here.This might be
closer to what you're looking for:
perl -ni -e 'print if !$seen{$_}++' /etc/fstab
but that would also remove repeated comment lines which may be desired
in some cases. Best to just not add duplicates in the first place.
--
cloud-init cloud-config-mounts can add duplicate fstab entries
https://bugs.launchpad.net/bugs/524562
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505482] Re: euca-bundle-vol dies with "Invalid cert"
Scott: Thanks for checking. The original AMI no longer exists, and I am also unable to reproduce this on the latest Lucid daily: ami-e9b95680 ubuntu-images-testing-us/ubuntu-lucid-daily-i386-server-20100301.manifest.xml I have marked the bug invalid. ** Changed in: euca2ools (Ubuntu) Status: Incomplete => Invalid -- euca-bundle-vol dies with "Invalid cert" https://bugs.launchpad.net/bugs/505482 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 514492] Re: hostname modifications user are overwritten by ec2init
With some software packages (e.g., Puppet) it's important for a hostname to be set correctly or the system may not function. I believe this is important enough to fix in future Hardy and Karmic AMIs. ** Changed in: ec2-init (Ubuntu) Importance: Low => Medium -- hostname modifications user are overwritten by ec2init https://bugs.launchpad.net/bugs/514492 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513060] Re: ec2/uec images should have complete apt package lists
FYI, the reason I did not include the apt package index in the original Ubuntu AMIs on EC2 was because: - it increased the size of the AMI by 40%, - there is a strong correlation between the AMI size and load time (pending to running), and - users should almost always "apt-get update" before upgrading or installing packages. On my Hardy ami-c4f615ad, disk usage goes from 393 MB to 553 MB with "apt-get update" (increase of 160 MB or 41%). On the Karmic ami-1515f67c, disk usage goes from 548 MB to 576 MB with "apt-get update (increase of 28 MB or 5%) so it is not as big of a deal. On the other hand, perhaps this is an indication of extra files left on the new Karmic images which might not be needed and which could be removed to speed up their startup time on EC2. Here's a couple sets of files for consideration with sizes on a fresh Karmic instance: 13M /var/cache/apt/pkgcache.bin 34M /var/lib/apt/lists -- ec2/uec images should have complete apt package lists https://bugs.launchpad.net/bugs/513060 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 499522] Re: swap turned off
Hi, it's me (again) trying to make sure that power users have the ability to control what they want (again). Is there a document or can you point me to code where the swap is automatically turned on? I'd like to be able to turn off swap in my /etc/fstab in my AMI and not have ec2-init override this. If necessary, I suppose I can turn off swap again later, but I get uncomfortable when the ec2-init keeps changing things out from under me after I have set them in my image (like it currently does with /etc/apt/sources.list). -- swap turned off https://bugs.launchpad.net/bugs/499522 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 512377] Re: ssh is started before hostkey is installed/regenerated
Changing this to "Confirmed" since I see this behavior occasionally on EC2 when I ssh in too quickly and then get a host key changed error when I ssh in again later. ** Changed in: ec2-init (Ubuntu) Status: New => Confirmed -- ssh is started before hostkey is installed/regenerated https://bugs.launchpad.net/bugs/512377 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494185] Re: ec2-init selects us-east-1 mirror when running in us-west-1 region
I verified this fix in my personal EC2 account using the 64-bit instances in eu-west-1, us-east-1, and us-west-1. # For each of these three groups, run the remainder of the commands region=eu-west-1 amiid=ami-4fcfe43b type=m1.large region=us-west-1 amiid=ami-c12c7d84 type=m1.large region=us-east-1 amiid=ami-bb12ffd2 type=m1.large # Add an ssh keypair for the region ec2-add-keypair \ --region $region \ ec2-$region \ > ~/.ssh/ec2-$region.pem # Run an instance and connect to it instanceid=$(ec2-run-instances \ --region $region \ --instance-type $type\ --key ec2-$region\ $amiid | egrep ^INSTANCE | cut -f2) echo "instanceid=$instanceid" while host=$(ec2-describe-instances --region $region "$instanceid" | egrep ^INSTANCE | cut -f4) && test -z $host; do echo -n .; sleep 1; done echo host=$host ssh\ -i ~/.ssh/ec2-$region.pem\ ubu...@$host # Enable proposed and get fixed ec2-init printf "%s %s %s %s\n" \ deb http://archive.ubuntu.com/ubuntu/ karmic-proposed main | sudo tee -a /etc/apt/sources.list sudo apt-get update && sudo apt-get install ec2-init # Let defaults be run on next reboot and reboot sudo rm -f /var/lib/ec2/ec2-defaults.ever sudo reboot # Connect to the instance again ssh\ -i ~/.ssh/ec2-$region.pem\ ubu...@$host # Verify archive host matches $region and test accessibility cat /etc/apt/sources.list sudo apt-get update && sudo apt-get upgrade -y exit # Kill the instance ec2-terminate-instances --region $region $instanceid Here is a sample /etc/apt/sources.list from the instance in us-west-1 (which had the original problem): deb http://eu-west-1.ec2.archive.ubuntu.com/ubuntu/ karmic main universe deb-src http://eu-west-1.ec2.archive.ubuntu.com/ubuntu/ karmic main universe deb http://eu-west-1.ec2.archive.ubuntu.com/ubuntu/ karmic-updates main universe deb-src http://eu-west-1.ec2.archive.ubuntu.com/ubuntu/ karmic-updates main universe deb http://security.ubuntu.com/ubuntu karmic-security main universe deb-src http://security.ubuntu.com/ubuntu karmic-security main universe ** Tags added: verification-done ** Tags removed: verification-needed -- ec2-init selects us-east-1 mirror when running in us-west-1 region https://bugs.launchpad.net/bugs/494185 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296610] Re: ALPS DualPoint Touchpad flaky performance
Thank you, Robert! Your instructions were very clear and helpful.
Some obvious touchpad bugs are clearly fixed on my E6500. I'll keep an
eye out for the other odd ones which were more sporadic, but so far, so
good.
For others attempting this on Jaunty, I'll point out:
- The referenced alps-dave-2.6.31.patch is available in the "Patches"
section towards the top right of the launchpad bug page.
- The patch had a couple rejects with the Jaunty kernel. In the first one, it
was pretty easy to see where to change the file drivers/input/mouse/alps.c so
that this line:
{ { 0x62, 0x02, 0x14 }, 0xcf, 0xcf, ALPS_PASS | ALPS_DUALPOINT }, /*
Dell Latitude E6500 */
instead read like:
{ { 0x62, 0x02, 0x14 }, 0xcf, 0xcf, DELL_STYLE_DUALPOINT },
The second patch reject was just comments.
- The final copying can be done a bit more easily using the commands:
sudo cp /lib/modules/$(uname -r)/kernel/drivers/input/mouse/psmouse.ko \
/lib/modules/$(uname -r)/kernel/drivers/input/mouse/psmouse.ko.orig
sudo cp ~/kernel/ubuntu-jaunty/drivers/input/mouse/psmouse.ko \
/lib/modules/$(uname -r)/kernel/drivers/input/mouse/psmouse.ko
- Install the new kernel module using:
sudo rmmod psmouse
sudo modprobe psmouse
If there's any way this can get into Jaunty it will make a lot of people
happy, but I'll try to spread the word to the folks I know who have been
hurting.
--
ALPS DualPoint Touchpad flaky performance
https://bugs.launchpad.net/bugs/296610
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296610] Re: ALPS DualPoint Touchpad flaky performance
I've been living with this horrible problem for a long time now. Is it possible to apply the patch on Jaunty? I'd be willing to test if somebody could walk me through the steps necessary. Hardware: Dell Latitude E6500 $ uname -srmv Linux 2.6.28-17-server #58-Ubuntu SMP Tue Dec 1 19:58:28 UTC 2009 i686 $ lsb_release -dc Description:Ubuntu 9.04 Codename: jaunty -- ALPS DualPoint Touchpad flaky performance https://bugs.launchpad.net/bugs/296610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 506981] Re: ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another
On second thought, you only get this notice if you are able to ssh to the root account with the correct private ssh key, so it's not much of a security risk to point out the username at that point. I have seen the "ubuntu" user message help new users of the Ubuntu AMIs, so I would keep that information. If they've reconfigured the username, then it's fine to remind them of the it, or simply to return a rejection on root@, even though they're using the right ssh key. I don't even have a preferance. Probably just do whatever is easiest to implement. -- ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another https://bugs.launchpad.net/bugs/506981 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 507070] Re: ssh keys not regenerated on first boot
I have confirmed that this is an issue for the latest daily Lucid AMI: ami-5936db30 ubuntu-images-testing-us/ubuntu-lucid-daily-i386-server-20100113.manifest.xml ubu...@domu-12-31-39-04-08-b2:~$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key 2048 15:46:e4:66:e3:60:b8:89:fe:d3:65:aa:7a:77:4e:cd /etc/ssh/ssh_host_rsa_key.pub (RSA) ubu...@domu-12-31-39-04-08-65:~$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key 2048 15:46:e4:66:e3:60:b8:89:fe:d3:65:aa:7a:77:4e:cd /etc/ssh/ssh_host_rsa_key.pub (RSA) I have confirmed that this is *not* an issue for the released Karmic AMI: ami-1515f67c ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml ubu...@domu-12-31-39-02-60-41:~$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key 2048 33:d7:a2:7d:ba:96:b0:e3:d7:f2:2e:be:04:24:38:ed /etc/ssh/ssh_host_rsa_key.pub (RSA) ubu...@domu-12-31-39-02-61-24:~$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key 2048 4e:e1:93:4c:31:9a:c8:f7:c7:f4:b0:6a:56:e1:97:78 /etc/ssh/ssh_host_rsa_key.pub (RSA) I did not test the latest daily Karmic AMI, but that should be checked before new Karmic AMIs are released. I started the importance to "High" since this effectively makes ssh unencrypted to a man in the middle which is a serious security issue for people who care about security. (Yes, I realize that most users don't check fingerprints on EC2, but it should at least be possible to be secure.) ** Changed in: ec2-init (Ubuntu) Status: New => Confirmed ** Changed in: ec2-init (Ubuntu) Importance: Undecided => High -- ssh keys not regenerated on first boot https://bugs.launchpad.net/bugs/507070 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506981] Re: ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another
Scott: Fair point. Perhaps if it is not "ubuntu", then we assume the AMI builder knows what they are doing and we completely disable root ssh by not updating /root/.ssh/authorized_keys (assuming root really is disabled in the config). I still think it's a bug that it points the user to "ubuntu" when that account does not exist. -- ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another https://bugs.launchpad.net/bugs/506981 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506981] Re: ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/37849522/Dependencies.txt -- ec2-fetch-credentials lists "ubuntu" user in root authorized_keys even if ec2-config.cfg specifies another https://bugs.launchpad.net/bugs/506981 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
