We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27210
    • 158 Posts
    Revo 2.0.8

    Happened at least twice.

    Manager is sitting with a Resource open. Try to log out of Manager, click logout, then yes to are you sure, nothing happens. Give up and close tab. Now i’m screwed.

    Can’t log back into Manager. Try to copy over all files from clean installation, clear my browser cache and do an upgrade which gives warning to make sure everyone is logged off, which i couldn’t do per above. Installation hangs with blank screen.

    The only solution i have found is to delete the database, do a new install and then restore the database.

    March 9 - happened again around 2:40 pm EST - here is the link to the cache logs but nothing was wrong at the exact time of the failure - does this log look correct? http://www.seaville-suzuki.com/temp/error.log

      • 27210
      • 158 Posts
      Here’s the latest occurrence @ around 1:00 pm est on 3/11/11

      • Environment:
      o XAMPP for Windows Version 1.7.3
      o Windows 7
      o MySql
       Server: localhost via TCP/IP
       Server version: 5.1.41
       Protocol version: 10
       User: root@localhost
       MySQL charset: UTF-8 Unicode (utf8)
      o Web Server
       Apache/2.2.14 (Win32) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l mod_autoindex_color PHP/5.3.1 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1
       MySQL client version: 5.1.41

      Failure Scenario - this is all i did:
      • Login to Manager
      • Open a chunk
      • Copy new data into the chunk
      • Hit Save (I have the Save and Continue choice selected) - Didn’t notice if the Save Successful message came up
      • Click on Resources tab and the Manager is hung with one of these as the URL http://localhost/modx/seaville/manager/index.php?a=10&id=3 or http://localhost/modx/seaville/manager/index.php?a=1
      • This URL http://localhost/modx/seaville/manager/ shows a blank screen
      • No entries for this time period in the core/cache/logs/error.log

      Edited to add:
      Compared Manager folders from clean install and crashed install, only difference was config.core.php which was correct.

      Edited to add:
      crashed site index.php was different - here is a link to the "bad" manager/index.php - http://www.seaville-suzuki.com/temp/index-bad.php

      What’s weird is that the index-bad.php file above seems to run remotely but not locally - i have a lot to learn - now on to debug php code?

      Edited to add:
      in the Manager/index.php the following statement is the one that the script hangs on:
      $modx->initialize(’mgr’);

      Edited to add:
      I found a workaround for the problem but not what caused the problem.
      I renamed the following 2 files and then i was able to login again
      - core/cache/mgr/context.cache.php
      - core/cache/mgr/actions.cache.php

      Edited to add:
      - happened again on 3/12/11
      - here are links to the two files i had to erase (originally they had an extension of php. I changed the extension to txt.
      - http://www.seaville-suzuki.com/temp/context.cache.txt
      - http://www.seaville-suzuki.com/temp/actions.cache.txt

      Edited to add:
      - failed again on 3/13/11 - multiple times when creating template variables - error log shows this error: C:\xampp\htdocs\modx\seaville\manager\index-test.php:29)
      [2011-03-13 19:13:42] (ERROR @ /modx/seaville/connectors/element/tv.php) modTemplateVarTemplate: Attempt to set NOT NULL field rank to NULL
      - this time erasing the two above files didn’t fix the problem. I erased all of the subdirectories under core/cache except the logs subdirectory and i’m getting a warning "Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at C:\xampp\htdocs\modx\seaville\manager\index-test.php:29) in C:\xampp\htdocs\modx\seaville\core\model\modx\modx.class.php on line 2846
      - posted the latest error log here: http://www.seaville-suzuki.com/temp/error.log
      - i could really use some help
        • 18373 ☆ A M B ☆
        • 3,141 Posts
        It seemed to have trouble running the installer properly, failing to set up critical database tables.


        It’s also had trouble caching, you may want to check the permissions of the core/cache folder and all its subfolders. Try removing all of it and setting the main core/cache folder with plenty of write permissions.

        If that doesn’t fix anything yet, please completely delete the MODX installation and re-install with a clean slate. Check permissions closely, and make sure the down- and upload of the files went as expected... Anything in the error.log means something went wrong, so keep an eye on that too.
          Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

          Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
          • 27210
          • 158 Posts
          Mark,

          I am pretty sure it is not an installation problem. I have compared folders from a clean install to my failed install.

          The workaround is to delete all of the files / folders under the core/cache/ directory.

          Then after a time the problem happens again, always when switching from one type of "resource" to another (css file to Resource, Chunk to Resource, or tv to tv sometimes which is the exception.

          Since changes were made in the cache area in 2.0.8, my money is on a still existing problem there.

          Edited to add:
          Except for the tv case which happens in real time, often the manager has been sitting with a file open for some time. Is there some sort of timeout involved that could screw up the cache?
            • 27210
            • 158 Posts
            latest errors from last 4 failures : [2011-03-14 19:14:00] (ERROR @ /modx/seaville/connectors/element/tv.php) modTemplateVarTemplate: Attempt to set NOT NULL field rank to NULL
            [2011-03-14 19:53:00] (ERROR @ /modx/seaville/connectors/element/tv.php) modTemplateVarTemplate: Attempt to set NOT NULL field rank to NULL
            [2011-03-14 19:53:52] (ERROR @ /modx/seaville/index.php) Error caching script elements/modplugin/1
            [2011-03-15 12:41:04] (ERROR @ /modx/seaville/index.php) Error caching resource 1
            [2011-03-15 15:54:47] (ERROR @ /modx/seaville/connectors/resource/index.php) Error caching lexicon topic lexicon/en/core/resource


            I can’t believe i’m the only one having this problem.

            I have to erase all of the files under the core/cache directory - happens 4 times in last 2 days
              • 18373 ☆ A M B ☆
              • 3,141 Posts
              What is the plugin with ID 1 in your installation?
                Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

                Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
                • 3749
                • 24,544 Posts
                Quote from: Mark at Mar 15, 2011, 06:44 PM

                What is the plugin with ID 1 in your installation?

                My money is on TinyMCE. wink
                  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
                  • 27210
                  • 158 Posts
                  ArchivistFurl is id 1

                    • 18373 ☆ A M B ☆
                    • 3,141 Posts
                    Try disabling it and see if that solves the problem. It seems to fail caching on that plugin.

                    If you can’t disable it from the manager, you can dive into the database (prefix_site_plugins) and set the "disabled" column to 1. Then clear all cache files again and try again.
                      Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

                      Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
                      • 27210
                      • 158 Posts
                      Thank you Mark - I’ll try this when I get back to the office on Saturday. Appreciate your help.