[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration
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 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1313450/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration
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 14.04 (Amazon/EC2) with default configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1313450/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration
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 vsftpd pte:8965 pmd:23042067 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160372] page:ea00 count:-259 mapcount:-259 mapping: (null) index:0x0 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160379] page flags: 0x10(dirty) Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160387] addr:7fd251b67000 vm_flags:08100071 anon_vma:88002381d700 mapping: (null) index:7fd251b67 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160397] CPU: 0 PID: 14426 Comm: vsftpd Tainted: GB3.13.0-24-generic #46-Ubuntu Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160399] 880023ca6c00 880016565c70 81715a64 7fd251b67000 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160404] 880016565cb8 81174183 800ffa106965 0007fd251b67 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160408] 880023042b38 ea00 7fd251b67000 7fd251b68000 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160411] Call Trace: Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160421] [81715a64] dump_stack+0x45/0x56 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160427] [81174183] print_bad_pte+0x1a3/0x250 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160430] [81175b67] unmap_page_range+0x717/0x7f0 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160433] [81175cc1] unmap_single_vma+0x81/0xf0 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160436] [81176d39] unmap_vmas+0x49/0x90 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160441] [8117feec] exit_mmap+0x9c/0x170 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160445] [8106482c] mmput+0x5c/0x120 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160449] [81069bbc] do_exit+0x26c/0xa50 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160453] [8109dd84] ? vtime_account_user+0x54/0x60 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160459] [8114d52f] ? context_tracking_user_exit+0x4f/0xc0 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160462] [8106a41f] do_group_exit+0x3f/0xa0 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160465] [8106a494] SyS_exit_group+0x14/0x20 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160469] [8172663f] tracesys+0xe1/0xe6 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160552] BUG: Bad rss-counter state mm:8800030af500 idx:0 val:-1 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.160559] BUG: Bad rss-counter state mm:8800030af500 idx:1 val:1 Apr 29 19:03:44 ip-10-34-255-23 kernel: [21095107.195341] BUG: Bad page map in process vsftpd pte:8965 pmd:23d36067 -- 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 configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1313450/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration
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 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 ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1313450/+attachment/4100694/+files/Dependencies.txt -- 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 configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1313450/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313450] [NEW] Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default configuration
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 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 ** Affects: vsftpd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images trusty -- 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 configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1313450/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
