Cannot start CTA Frontend - 5.10.10.1-1

Troubleshooting
1

Hi,

I cant seem to be able to start cta-frontend.service after upgrading to
CTA 5.10.10.1-1 (EL7).

See log lines pasted below. Can you please give us clue?

Thanks,

George

Config Configuring standalone server.
240603 18:20:09 14849 ssi_XrdSsiCtaServiceProvider: pid:14849 tid:140520811014336 XrdSsiCtaServiceProvider() constructor
240603 18:20:09 14849 ssi_XrdSsiCtaServiceProvider: pid:14849 tid:140520811014336 Called Init(/etc/cta/cta-frontend-xrootd.conf,)
240603 18:20:09 14849 ssi_XrdSsiCtaServiceProvider: pid:14849 tid:140520811014336 XrdSsiCtaServiceProvider::Init(): std::exception bad optional access
240603 18:20:09 14849 ssi_Config: Provider initialization failed.
------ ssi initialization failed.
240603 18:20:09 14849 XrootdConfig: Unable to load file system via libXrdSsi.so
240603 18:20:09 14849 XrootdConfig: Unable to load base file system using libXrdSsi.so
------ xroot protocol initialization failed.
240603 18:20:09 14849 XrdProtocol: Protocol xroot could not be loaded
------ xrootd cta@cta-front02.scd.rl.ac.uk:10955 initialization failed.

2

Hi George,
there was a similar question the other day, re. the new CTA frontend on Alma9, perhaps there is some overlap? Frontend not starting on Alma9

Based on the above error I’d check cta-frontend-xrootd.conf. We put a list of the options we changed during our Alma9 migration in the other thread.

3

Hi Richard,

Thanks for your reply.

It turned out that, I needed to add to the cta-frontend-xrootd.conf
the following directives

Block requests for user or repack

cta.schedulerdb.enable_repack_requests on
cta.schedulerdb.enable_user_requests on

It looks like that the following are optional: cta-frontend.service starts successfully without them being present.

George