ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    FreePBX 14 Fails with Update to Asterisk 16

    Scheduled Pinned Locked Moved IT Discussion
    freepbxpbxvoiptelephonyasteriskfreepbx 14asterisk 16
    14 Posts 4 Posters 2.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch @scottalanmiller
      last edited by

      @scottalanmiller said in FreePBX 14 Fails with Update to Asterisk 16:

      Attempting to update FreePBX 14 to Asterisk 16. But when we do the update, we get this error and Asterisk cannot run.

      Reloading FreePBX
      Error(s) have occured, the following is the retrieve_conf output:
      exit: 1
      

      Currently running 15.7.2 since 16 did not work. FreePBX and the OS are fully up to date otherwise.

      How are you doing it? I've never had it fail using the built in version switch script.

      asterisk-version-switch
      

      Also, Asterisk 15.7.2 has a memory leak. I had to revert systems to 15.5.0.

      a9c95dc7-c9fc-406b-a350-13c1e32bd599-image.png

      scottalanmillerS 1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @JaredBusch
        last edited by

        @JaredBusch yeah, using the switch is how it failed.

        1 Reply Last reply Reply Quote 0
        • CCWTechC
          CCWTech
          last edited by

          Mine did that as well. I did this:

          Try from SSH

          fwconsole ma upgradeall
          fwconsole reload

          And it resolved it.

          As per https://community.freepbx.org/t/rconffail-retrieve-conf-failed-config-not-applied/47699

          JaredBuschJ scottalanmillerS 2 Replies Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch @CCWTech
            last edited by

            @CCWTech said in FreePBX 14 Fails with Update to Asterisk 16:

            Mine did that as well. I did this:

            Try from SSH

            fwconsole ma upgradeall
            fwconsole reload

            And it resolved it.

            As per https://community.freepbx.org/t/rconffail-retrieve-conf-failed-config-not-applied/47699

            That has nothing to do with switching Asterisk versions.

            CCWTechC 1 Reply Last reply Reply Quote 0
            • CCWTechC
              CCWTech @JaredBusch
              last edited by

              @JaredBusch said in FreePBX 14 Fails with Update to Asterisk 16:

              @CCWTech said in FreePBX 14 Fails with Update to Asterisk 16:

              Mine did that as well. I did this:

              Try from SSH

              fwconsole ma upgradeall
              fwconsole reload

              And it resolved it.

              As per https://community.freepbx.org/t/rconffail-retrieve-conf-failed-config-not-applied/47699

              That has nothing to do with switching Asterisk versions.

              Just reporting what worked for me.

              1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller
                last edited by

                Customer system went to Asterisk 16 with no issues.

                1 Reply Last reply Reply Quote 1
                • B
                  bnrstnr
                  last edited by

                  The FreePBX installer still recommends Asterisk 13, do you guys always run the current version?

                  scottalanmillerS 1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller @bnrstnr
                    last edited by

                    @bnrstnr said in FreePBX 14 Fails with Update to Asterisk 16:

                    The FreePBX installer still recommends Asterisk 13, do you guys always run the current version?

                    More or less, yeah. I've found 13 to be a poor choice, 15 worked a bit better. Now that 16 is out, seems like the way to go. It's an LTS release, so while I'm not big on sticking to LTS releases, they are definitely the best option when they are both LTS and current at the same time.

                    1 Reply Last reply Reply Quote 0
                    • B
                      bnrstnr
                      last edited by

                      Not to hijack this thread, but is there a specific upgrade path to get from 13 to 16? Do I need to hit all releases between?

                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @bnrstnr
                        last edited by

                        @bnrstnr said in FreePBX 14 Fails with Update to Asterisk 16:

                        Not to hijack this thread, but is there a specific upgrade path to get from 13 to 16? Do I need to hit all releases between?

                        No need to go step by step. At least not normally. Just issue the switch command and pick the version that you want to go to. You can go up or down at will.

                        1 Reply Last reply Reply Quote 2
                        • scottalanmillerS
                          scottalanmiller @CCWTech
                          last edited by

                          @CCWTech said in FreePBX 14 Fails with Update to Asterisk 16:

                          Mine did that as well. I did this:
                          Try from SSH
                          fwconsole ma upgradeall
                          fwconsole reload
                          And it resolved it.

                          Did that, but no change. Same error.

                          1 Reply Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller
                            last edited by

                            Gives this error as well:

                            fclose(): 111 is not a valid stream resource
                            
                            1 Reply Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller
                              last edited by

                              Okay, we got it. Doing the switch, then the fwconsole update, then rebooting, and running through it all again... eventually it fixed itself.

                              1 Reply Last reply Reply Quote 0
                              • 1 / 1
                              • First post
                                Last post