Public bug reported:
Binary package hint: vsftpd
On Lucid (this problem probably also exists in Karmic) vsftpd 2.2.2-3ubuntu5
fails to start automatically on boot when pasv_addr_resolve is used.
The reason for this is that vsftpd tries to resolve the domain name given in
this setting, but eth0 is not yet up at the time vsftpd is called by upstart.
The result in syslog:
[...]
Apr 15 10:36:30 desktop init: vsftpd main process (986) terminated with status 1
Apr 15 10:36:30 desktop init: vsftpd main process ended, respawning
Apr 15 10:36:30 desktop init: vsftpd main process (989) terminated with status 1
Apr 15 10:36:30 desktop init: vsftpd main process ended, respawning
Apr 15 10:36:30 desktop init: vsftpd main process (992) terminated with status 1
Apr 15 10:36:30 desktop init: vsftpd main process ended, respawning
Apr 15 10:36:30 desktop init: vsftpd main process (995) terminated with status 1
Apr 15 10:36:30 desktop init: vsftpd respawning too fast, stopped
Both; not using pasv_addr_resolve or waiting till eth0 is up fixes the problem.
I fixed this by adding IFACE=eth0 to the start conditions in
/etc/init/vsftpd.conf, but this assumes eth0 is your default network interface.
This bug is probably related to #277114
** Affects: vsftpd (Ubuntu)
Importance: Undecided
Status: New
--
vsftpd fails to start on boot when using pasv_addr_resolve
https://bugs.launchpad.net/bugs/563973
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in ubuntu.
--
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
