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

    Sangoma 6 to 7 Upgrade Tool Error

    Scheduled Pinned Locked Moved IT Discussion
    10 Posts 4 Posters 1.0k 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.
    • A
      Alex Sage
      last edited by Alex Sage

      Any ideas?

      [root@localhost ~]# distro-upgrade
      ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
      ┃                                            ┃
      ┃        Sangoma 6 to 7 Upgrade Tool         ┃
      ┃                                            ┃
      ┃    Distro Upgrade - Version 1802-2.sng7    ┃
      ┃    Build Date: 2018-02-14                  ┃
      ┃                                            ┃
      ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
      
       Checking prerequsites...
              Checking FreePBX Version        [ ✔ ] - 13.0.194.2
              Checking bitsize of machine     [ ✔ ] - x86_64
              Checking for 32 bit packages    [ ✔ ] - No i686 rpms found
              Checking available disk space   [ ✔ ] - 81G Available
              Checking for IonCube Loader     [ ✔ ] - IonCube Loader not detected
              Checking for outdated system    [ ✔ ] - No pending updates.
              Checking for HA Setup           [ ✔ ] - Not a HA system
       All prerequsites passed!
      
      Are you ready to upgrade your machine to SNG7? This process requires
      two reboots, and will download approximately 400mb of files before
      starting. There will be no interruption to service until this machine
      is rebooted.
      
      Download files required for upgrade [Yn]? y
      ######### Starting setup upgrade on Thu Mar  8 17:32:31 EST 2018 #########
      ######### An error occured, please check /var/log/sngupdate #########
      Error! setup_upgrade did not exit cleanly. Not enabling upgrade service
      
      [root@localhost ~]# cat /var/log/sngupdate
      ######### Starting setup upgrade on Thu Mar  8 17:32:31 EST 2018 #########
      ######### An error occured, please check /var/log/sngupdate #########
      [root@localhost ~]#
      
      wirestyle22W JaredBuschJ 2 Replies Last reply Reply Quote 0
      • wirestyle22W
        wirestyle22 @Alex Sage
        last edited by wirestyle22

        @aaronstuder said in Sangoma 6 to 7 Upgrade Tool Error:

        /var/log/sngupdate

        So the log it refers you to just says a generic error occurred? Ugh

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

          That’s a low volume upgrade, bound to be a lot of snags 😞

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

            In other news, this is why I prefer Fedora over CentOS.

            1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @Alex Sage
              last edited by

              @aaronstuder said in Sangoma 6 to 7 Upgrade Tool Error:

              Any ideas?

              [root@localhost ~]# distro-upgrade
              ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
              ┃                                            ┃
              ┃        Sangoma 6 to 7 Upgrade Tool         ┃
              ┃                                            ┃
              ┃    Distro Upgrade - Version 1802-2.sng7    ┃
              ┃    Build Date: 2018-02-14                  ┃
              ┃                                            ┃
              ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
              
               Checking prerequsites...
                      Checking FreePBX Version        [ ✔ ] - 13.0.194.2
                      Checking bitsize of machine     [ ✔ ] - x86_64
                      Checking for 32 bit packages    [ ✔ ] - No i686 rpms found
                      Checking available disk space   [ ✔ ] - 81G Available
                      Checking for IonCube Loader     [ ✔ ] - IonCube Loader not detected
                      Checking for outdated system    [ ✔ ] - No pending updates.
                      Checking for HA Setup           [ ✔ ] - Not a HA system
               All prerequsites passed!
              
              Are you ready to upgrade your machine to SNG7? This process requires
              two reboots, and will download approximately 400mb of files before
              starting. There will be no interruption to service until this machine
              is rebooted.
              
              Download files required for upgrade [Yn]? y
              ######### Starting setup upgrade on Thu Mar  8 17:32:31 EST 2018 #########
              ######### An error occured, please check /var/log/sngupdate #########
              Error! setup_upgrade did not exit cleanly. Not enabling upgrade service
              
              [root@localhost ~]# cat /var/log/sngupdate
              ######### Starting setup upgrade on Thu Mar  8 17:32:31 EST 2018 #########
              ######### An error occured, please check /var/log/sngupdate #########
              [root@localhost ~]#
              

              Hahahahhaahahahah

              1 Reply Last reply Reply Quote 1
              • JaredBuschJ
                JaredBusch
                last edited by

                No clue where to go with no good error log.

                1 Reply Last reply Reply Quote 2
                • A
                  Alex Sage
                  last edited by

                  Guess I am just going to build a new 14 VM and transfer over the config. Any thing to watch for?

                  JaredBuschJ 1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch @Alex Sage
                    last edited by

                    @aaronstuder said in Sangoma 6 to 7 Upgrade Tool Error:

                    Guess I am just going to build a new 14 VM and transfer over the config. Any thing to watch for?

                    You can export and import some things with the default handlers.

                    If you are using SSL from LE and have the Yelaink T4xG series phones they won't talk right using SSL.
                    If this is the same system I worked on, don't forget to grab crontab with the bell schedule.

                    A 1 Reply Last reply Reply Quote 1
                    • A
                      Alex Sage @JaredBusch
                      last edited by

                      @jaredbusch said in Sangoma 6 to 7 Upgrade Tool Error:

                      @aaronstuder said in Sangoma 6 to 7 Upgrade Tool Error:

                      Guess I am just going to build a new 14 VM and transfer over the config. Any thing to watch for?

                      You can export and import some things with the default handlers.

                      If you are using SSL from LE and have the Yelaink T4xG series phones they won't talk right using SSL.
                      If this is the same system I worked on, don't forget to grab crontab with the bell schedule.

                      It is in fact the same system. Will the custom extensions come over?

                      JaredBuschJ 1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch @Alex Sage
                        last edited by

                        @aaronstuder said in Sangoma 6 to 7 Upgrade Tool Error:

                        @jaredbusch said in Sangoma 6 to 7 Upgrade Tool Error:

                        @aaronstuder said in Sangoma 6 to 7 Upgrade Tool Error:

                        Guess I am just going to build a new 14 VM and transfer over the config. Any thing to watch for?

                        You can export and import some things with the default handlers.

                        If you are using SSL from LE and have the Yelaink T4xG series phones they won't talk right using SSL.
                        If this is the same system I worked on, don't forget to grab crontab with the bell schedule.

                        It is in fact the same system. Will the custom extensions come over?

                        Yes. they are still extensions.

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