# Cannot start CTA Frontend - 5.10.10.1-1

**URL:** <https://cta-community.web.cern.ch/t/cannot-start-cta-frontend-5-10-10-1-1/308>\
**Category:** Troubleshooting\
**Created:** [3 June 2024 17:21 UTC](https://cta-community.web.cern.ch/t/cannot-start-cta-frontend-5-10-10-1-1/308 "2024-06-03T17:21:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![george\_patargias](https://cta-community.web.cern.ch/letter_avatar_proxy/v4/letter/g/b9bd4f/32.png) [@george\_patargias](https://cta-community.web.cern.ch/u/george_patargias)\
**Post date:** [3 June 2024 17:21 UTC](https://cta-community.web.cern.ch/t/cannot-start-cta-frontend-5-10-10-1-1/308/1 "2024-06-03T17:21:13Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![rbachman](https://cta-community.web.cern.ch/user_avatar/cta-community.web.cern.ch/rbachman/32/33_2.png) [@rbachman](https://cta-community.web.cern.ch/u/rbachman)\
**Post date:** [4 June 2024 07:01 UTC](https://cta-community.web.cern.ch/t/cannot-start-cta-frontend-5-10-10-1-1/308/2 "2024-06-04T07:01:05Z")

</div>

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](https://cta-community.web.cern.ch/t/frontend-not-starting-on-alma9/304)

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.

---

<div class="post-metadata">

**Author:** ![george\_patargias](https://cta-community.web.cern.ch/letter_avatar_proxy/v4/letter/g/b9bd4f/32.png) [@george\_patargias](https://cta-community.web.cern.ch/u/george_patargias)\
**Post date:** [4 June 2024 10:00 UTC](https://cta-community.web.cern.ch/t/cannot-start-cta-frontend-5-10-10-1-1/308/3 "2024-06-04T10:00:37Z")

</div>

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
