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

The new manager - looking for best practice solutions

    • 1343 ☆ A M B ☆
    • 2,213 Posts
    AMDbuilder Reply #171, 17 years, 8 months ago
    It looks like someone updated the SVN as this is what I just got:

    [2009-02-07 00:58:23] (INFO @ /revo/_build/transport.core.php) Beginning build script processes...
    [2009-02-07 00:58:23] (INFO @ /revo/_build/transport.core.php) Removed pre-existing core/ and core.transport.zip.
    [2009-02-07 00:58:23] (INFO @ /revo/_build/transport.core.php) Core transport package created.
    [2009-02-07 00:58:23] (INFO @ /revo/_build/transport.core.php) Default workspace packaged.
    [2009-02-07 00:58:23] (INFO @ /revo/_build/transport.core.php) Packaged in MODx Web Transport Facility reference.
    [2009-02-07 00:58:24] (INFO @ /revo/_build/transport.core.php) Packaged all modActions.
    [2009-02-07 00:58:24] (INFO @ /revo/_build/transport.core.php) Packaged all modMenus.
    [2009-02-07 00:58:24] (INFO @ /revo/_build/transport.core.php) Packaged all default modContentTypes.
    [2009-02-07 00:58:24] (INFO @ /revo/_build/transport.core.php) Packaged in web context.
    [2009-02-07 00:58:44] (INFO @ /revo/_build/transport.core.php) Packaged in mgr context.
    [2009-02-07 00:58:44] (INFO @ /revo/_build/transport.core.php) Packaged in connectors.
    [2009-02-07 00:58:45] (INFO @ /revo/_build/transport.core.php) Packaged all default events.
    [2009-02-07 00:58:45] (INFO @ /revo/_build/transport.core.php) Packaged all default system settings.
    [2009-02-07 00:58:45] (INFO @ /revo/_build/transport.core.php) Packaged all default context settings.
    [2009-02-07 00:58:45] (INFO @ /revo/_build/transport.core.php) Packaged in default user groups.
    [2009-02-07 00:58:45] (INFO @ /revo/_build/transport.core.php) Packaged in default roles Member and SuperUser.
    [2009-02-07 00:58:45] (INFO @ /revo/_build/transport.core.php) Packaged in default access policies.
    [2009-02-07 00:58:47] (INFO @ /revo/_build/transport.core.php) Packaged core lexicon entries and topics.
    [2009-02-07 00:58:47] (INFO @ /revo/_build/transport.core.php) Packaged in default access context permissions.
    [2009-02-07 00:58:47] (INFO @ /revo/_build/transport.core.php) Beginning to zip up transport package...
    [2009-02-07 00:58:52] (INFO @ /revo/_build/transport.core.php) Transport zip created. Build script finished.

    Execution time: 29.7240 s

    I love my home server grin
    AMDbuilder
      Patrick | Server Wrangler
      About Me: Website | Tweets |  MODX Hosting
      • 3749
      • 24,544 Posts
      BobRay Reply #172, 17 years, 8 months ago
      One of my sites hangs after showing:

      Beginning to zip up transport package...

      My other sites are fine, but this one hangs there in every browser and every _build method.

      I believe it’s this line where things go south:

      $packResults = $archive->create("{$path}{$this->signature}", PCLZIP_OPT_REMOVE_PATH, "{$path}");


      On the problem site, an earlier build was aborted during a build so it’s half-built. I’m pretty sure that’s the problem.

      Is there anything I can try before doing a new checkout?
        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
        • 22303 MODX Staff
        • 10,725 Posts
        opengeek Reply #173, 17 years, 8 months ago
        Check differences in the memory_limits. PCLZIP does everything in memory which can take a lot.

        BTW, I always build local and upload the packages. I don’t ever recommend running the _build stuff on an actual server.
          Jason Coward
          Chief Architect @ MODX
          http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
          • 3749
          • 24,544 Posts
          BobRay Reply #174, 17 years, 8 months ago
          Quote from: OpenGeek at Feb 07, 2009, 05:18 PM

          Check differences in the memory_limits. PCLZIP does everything in memory which can take a lot.

          BTW, I always build local and upload the packages. I don’t ever recommend running the _build stuff on an actual server.

          I was using the term "site" loosely. They’re all local. I’m sure the memory is OK (I think it’s 256) because it’s the same for all the installs and the others are fine.

          I made the mistake of closing down the resident debug listener during the _build on this "site" and it crashed the _build. It has hung ever since then. Is there some way I can get back to a clean pre-_build state without doing a fresh checkout?

            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
            • 26903
            • 1,336 Posts
            shamblett Reply #175, 17 years, 8 months ago
            I’ve found on one of my windows boxes that deleting any existing core.transport.zip files and core directories in packages before I run the transport.core.zip seems to make it happier with zipping the core up. It would occasionally fail in the zipping, I do this every time now and its been OK since. Why this should be I don’t know, linux has never done this.

            BTW why do we zip it anyway? Does the install not just unzip it into the packages directory as ’core’ and use that for the actual install. I’ve often thought this may be a step we can do without for local/dev testing. A flag maybe?
              Use MODx, or the cat gets it!
              • 22303 MODX Staff
              • 10,725 Posts
              opengeek Reply #176, 17 years, 8 months ago
              Quote from: shamblett at Feb 08, 2009, 03:18 AM

              I’ve found on one of my windows boxes that deleting any existing core.transport.zip files and core directories in packages before I run the transport.core.zip seems to make it happier with zipping the core up. It would occasionally fail in the zipping, I do this every time now and its been OK since. Why this should be I don’t know, linux has never done this.
              The packaging system is not controlled by SVN, so yes, you should always delete the old zip and the old package directory (core/packages/core/) or you run the risk of zipping up old files that may have moved or been deleted. The Ant build scripts do this automatically, and I thought the build script did so itself as well, but maybe not.

              Quote from: shamblett at Feb 08, 2009, 03:18 AM

              BTW why do we zip it anyway? Does the install not just unzip it into the packages directory as ’core’ and use that for the actual install. I’ve often thought this may be a step we can do without for local/dev testing. A flag maybe?
              The package contains the manifest for installation of all data and files. Technically, unless you run the Ant build scripts (local or distribution), you are not truly testing properly. JS compression and aggregation, important file token replacement, and build specific features are all part of the build system to produce a downloadable/usable distribution package.

              The Ant build system will be soon replaced by a Phing build system (since most PHP developers would be more likely to work with Phing than Ant), but will retain hooks from Ant (for those who use Eclipse, this will provide smooth integration with Phing via Ant).
                Jason Coward
                Chief Architect @ MODX
                http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
                • 26903
                • 1,336 Posts
                shamblett Reply #177, 17 years, 8 months ago
                Fair enough, thanks for the info
                  Use MODx, or the cat gets it!
                  • 3749
                  • 24,544 Posts
                  BobRay Reply #178, 17 years, 8 months ago
                  Quote from: OpenGeek at Feb 08, 2009, 11:14 AM

                  You should always delete the old zip and the old package directory (core/packages/core/) or you run the risk of zipping up old files that may have moved or been deleted.  The Ant build scripts do this automatically, and I thought the build script did so itself as well, but maybe not.

                  The code to delete it is there and I can’t see anything wrong with it, but it wouldn’t surprise me if there’s a permission problem on Vista.

                  I updated the _build code to report on this and it appears that core.transport.zip is deleted but the attempt to remove the core/ directory fails:

                  /* remove pre-existing package files and directory */
if (file_exists($packageDirectory . 'core.transport.zip')) {
    unlink($packageDirectory . 'core.transport.zip');
}
   if (file_exists($packageDirectory . 'core.transport.zip')) {
       $xpdo->log(XPDO_LOG_LEVEL_INFO,'Failed to Remove core.transport.zip.'); flush();
   } else {
       $xpdo->log(XPDO_LOG_LEVEL_INFO,'Removed core.transport.zip.'); flush();

   }
if (file_exists($packageDirectory . 'core') && is_dir($packageDirectory . 'core')) {
    $cacheManager->deleteTree($packageDirectory . 'core', true);
}

if (file_exists($packageDirectory . 'core') && is_dir($packageDirectory . 'core')) {
    $xpdo->log(XPDO_LOG_LEVEL_INFO,'Failed to remove pre-existing core/'); flush();
} else {
    $xpdo->log(XPDO_LOG_LEVEL_INFO,'Removed pre-existing core/'); flush();
}


                  Manually removing the core directory solved my hanging _build problem (thanks Shamblett!  grin)

                  It also dropped my typical _build time from 540 seconds to 25 seconds.
                    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