Introduction

Cache Clearing

This page describes commands involved in clearing cache from the command line.

Clearing file cache using the Symfony cache:clear command

Out of the box Symfony provides a command to perform cache clearing. It will delete all file-based caches, which mainly consist of Twig template, Symfony container, and Symfony route cache, but also everything else stored in cache folder. Out of the box on a single-server setup this includes "Content cache". For further information on use, see the help text of the command:

php app/console --env=prod cache:clear -h

Clearing "Content Cache" on a Cluster setup

For Cluster setup, the content cache ( HTTP Cache   and Persistent Cache) must be set up to be shared among the servers. And while all relevant cache is cleared for you on repository changes when using the APIs, there might be times where you'll need to clear cache manually: 

• Varnish: Cache purge
• Persistence Cache: Using Cache service

Web Debug Toolbar

When running eZ Platform in the dev environment you have access to the standard Symfony Web Debug Toolbar. It is extended with some eZ Platform-specific information:

SPI (persistence)

This sections provides section provides the number of uncached non-cached SPI calls and handlers. You can see details of these calls in the Symfony Profiler page.

Site Access

Here you can see the name of the current Siteaccess and how it was matched. For reference see the list of possible siteaccess matchers.

Configuration

Logging and Debug Configuration

Introduction

Logging in eZ Platform consists of two parts, several debug systems that integrates with symfony developer toolbar to give you detailed information about what is going on. And standard PSR-3 logger, as provided by Symfony using Monolog.

Debugging in dev environment

When using the Symfony dev environment , the system out of the box tracks additional metrics for you to be able to debug issues, this includes Stash cache use (done by StashBundle), and a persistence cache use.

Reducing memory use

If you are running out of memory and don't need to keep track of cache hits and misses. Then StashBundle tracking, represented by the stash.tracking setting, and persistence cache logging, represented by the setting parameters.ezpublish.spi.persistence.cache.persistenceLogger.enableCallLogging, can optionally be disabled.

stash:
    tracking: false                  # Default is true in dev
    tracking_values: false           # Default is false in dev, to only track cache keys not values
    caches:
        default:
            inMemory: false          # Default is true
            registerDoctrineAdapter: false

parameters:
    ezpublish.spi.persistence.cache.persistenceLogger.enableCallLogging: false

Error logging and rotation

eZ Platform uses the Monolog component to log errors, and it has a RotatingFileHandler that allows for file rotation.

According to their documentation, it "logs records to a file and creates one logfile per day. It will also delete files older than $maxFiles".

But then, their own recommendation is to use "logrotate" instead of doing the rotation in the handler as you would have better performance.

If you decided to use Monolog's handler, it can be configured in app/config/config.yml

monolog:
    handlers:
        main:
            type: rotating_file
            max_files: 10
            path: "%kernel.logs_dir%/%kernel.environment%.log"
            level: debug