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

    Elastix 4 Database Driver Error for Endpoint Configuration

    Scheduled Pinned Locked Moved IT Discussion
    15 Posts 2 Posters 2.3k 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.
    • scottalanmillerS
      scottalanmiller
      last edited by

      Wonderful, if you Google this error, we are already the top hit for Elastix 4! Good for SEO, bad for finding the answer.

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

        Okay @lucale I'm grasping a bit here as I don't have a test system to work on, but...

        Start by trying this...

        yum install sqlite
        

        And let me know the output. My guess is that it is trying to use SQlite and that that is not installed.

        1 Reply Last reply Reply Quote 0
        • L
          lucale
          last edited by

          Thanks for your answer!

          let me tell you that after install about 3 or 4 times elastix using your instructions with some little modifications always endpoint has problems with the database, other times the problem was the username.

          Now, I change the username to connect to the database from asteriskuser to root in the file paloSantoEndpoints.class.php and get other error ERR: failed to get database credentials

          yum install sqlite
          Failed to set locale, defaulting to C
          Complementos cargados:fastestmirror
          Loading mirror speeds from cached hostfile

          • base: mirror.gtdinternet.com
          • commercial-addons: elastix.adaptixnetworks.com
          • elastix-base: elastix.adaptixnetworks.com
          • elastix-extras: elastix.adaptixnetworks.com
          • elastix-updates: elastix.adaptixnetworks.com
          • epel: epel.gtdinternet.com
          • extras: mirror.gtdinternet.com
          • updates: mirror.gtdinternet.com
            El paquete sqlite-3.7.17-8.el7.x86_64 ya se encuentra instalado con su versi?n m?s reciente
            Nada para hacer
          scottalanmillerS 1 Reply Last reply Reply Quote 1
          • scottalanmillerS
            scottalanmiller @lucale
            last edited by

            @lucale there is every possibility that the Endpoint Configuration simply does not work in Elastix 4. That's not a component that we often use and we migrated everything off of Elastix 4 because of its stability and support problems. But at this point, basically no one uses Elastix 4 so there just might not be people reporting issues with it 😞

            1 Reply Last reply Reply Quote 0
            • L
              lucale
              last edited by

              Problem SOLVED 🙂

              To fix this problem it's necessary add the user and password for the database in the file /etc/amportal.conf

              AMPDBUSER=asteriskuser
              AMPDBPASS=yourultrasecretpassword

              After that the endpoint will be fully functionally

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

                @lucale said in Elastix 4 Database Driver Error for Endpoint Configuration:

                Problem SOLVED 🙂

                To fix this problem it's necessary add the user and password for the database in the file /etc/amportal.conf

                AMPDBUSER=asteriskuser
                AMPDBPASS=yourultrasecretpassword

                After that the endpoint will be fully functionally

                So AMP was not working at all then? How did we get focused on the Endpoint Configuration manager? None of the interface should have been working if this was not done.

                I believe that the step to make this work is in the instructions as it is a known problem with Elastix. I thought that the fix for the main AMP database was built in.

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

                  Had you done this step after the initial build? Did you get the on console screen to set the AMP password?

                  systemctl enable mariadb.service
                  systemctl enable httpd.server
                  reboot
                  
                  L 1 Reply Last reply Reply Quote 0
                  • L
                    lucale @scottalanmiller
                    last edited by

                    @scottalanmiller Of course, I did.

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

                      @lucale said in Elastix 4 Database Driver Error for Endpoint Configuration:

                      @scottalanmiller Of course, I did.

                      And did the correct prompts come up, but just fail to set the database correctly?

                      L 1 Reply Last reply Reply Quote 0
                      • L
                        lucale @scottalanmiller
                        last edited by

                        @scottalanmiller Exactly, until now i have only problems with that database.

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

                          @lucale said in Elastix 4 Database Driver Error for Endpoint Configuration:

                          @scottalanmiller Exactly, until now i have only problems with that database.

                          Elastix has been having huge problems with their database stuff not being reliable in Elastix 4 across the board. But at least with the old builds, it was working after some standard modifications.

                          But I can't state enough that I would not keep using Elastix 4. They are just not able to support the product any longer. It's just too risky to use in production today.

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