[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-05-03 Thread Erik Andersson
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

[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-05-03 Thread Erik Andersson
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

[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-05-03 Thread Erik Andersson
Another report found here: http://askubuntu.com/questions/457248/vsftpd-not-working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313450 Title: Unable to start vsftpd on Ubuntu 14.04

[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-05-03 Thread Erik Andersson
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313450 Title: Unable

[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-04-29 Thread Erik Andersson
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

[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-04-29 Thread Erik Andersson
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

[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-04-29 Thread Erik Andersson
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

[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-04-29 Thread Erik Andersson
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

[Bug 1313450] [NEW] Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-04-27 Thread Erik Andersson
Public bug reported: 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

[Bug 1313450] [NEW] Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration

2014-04-27 Thread Erik Andersson
Public bug reported: 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