Details
Normal Description
Our client has had a Quay deployment for 6 months, the deployment is hooked to an AWS S3 backend for storage. The log export worker is not periodically saving logs to hard storage which increases the database size. We have run some SQL commands on the logentry3 table:
quaydb=> select datetime from logentry3 limit 1; datetime ---------------------------- 2021-11-15 00:25:19.187885 quaydb=> select datetime from logentry3 order by datetime desc limit 1; datetime ---------------------------- 2022-06-28 14:43:01.638894
Currently, they have the following settings in their config.yaml file:
ACTION_LOG_ARCHIVE_LOCATION: default ACTION_LOG_ARCHIVE_PATH: /datastorage/registry/logentry ACTION_LOG_ROTATION_THRESHOLD: 2w FEATURE_ACTION_LOG_ROTATION: true
We tried with 4 weeks as well, but no logs were exported to the S3 bucket:
DISTRIBUTED_STORAGE_CONFIG: default: - S3Storage - host: s3.eu-central-1.amazonaws.com s3_access_key: xxx s3_bucket: dev-quay-container-registry-dare s3_secret_key: xxx storage_path: /datastorage/registry DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS: [] DISTRIBUTED_STORAGE_PREFERENCE: - default
We also see in the logs that the export log worker is started and we also see that it's searching for jobs to run, but no jobs are created.
Can you please check what's going on? Thanks!
