[Bug 868885] Re: Ubuntu natty Proftpd start fails at boot time when using MasqueradeAddress and Network-manager

[Amr Ibrahim]

In the future, please use 'ubuntu-bug package-name' to report Ubuntu bugs.
https://help.ubuntu.com/community/ReportingBugs

You have reported a bug in a non-existent package in Ubuntu archives
since 2007. No developer will see this bug report because simply the
package does not exist any more.

** Package changed: proftpd (Ubuntu) => proftpd-dfsg (Ubuntu)

-- 
You received this bug notification because you are a member of ProFTPD
Maintainance Team, which is subscribed to proftpd-dfsg in Ubuntu.
https://bugs.launchpad.net/bugs/868885

Title:
  Ubuntu natty Proftpd start fails at boot time when using
  MasqueradeAddress and Network-manager

Status in proftpd-dfsg package in Ubuntu:
  Confirmed

Bug description:
  Since latest kernel upgrade off ubuntu natty 11.04. proftpd start at boot failed with message : - Fatal: MasqueradeAddress: unable to resolve "xxxxxxx.xxx.cx" on line 177 of '/etc/proftpd/proftpd.conf'. I'm using a relatively avanced proftpd config. With first just standalone base server on standard port for local network only and a virtual with tls (ftps) user apart who is jailed to certain maps and limited in possible ftpd commands. Accessible trough internet. Masquerading is necessary to have the passive ports opened to corect ip  by the client. 
  I use network-manager to configure the interface. (it's easy with the applet to see your network status) . 
  When configure the proftpd without MasqueradeAddress it does start fine. 
  This all occur on my latest pc with intel core duo E8600 2 X 3,33 Ghz, and raptor hd's. 
  On my older pc amd64 athlon x2 dual core standard hd's with same ubuntu natty same configuration no problem. proftpd start always at boot time.
  I figured out that with a fast pc proftpd starts whiles the network is not fully up when working trough network manager. Which causes a start failure as it cannot resolve the MasqueradeAddress yet.
  I tried to give it the highest possible start number into runlevel 2,3,4,5 . But still the same problem. When I configured my network adapter trough /network/interfaces  no problem proftpd started well.(But I like to have the network status with the nm-applet) With inetd also no problem but I do not want a pid for each session. 

  I do now found out a solution (that's why a fill a bug repport it would be nice to include this into further ubuntu versions)
  I first removed the standard upstart with update-rc.d -f proftpd remove.
  Created an upstart conf into /etc/init

  named proftpd.conf

  # Proftpd 
  #Use this instead of standard(old) rc.d When using network manager
  #and dns masquer address Otherwise proftp start may fail due to no dns lookup avbl yet
  #during boottime. With this proftpd will only start when network device is up 
  # 

  description     "proftpd"

  start on (local-filesystems and net-device-up IFACE!=lo)
            
  stop on stopping dbus

  exec /etc/init.d/proftpd start

  Now proftpd does start fine again at boot time. And is also avbl
  without local login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/868885/+subscriptions