Announcement

Collapse
No announcement yet.

500 Internal Server Error after Empressa Upgrade

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

    500 Internal Server Error after Empressa Upgrade

    Tonight I attempted to upgrade my CentOS 6.1 server from Empressa V5.20 to v5.31
    using the Linux 64bit version (not GLIBC or FastCGI)

    I downloaded the 5.31 tar file directly to my server from a command line so that I didn't mess up the binaries.

    I reinstalled using the Standard Mode instructions exactly as I have done on my newer CentOS server.

    After triple-checking permissions, folder locations, etc, I get the following error in my suexec_log.

    "(2)No such file or directory: exec failed (mivavm)"

    Everything I read says to check permissions. Below are the current permissions for the relevant files.

    /cgi-bin/mivavm (0755)
    /cgi-bin/libmivaconfig.so (0755)
    /cgi-bin/mivavm.conf (0664)



    My .htacess looks like this

    AddType application/x-miva-compiled .mvc

    Action application/x-miva-compiled /cgi-bin/mivavm


    Any thoughts on what else I should look at?

    Thank you,
    Tim Mallardi



    #2
    The error tells me that some file can not be found. Check your mivavm.conf - are all the paths in it correct?
    William Gilligan - Orange Marmalade, Inc.
    www.OrangeMarmaladeinc.com

    Comment


      #3
      At this point you'll want 5.32; it's required for the latest version of Merchant. https://www.miva.com/support/downloads

      Generally for a standard mode install, just copying over the mivavm and libmivaconfig.so binaries (with the appropriate 3x.so or env.so), is all you'd need to do, then adjust the config for the new library directory wherever it has been extracted. Typically if you didn't cp -p, the two files would retain their previous permissions, which is desirable to keep things working.

      Were you able to simply put it back and it began working again?
      David Hubbard
      CIO
      Miva
      [email protected]
      http://www.miva.com

      Comment


        #4
        When running under suexec, file owner/group owner are also checked, as is the parent directory and its permissions (no group writable), so those are worth checking too.
        David Hubbard
        CIO
        Miva
        [email protected]
        http://www.miva.com

        Comment

        Working...
        X