After doing a little more investigation, it looks like there are other
distributions that are having problems with vsftpd running on AWS EC2
instances.
It sounds like it may be related to a kernel bug that affect Xen
paravirtualized hosts.
http://www.gossamer-
** Tags added: paravirtualization xen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1313450
Title:
Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default
It is related to a kernel bug.
Don't know if you have the ability to upgrade kernels on EC2, but this
bug can be worked around by installing one of the latest Ubuntu Mainline
kernels.
You need at least: linux-image-3.15.0-031500rc2
Reference: http://www.deinon.com/wiki/doku.php?id=linux:ubuntu
I'm also having the exact same issue running vsftpd on Ubuntu 14.04 in
an Amazon/EC2 instance. Adding seccomp_sandbox=NO does not fix the
problem for me either.
Upgraded to vsftpd 3.0.2-1ubuntu2.14.04.1 that was just released on
2014-05-05 but this does not fix the issue.
here the message in
I am going to try the steps suggested here:
http://askubuntu.com/questions/453784/vsftpd-installation-not-working-as-of-14-04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1313450
Another report found here:
http://askubuntu.com/questions/457248/vsftpd-not-working
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1313450
Title:
Unable to start vsftpd on Ubuntu
That made no difference.
My configuration:
seccomp_sandbox=NO
Listen=YES
#Listen_IPV6
Anonymous=YES
#Local_enabled=YES
#Write_enabled=YES
This is taken from the kernel log (also visible in the syslogs).
Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160354] BUG: Bad page map in
process
apport information
** Tags added: apport-collected
** Description changed:
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is this the same as bug 1219857? Does adding seccomp_sandbox=NO to
/etc/vsftpd.conf work around the issue for you?
** Changed in: vsftpd (Ubuntu)
Status: New = Incomplete
--
You received this bug
