search

rucio / containers

Containers for Rucio
Apache License 2.0
8 stars 54 forks source link

Error when running fts container: /docker-entrypoint.sh: line 19: /usr/sbin/fts_bringonline: No such file or directory #299

Closed maxnoe closed 2 months ago

maxnoe commented 3 months ago

Running the rucio-fts container in a docker compose setting, I see the following error in the log. However, the container continues to run.

rucio-fts-1        | wait-for-it.sh: waiting 3600 seconds for ftsdb:3306
rucio-fts-1        | wait-for-it.sh: ftsdb:3306 is available after 0 seconds
rucio-fts-1        | ERROR 2059 (HY000): Authentication plugin 'caching_sha2_password' cannot be loaded: /usr/lib64/mysql/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory
rucio-fts-1        | DEBUG   Wed, 27 Mar 2024 14:20:56 +0000; Changed running user and group to fts3:fts3
rucio-fts-1        | DEBUG   Wed, 27 Mar 2024 14:20:56 +0000; fts_url_copy full path /usr/sbin/fts_url_copy
rucio-fts-1        | DEBUG   Wed, 27 Mar 2024 14:20:56 +0000; Changed running user and group to fts3:fts3
rucio-fts-1        | /docker-entrypoint.sh: line 19: /usr/sbin/fts_bringonline: No such file or directory
rucio-fts-1        | AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.29.0.9. Set the 'ServerName' directive globally to suppress this message
bari12 commented 2 months ago

The fts container should really only be used in testing / demo environments. So we don't really mind so much if there are non-critical errors. This is not a production container.