Announcement

Collapse
No announcement yet.

Can not update Miva Merchant to

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Can not update Miva Merchant to

    I am trying to update Miva 99.14.00 to Miva 10. I have posted screenshots of errors and of my configuration as well as some support questioned asked to me and how I responded. Please refer to these these screenshots for errors I am receiving:

    Miva Update Error: miva-error.JPG

    Miva Error after upgrading Empresa: error.JPG

    The buitins upgrade is no different than past builtin updates and I find it much easier to just replace the folders rather than changing the paths. If you're getting an error when doing that than you 'll want to take a closer look at the files/folder you used.

    I downloaded the zip file for CentOS 7 (image file 'download_link.JPG'), should I use a different one for Debian 9?

    I then extracted and placed in a folder named 'mivavm-v5.34' along side the current running folder that has 'mivavm-v5.33'.

    There is a symlink named 'mivavm' that is currently linked to 5.33. I linked it to 5.34. (please refer 'old-symlink.JPG' and 'new-symlink.JPG')


    Did you replace the env.so/libmivaconfig.so and the mivavm binary?

    I have done a similar situation with the binary and env.so/libmivaconfig.so. I put the new cgi-bin/mivavm-v5.34 and env.so in the directory the apache configuration looks at and change respective symlinks to the new files.

    I needed to rename env.so to libmivaconfig.so, correct?

    (reference picture 'bin_config.JPG')

    Did you add the BZ2 library config?

    I have BZip2 installed but I do not know its directory path or apache configuration variable name. I'm assuming it would be something like this but I do not know the exact syntax:

    SetEnv HTTP_MvCONFIG_BZ2_DIR {PATH_TO_BZIP2}

    #2
    I'd start by loading the diagtool.mvc that comes with the Empresa distribution and see if it mentions any specific library load failures or other errors related to mivadata and script directories, etc.
    David Hubbard
    CIO
    Miva
    [email protected]
    http://www.miva.com

    Comment


      #3
      You're most likely missing the MYSQLCLIENT system library definition in your mivavm.conf file. View your store at runtime, I believe the error may be different.
      David Carver
      Miva, Inc. | Software Developer

      Comment


        #4
        I see no errors in the Miva diagtool.mvc for data directory or script directory. I have attached screenshots of the results.

        https://drive.google.com/file/d/13oF...ew?usp=sharing

        https://drive.google.com/file/d/1roc...ew?usp=sharing

        https://drive.google.com/file/d/1JKc...ew?usp=sharing

        https://drive.google.com/file/d/1153...ew?usp=sharing

        Comment


          #5
          You're missing the MYSQLCLIENT system library. In your final screen shot only the GD system library is registered. You need to add the MYSQLCLIENT system library to your Miva configuration.
          David Carver
          Miva, Inc. | Software Developer

          Comment


            #6
            Thank you dcarver for the prompt response and addition information.

            We have most of our configuration done in the apache configuration file.
            https://drive.google.com/file/d/13XU...ew?usp=sharing

            This is our mivavm.conf file:
            https://drive.google.com/file/d/1UTr...ew?usp=sharing

            Would we put this in the mivavm file or the apache file? Also, what would be the path we provide this with? Would it be something I would need to install?

            Comment


              #7
              Which configuration are you actually using? One is the 3x configuration while the other is the ENV configuration. Basically you need to either add "SetEnv HTTP_MvCONFIG_SYSTELLIB_MYSQLCLIENT /path/to/mysqlclient.so" to your ENV configuration or you need to add "<SYSTEM-LIB CODE="MYSQLCLIENT" LIBRARY="/path/to/mysqlclient.so"> to your 3x configuration. You can get the shared libraries either from the MySQL website or you could do "yum install mariadb-libs" depending on the OS you're running. The best way is probably to install it through your package manager, either yum, apt, etc...
              David Carver
              Miva, Inc. | Software Developer

              Comment


                #8
                Thanks for the suggestions David. I went ahead and found the mysqlclient.so, it was located in /usr/lib/x86_64-linux-gnu/libmysqlclient.so. Does this seem like the correct one to you?

                I put it first in the apache ENV file, and it didn't work and I put it in the mivavm.conf files, it still didn't seem to work. I checked the diagtool, and it wasn't showing up. I checked Miva admin and the error is still there when trying to update.

                mivavm.conf:
                https://drive.google.com/file/d/1H8W...ew?usp=sharing

                ENV conf:
                https://drive.google.com/file/d/1yyC...ew?usp=sharing

                diagtool:
                https://drive.google.com/file/d/1rwU...ew?usp=sharing

                Comment


                  #9
                  I'm guessing you're using the ENV library in that case and you probably need to restart Apache. Either that or you're editing the wrong mivavm.conf file, but I'm pretty sure you just need to restart Apache.
                  David Carver
                  Miva, Inc. | Software Developer

                  Comment


                    #10
                    I'm sorry, I forgot to mention that I restarted Apache. Every time I modify Apache conf files, I restart it using the command: service apache2 restart

                    Comment


                      #11
                      What does diagtool report for system variable "mvconfig_library?" That way we know exactly which configuration we should be focusing on.
                      David Carver
                      Miva, Inc. | Software Developer

                      Comment


                        #12
                        I am sorry once again, I seemed to have overlooked something. I had the 5.33 files in use with the 5.34 binary. I changed the files to the 5.34:

                        https://drive.google.com/file/d/1-PO...ew?usp=sharing

                        But this caused the following error when trying to reach the Miva admin:

                        https://drive.google.com/file/d/16Eb...ew?usp=sharing

                        The diagtool did not show anything different from what I could tell. If there is something specific you would like to see from it, let me know and I can snip it for you.

                        Comment


                          #13
                          There error is because the MYSQLCLIENT system library is not configured. Go to diagtool, System Variables, and see what value you have for "s.mvconfig_library".
                          David Carver
                          Miva, Inc. | Software Developer

                          Comment


                            #14
                            This is what system variable shows. I do not see "s.mvconfig_library":
                            https://drive.google.com/file/d/1aoU...ew?usp=sharing

                            Comment


                              #15
                              There must be another mivavm.conf file somewhere that needs to be edited or something like that. If I add an invalid system library to my configuration it still shows up under "Installed System Libraries" in diagtool, but it just says it can't be loaded. MYSQLCLIENT isn't even showing up for you which is suspect.
                              David Carver
                              Miva, Inc. | Software Developer

                              Comment

                              Working...
                              X