Skip to content

NAME#

cta-maintd --- CTA Maintenance daemon

SYNOPSIS#

cta-maintd [--config config_file] [--stdout]] [--log-to-file log_file] [--log-format format]\ cta-maintd --help

DESCRIPTION#

cta-maintd is the daemon responsible for performing housekeeping tasks related to the disk buffer and scheduler. It is composed of different routines that periodically execute.

Disk Report Routine

Queue Cleanup Routine

Garbage Collector Routine

Repack Request Routine

OPTIONS#

-c, --config config_file

Read cta-maintd configuration from config_file instead of the default, /etc/cta/cta-maintd.conf.

-h, --help

Display command options and exit.

-l, --log-to-file log_file

Log to a file instead of stdout.

-o, --log-format format

Output format for log messages. [default|json]

-s, --stdout

Log to standard output. Logging to stdout is the default, but this option is kept for compatibility reasons

CONFIGURATION#

The cta-maintd daemon reads its configuration parameters from the CTA configuration file (by default, /etc/cta/cta-maintd.conf). Each option is listed with its default value.

Maintd Configuration Options#

maintd LogMask INFO

Logs with a level lower than this value will be masked. Possible values are EMERG, ALERT, CRIT, ERR, WARNING, NOTICE (USERERR), INFO, DEBUG. USERERR log level is equivalent to NOTICE, because by convention, CTA uses log level NOTICE for user errors.

maintd LogFormat json

The default format for log lines is jsos. If this option is set to unstructured, log lines will be output in key=value format.

maintd CatalogueConfigFile /etc/cta/cta-catalogue.conf

Path to the CTA Catalogue configuration file. See FILES, below.

ObjectStore BackendPath (no default)

URL of the objectstore (CTA Scheduler Database). Usually this will be the URL of a Ceph RADOS objectstore. For testing or small installations, a file-based objectstore can be used instead. See cta-objectstore-initialize.

General Configuration Options#

This options will be included in every log line of maintd to enhance log identification when swapping drives between different backends.

InstanceName (no default)

Unique string to identify CTA\'s catalogue instance maintd is serving.

SchedulerBackendName (no default)

The unique string to identify the backend scheduler resources. It can be structured as: [ceph|postgres|vfs][User|Repack].

FILES#

/etc/cta/cta-maintd.conf

The CTA maintd configuration file, containing the options described above under CONFIGURATION. See /etc/cta/cta-maintd.conf.example.

/etc/cta/cta-catalogue.conf

Usual location for the CTA Catalogue configuration file. See CatalogueConfigFile option under CONFIGURATION, and /etc/cta/cta-catalogue.conf.example.

/var/log/cta/cta-maintd.log

Usual location for the maintd log file.

SEE ALSO#

CERN Tape Archive documentation https://cta.docs.cern.ch/

COPYRIGHT#

Copyright © 2025 CERN. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. In applying this licence, CERN does not waive the privileges and immunities granted to it by virtue of its status as an Intergovernmental Organization or submit itself to any jurisdiction.