ProFTP not starting correctly on boot

    • ProFTP not starting correctly on boot

      I am migrating my OMV2 installation to OMV3 and encountered 2 issues with ProFTPD.

      1. When i boot up proftpd fails to start as you can see in the following paste. When i turn it off and on again it then starts fine.

      Source Code

      1. Okt 18 10:33:08 debNAS systemd[1]: Starting LSB: Starts ProFTPD daemon...
      2. Okt 18 10:33:08 debNAS proftpd[831]: Starting ftp server: proftpd2017-10-18 10:33:08,892 debNAS proftpd[912]: warning: handling possibly truncated configuration data at line 10 of '/etc/proftpd/tls.conf'
      3. Okt 18 10:33:08 debNAS proftpd[831]: 2017-10-18 10:33:08,902 debNAS proftpd[912]: fatal: MasqueradeAddress: unable to resolve "xxx.xxx.xxx" on line 58 of '/etc/proftpd/proftpd.conf'
      4. Okt 18 10:33:08 debNAS systemd[1]: proftpd.service: control process exited, code=exited status=1
      5. Okt 18 10:33:08 debNAS systemd[1]: Failed to start LSB: Starts ProFTPD daemon.
      6. Okt 18 10:33:08 debNAS systemd[1]: Unit proftpd.service entered failed state.
      7. Okt 18 10:33:08 debNAS proftpd[831]: failed!

      ... where xxx.xxx.xxx is my dyndns address.

      2. It comes up with a warning about tls.conf. It seems to work fine so not sure where this warning comes from.

      Not sure if this helps for anything, but here is my tls.conf


      Source Code

      1. <IfModule mod_tls.c>
      2. TLSEngine on
      3. TLSLog /var/log/proftpd/tls.log
      4. TLSProtocol TLSv1.2
      5. TLSOptions NoCertRequest
      6. TLSRSACertificateFile /etc/ssl/certs/openmediavault-b2aab8c6-3840-48ce-9c2f-c3f220d7688a.crt
      7. TLSRSACertificateKeyFile /etc/ssl/private/openmediavault-b2aab8c6-3840-48ce-9c2f-c3f220d7688a.key
      8. TLSVerifyClient off
      9. TLSRenegotiate required off
      10. TLSRequired on
      11. </IfModule>
      Display All
    • Ok i just found out that i was right with my assumption to change boot order. Network has to be available before proftpd start, so it is able to resolve the dyndns host.

      Here is the solution: forums.proftpd.org/smf/index.php?topic=3747.0

      Unfortunately the solution does not seem to apply for OMV. How can i start proftpd service at a later point in boot process?

      I tried:

      Source Code

      1. update-rc.d -f proftpd remove
      2. update-rc.d proftpd defaults 06

      But proftpd always appears again as

      Source Code

      1. S02proftpd -> ../init.d/proftpd
      What am i doing wrong?

      The post was edited 1 time, last by monsen ().

    • monsen wrote:

      How can i start proftpd service at a later point in boot process?
      By modifying the respective systemd unit file and add there the needed dependencies. Since this might break with future package updates I would add to /etc/rc.local prior to the 'exit 0' line something like this:

      Source Code

      1. (sleep 10 && systemctl restart proftpd)
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • Users Online 1

      1 Guest