I'm confused. As I understand it, a simple solution exists upstream, it's been understood for over a month, and it's easy to apply. I also understand that this bug affects everybody who uses Ubuntu 14.04 on AWS, and it prevents anybody from using Ubuntu 14.04 in a production environment on AWS. A sketchy workaround -- replacing the kernel -- might suffice for test or development environments. (I'm rehashing what I've learned from https://groups.google.com/forum/#!topic/logstash-users/sFNrqRbI6EM and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308796 and the LKML....)
So why hasn't Ubuntu updated its AWS cloud images? Why didn't Ubuntu fix its kernel before re-releasing its AWS cloud images on 2014-06-07, at http://cloud-images.ubuntu.com/releases/14.04/release/? Was anybody aware, when releasing those images, that they are unreliable? If so, was there a release note that I missed? I don't understand the logistical issues that are keeping this bug unresolved. What would it take to escalate this bug to Critical? Either I'm affected by this kernel bug far more than everybody else is, I have unrealistic expectations about Ubuntu 14.04 LTS, or Ubuntu is being too opaque. What's happening? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration Status in “linux” package in Ubuntu: Confirmed Status in “vsftpd” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Status in “vsftpd” source package in Trusty: Invalid Bug description: The configuration submitted was modified during testing, but this also failed with the default configuration. The only solution I have found so far was to delete the configuration, this would allow the service to start, but obviously not work as intended. If I try to start the service manually using vsftpd or sudo vsftpd I receive the following error message: 500 OOPS: munmap I also tried the default commands /etc/init.d/vsftpd or service vsftpd start ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vsftpd 3.0.2-1ubuntu2 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 21:23:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vsftpd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-27T21:16:28.222467 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable Package: vsftpd 3.0.2-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-29T19:03:28.834467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp