RucioAccessingLogs

Rucio logs

Rucio is built up of several components, each with their own set of logs.

Rucio Server

The Rucio server is the place that clients will authenticate with and send commands to to make Rucio do tasks. If there is an issue with authentication, access, or issues with commands this may be found in the server logs.

The server is found at:

rucio-server01.nubes.stfc.ac.uk

Access logs can be found /var/log/rucio/httpd_access_log Error logs can be found /var/log/rucio/httpd_error_log

Rucio Daemons

Rucio's tasks are carried out by daemons. These are found at:

rucio-daemon02.nubes.stfc.ac.uk

For Rucio to function it needs to run several different daemons, these are all currently being run using docker, but the logs are being mounted into /var/log/rucio/ Below is a list of the various daemons, a brief description of their use, and where to find the logs.

Abacus Daemons

The daemons responsible for accounts are the abacus daemons, account and rse, within the folders below are the daemon logs and the error logs:

/var/log/rucio/abacus-account/
/var/log/rucio/abacus-rse/ 

Conveyor Daemons

The daemons responsible for the movement of data. There are three, submitter sends jobs to FTS, poller updates Rucio with FTS progress, finisher finalises any data movement in Rucio. Within the directories below are the daemon logs and the error logs:

/var/log/rucio/dtm/conveyor-submitter/
/var/log/rucio/dtm/conveyor-poller/
/var/log/rucio/dtm/conveyor-finisher/

Reaper Daemons

The daemons responsible for deleting files from RSEs that are not protected by rules as RSEs become full. Within the directories below are the daemon logs and the error logs:

/var/log/rucio/dtm/reaper

Judge Daemons

The daemons responsible for looking at rules and assessing changes, re Within the directories below are the daemon logs and the error logs:

/var/log/rucio/dtm/judge-evaluator/
/var/log/rucio/dtm/judge-repairer/
/var/log/rucio/dtm/judge-cleaner/