Tags:
create new tag
view all tags
The server caches a lot of information on the status of profile compilations, and the dependencies between files. Occasionally, these caches may be corrupt. Typically, this may happen if:

  • The source file hierarchy has been moved around.
  • The server has been forced to quit in the middle of a pass. This will only happen if the process itself is interrupted. The normal stop procedure will wait for the server to cleanly complete the current pass.

The recommended way of rebuilding the caches is:

om server run -- -r

Note that this will initiate a rebuild of all the profiles which might take a while. If there still appears to be cache problems, then it is safe to manually delete the cache files (rm /var/lcfg/conf/server/cache*) and they will be recreated when the server restarts (stop the server before deleting them). However, this should not be necessary, and I'd like to know of any cases where it appears to be.

-- PaulAnderson - 17 Oct 2005

Topic revision: r1 - 2008-02-07 - squinney
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback