We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Error 500 - Internal server error when upgrading from SVN

    • 5340
    • 1,624 Posts
    cipa Reply #1, 14 years, 7 months ago
    Hi I just installed Revo Beta and after the SVN update I get

    Error 500 - Internal server error

    An internal server error has occured!
    Please try again later.

    at this page http://hostabc.com/revo/setup/index.php?action=install


    Any ideas if this related to the memory. This is a regular host.
    Should I increase the memory from .htaccess

    Thank You

    PS: I followed the instruction in here
      Responsive CSS Grid: cipalabs.com/projects/metal/
      Blog: MODX Tutorials & Articles
    • opengeek Reply #2, 14 years, 7 months ago
      Quote from: cipa at Sep 23, 2009, 11:04 PM

      This is a regular host.
      You’ll have to be more specific. PHP version, MySQL server and client versions, etc.
        Jason Coward
        Chief Architect @ MODX
        http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
        • 5340
        • 1,624 Posts
        cipa Reply #3, 14 years, 7 months ago
        Off course

        PHP Version 5.2.11
        memory_limit 40M

        From control panel - MySQL5.0
        From Php Info - Client API version 5.0.67


        What I can say is the default download worked perfect. Only when updating from SVN I got this


        Edit: It seems that something was done. I can see the tabs on the left side which were not present before.
        There is a problem with the first tab. Please see the image

          Responsive CSS Grid: cipalabs.com/projects/metal/
          Blog: MODX Tutorials & Articles
          • 28215
          • 4,149 Posts
          splittingred Reply #4, 14 years, 7 months ago
          Quote from: cipa at Sep 24, 2009, 02:17 AM

          Edit: It seems that something was done. I can see the tabs on the left side which were not present before.
          There is a problem with the first tab. Please see the image
          That seems like your lexicons didnt load fully. Try these things:

          1. Go to Lexicon Management, and click on the bottom of the grid the button "Reload Core Lexicons from Base" (or something like that).
          2. Clear the cache.

          If that doesn’t work:
          3. Run the transport build and setup again.
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 5340
            • 1,624 Posts
            cipa Reply #5, 14 years, 7 months ago
            I’ll try to reupload the files first and if I get the same error I will try your solution.

            Thx
              Responsive CSS Grid: cipalabs.com/projects/metal/
              Blog: MODX Tutorials & Articles
              • 5340
              • 1,624 Posts
              cipa Reply #6, 14 years, 7 months ago
              I just replaced all the files again and I have the same problem
              At the last step of the setup I get the above mentioned error message.

              After running the Lexicon update the issue in the image was fixed. Thx splittingred

              Just after running the lexion update I tried to clear the cache but nothing happen. Just the "Console Running". After playing around some more I tried it again and it work instantly.

              Is there an error log I can check. I tried the one on the server but nothing interesting.


              Edit: I found the error log in modx unfortunately is to big to post so I’m just gonna post the end

              Note: The file is to big to be copy/pasted from the browser. Firefox crashed 2 times when I tried to select all(command A)

              [2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'email',`value` = 'Email',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 325 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 325 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => 5b5b83b2144bb02cd6da4d393dc8aeba
    [native_key] => 325
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":325,"name":"email","value":"Email","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => c7b0af7927e941128edf4cb370715331
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'empty_recycle_bin',`value` = 'Purge deleted documents',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 326 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 326 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => 8e7177f6f9d48486ee5d870bfbdb9c8c
    [native_key] => 326
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":326,"name":"empty_recycle_bin","value":"Purge deleted documents","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => 12f2cbb8a3b3dee8126bce897518b6d6
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'empty_recycle_bin_empty',`value` = 'There are no deleted documents to purge.',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 327 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 327 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => 4fa6b9027cee9138dd35ba4d2319c480
    [native_key] => 327
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":327,"name":"empty_recycle_bin_empty","value":"There are no deleted documents to purge.","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => a2b31804d9700c0d4ad5d3241486212f
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'enabled',`value` = 'Enabled',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 328 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 328 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => d9d0ec6d9859cd14a8daafaff1fe71ab
    [native_key] => 328
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":328,"name":"enabled","value":"Enabled","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => 0f5fe71afeba856b82965de752b1ad8d
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'err_self_parent',`value` = 'Cannot make something its own parent!',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 329 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 329 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => 31b71628f3f5cda43ce076714b158046
    [native_key] => 329
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":329,"name":"err_self_parent","value":"Cannot make something its own parent!","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => 365943542e3abf33df5a8b1738ffafac
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'error',`value` = 'Error',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 330 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 330 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => fcb05e56a8dc6a1a8e52d6253fb62785
    [native_key] => 330
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":330,"name":"error","value":"Error","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => fd9d801e79efc264aee38833ce92d33b
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'error_sending_email',`value` = 'Error sending email',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 331 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 331 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => 962bfb9c7f1b95413e0e8cfb4df07aac
    [native_key] => 331
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":331,"name":"error_sending_email","value":"Error sending email","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => 357b61f47fa72be50e8408742e957c40
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'error_sending_email_to',`value` = 'Error while sending mail to ',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 332 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 332 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => 8341058eccb41a1370e9bcc5947f70d2
    [native_key] => 332
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":332,"name":"error_sending_email_to","value":"Error while sending mail to ","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => 8373c50f84e6c13ed44f90f5d07a6aa3
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error SQLER executing statement:
UPDATE `modx_lexicon_entries` SET `name` = 'event_id',`value` = 'Event Id',`topic` = 10,`namespace` = 'core',`language` = 'en',`createdon` =  WHERE `id` = 333 LIMIT 1
Array
(
    [0] => SQLER
    [1] => 1064
    [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id` = 333 LIMIT 1' at line 1
)

[2009-09-23 22:05:03] (ERROR @ /x649/setup/index.php) Error saving vehicle object: Array
(
    [resolve_files] => 0
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modLexiconEntry
    [guid] => f8b6c7b001744073c1f762de0c290438
    [native_key] => 333
    [filename] => modLexiconTopic/8a8c93828e5a50279a60ee70cd4238ec.vehicle
    [preserve_keys] => 
    [update_object] => 1
    [unique_key] => Array
        (
            [0] => name
            [1] => topic
            [2] => language
        )

    [object] => {"id":333,"name":"event_id","value":"Event Id","topic":10,"namespace":"core","language":"en","createdon":null,"editedon":null}
    [signature] => 28bfde90496b155bf876152c25d312b2
)

[2009-09-23 23:36:47] (ERROR @ /x649/setup/index.php) Error saving changes to parent object fk field action
[2009-09-23 23:36:47] (ERROR @ /x649/setup/index.php) Error saving changes to parent object fk field action
[2009-09-23 23:36:47] (ERROR @ /x649/setup/index.php) Error saving changes to parent object fk field action
[2009-09-23 23:36:47] (ERROR @ /x649/setup/index.php) Error saving changes to parent object fk field action
[2009-09-23 23:36:47] (ERROR @ /x649/setup/index.php) Error saving changes to parent object fk field action
[2009-09-23 23:36:47] (ERROR @ /x649/setup/index.php) Error saving changes to parent object fk field action
[2009-09-23 23:36:47] (ERROR @ /x649/setup/index.php) Error saving changes to parent object fk field action
[2009-09-23 23:36:47] (ERROR @ /x649/setup/index.php) Error saving changes to parent object fk field action
                Responsive CSS Grid: cipalabs.com/projects/metal/
                Blog: MODX Tutorials & Articles
                • 3749
                • 24,544 Posts
                BobRay Reply #7, 14 years, 7 months ago
                Quote from: cipa at Sep 24, 2009, 03:53 AM

                I just replaced all the files again and I have the same problem
                At the last step of the setup I get the above mentioned error message.

                After running the Lexicon update the issue in the image was fixed. Thx splittingred

                Just after running the lexion update I tried to clear the cache but nothing happen. Just the "Console Running". After playing around some more I tried it again and it work instantly.

                Is there an error log I can check. I tried the one on the server but nothing interesting.


                I would try upping the memory_limit to at least 64M (if not 128M) for the setup.
                  Did I help you? Buy me a beer
                  Get my Book: MODX:The Official Guide
                  MODX info for everyone: http://bobsguides.com/modx.html
                  My MODX Extras
                  Bob's Guides is now hosted at A2 MODX Hosting
                  • 5340
                  • 1,624 Posts
                  cipa Reply #8, 14 years, 7 months ago
                  I’ll try that Bob.

                  But from the log I posted above there is a problem with the sql near createdon.

                  I’ll try to find a solution to increase the memory from the .htaccess file.
                    Responsive CSS Grid: cipalabs.com/projects/metal/
                    Blog: MODX Tutorials & Articles
                    • 5340
                    • 1,624 Posts
                    cipa Reply #9, 14 years, 7 months ago
                    it seems that php_value memory_limit 128M in .htaccess throws the same error as mentioned above.

                    Any other ways I can increase the memory. Remember that I’m on a host.


                    I also modified the setup/index.php file with ini_set(’memory_limit’, ’128M’). Made no difference.



                      Responsive CSS Grid: cipalabs.com/projects/metal/
                      Blog: MODX Tutorials & Articles
                      • 3749
                      • 24,544 Posts
                      BobRay Reply #10, 14 years, 7 months ago
                      Quote from: cipa at Sep 24, 2009, 04:28 AM

                      it seems that php_value memory_limit 128M in .htaccess throws the same error as mentioned above.

                      Any other ways I can increase the memory. Remember that I’m on a host.

                      I also modified the setup/index.php file with ini_set(’memory_limit’, ’128M’). Made no difference.
                      You can try putting this in a php.ini file:

                      memory_limit = 128M


                      If the host is running suPHP, you’ll have to put something like this in the public_html .htaccess file to tell suPHP where the php.ini file is:

                      suPHP_ConfigPath /home/user/public_html/modx


                      If that doesn’t work, you’d have to ask the host to up the memory_limit.

                      Running short of memory during the install can cause a wide variety of problems.
                        Did I help you? Buy me a beer
                        Get my Book: MODX:The Official Guide
                        MODX info for everyone: http://bobsguides.com/modx.html
                        My MODX Extras
                        Bob's Guides is now hosted at A2 MODX Hosting