Cta-frontend-grpc fails to start after upgrading to 5.11.2.0-1

Hi,

After the upgrade to version 5.11.2.0-1, the cta-frontend-grpc fails to start. The parameters “no-log-header” and “port” are no longer required, but they are still included in the systemd service unit file.

ExecStart=/usr/bin/cta-frontend-grpc --no-log-header --port ${GRPC_PORT}

The new version requires a configuration file, but it’s not included in the rpm.

If we try to use this example , it doesn’t work either.

Reviewing this issue with Mwai from Desy, he has seen that the cta-frontend-grpc starts if we add the following lines to the configuration file:

cta.instance_name test
cta.schedulerdb.scheduler_backend_name vfstest
cta.catalogue.numberofconnections 10
cta.objectstore.backendpath /ctavfs
cta.log.url file:/var/log/cta/cta-frontend-grpc.log
cta.log.format default
cta.schedulerdb.numberofthreads 100
cta.schedulerdb.threadstacksize_mb 1
cta.schedulerdb.enable_repack_requests off
cta.schedulerdb.enable_user_requests off

We are not sure why this extra configuration is needed because it’s already present in the cta-frontend-xrootd.conf.

Many thanks,
Esther

Hi Esther,

This version indeed introduced some changes to the gRPC frontend but the example.conf file was not updated, nor the systemd service file. The configuration file for the grpc-frontend is now expected to be found in /etc/cta/cta-frontend-grpc.conf, so these values indeed need to be added there. This is the default location but you could try to pass the config as a command-line option when starting the frontend to override it, (option -c <path_to_config>)

I will update these files right away. Thank you for reporting the issue.

Also please note that the port is now specified as a config entry, as shown in the example file, and the --no-log-header option is also replaced by the following config entry:

cta.log.log_header false

If this line is skipped, the default behaviour is to log the header.

Hi Konstantina,

Thank you very much for reviewing this problem.