Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-16281

TFTP Service not started automatically at boot

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Asterisk Configuration
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      13.18.1-1
    • Distro Version:
      PBX version 14.0.1.20
    • Distro:
      FreePBX Distro

      Description

      Hi,
      I upgraded my FreePBX server, a FreePBX 13 distro, asterisk 13 (latest) to FreePBX14, asterisk 13.18.1-1 using the upgrade script.
      The update was good but I saw that no phone can register/connect to the PBX.
      I started to debug the issue and I saw there is no listen on the port 69.
      Also, the tftp.service is not started.

      tftp.service - Tftp Server
      Loaded: loaded (/usr/lib/systemd/system/tftp.service; indirect; vendor preset: disabled)
      Active: inactive (dead)
      Docs: man:in.tftpd

      When I start it manually, it works but if I do:

      1. chkconfig --level 12 tftp on
        Note: Forwarding request to 'systemctl enable tftp.service'.

      then I reboot the server, the same issue happens:
      tftp.service - Tftp Server
      Loaded: loaded (/usr/lib/systemd/system/tftp.service; indirect; vendor preset: disabled)
      Active: inactive (dead)
      Docs: man:in.tftpd

      That explain why I decided to open a issues.
      If you need more info or you need testing, I am available since the server is not in production.
      Sincerely

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                boubou Sébastien Boulianne
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.