asevcenc
April 7, 2020, 8:25am
1
Hi! So, after what successful start of mgm (it would seem so) when starting the fst i get this:
------ File system server initialization completed.
=====> fstofs does not enforce SSS authentication for XROOT clients - make sure MGM enforces sss for this FST!
=====> fstofs.autoboot : true
=====> fstofs.broker : root://mgm.spacescience.ro:1097//eos/fst01.spacescience.ro:1095/fst
=====> eoscp-log : /var/log/eos/fst/eoscp.log
200407 11:18:19 time=1586247499.003158 func=UpdateSanitizedGeoTag level=ERROR logid=static.............................. unit=fst@fst01.spacescience.ro:1095 tid=00007f74daccb780 source=XrdFstOfs:923 tident= sec=(null) uid=99 gid=99 name=- geo="" msg="empty geotag"
200407 11:18:19 time=1586247499.003182 func=Configure level=ERROR logid=static.............................. unit=fst@fst01.spacescience.ro:1095 tid=00007f74daccb780 source=XrdFstOfs:739 tident= sec=(null) uid=99 gid=99 name=- geo="" msg="failed to update geotag, wrongly formatted"
200407 11:18:19 213145 XrootdConfig: Unable to create file system object via libXrdEosFst.so
200407 11:18:19 213145 XrootdConfig: Unable to load file system.
------ xrootd protocol initialization failed.
200407 11:18:19 213145 XrdProtocol: Protocol xrootd could not be loaded
------ xrootd fst@fst01.spacescience.ro:1095 initialization failed.
Any idea what it missing? i already registered the mount points with eosfstregister
esindril
April 7, 2020, 9:00am
2
Hi Adrian,
Looking at the error message in your post I would assume you are missing the EOS_GEOTAG env variable. You can set it in /etc/sysconfic/eos_env like this for example:EOS_GEOTAG="::test"
Cheers,
asevcenc
April 7, 2020, 9:04am
3
well, why is this needed? from the description from eos_env and the fact that the default is empty i assumed that the default is good enough
esindril
April 7, 2020, 9:22am
4
Without a geotag the FSTs will not start. The /etc/sysconfig/eos_env needs some customization before you can actually start the service. I think we used to have a default value before but we dropped it in the meantime. You can have look here on the constraints put on the geotag:https://gitlab.cern.ch/dss/eos/-/blob/master/fst/XrdFstOfs.cc#L893
Cheers,
gbiro
May 24, 2022, 9:52am
6
Dear Elvin, Adrian,
sorry for bringing up this old topic, but I think we have a very similar problem. We tried to add some new FST nodes to the already working infrastructure, with the methods that we used before, but now we recive the following message from the FST:
Config effective /etc/xrd.cf.fst ofs configuration:
all.role server
ofs.maxdelay 60
ofs.persist off hold 600
ofs.trace 0
220524 09:35:05 time=1653384905.285095 func=Configure level=INFO logid=cb11e91c-db44-11ec-ae7f-001e675049de unit=fstoss@localhost tid=00007f5e9abf3780 source=XrdFstOss:170 tident=<service> sec= uid=0 gid=0 name= geo="" preread depth=0, queue_size=0 and bytes=0
ofs.osslib libEosFstOss.so
------ File system server initialization completed.
=====> fstofs does not enforce SSS authentication for XROOT clients - make sure MGM enforces sss for this FST!
220524 09:35:05 time=1653384905.286269 func=SetXrdClTimeouts level=INFO logid=static.............................. unit=fstoss@localhost tid=00007f5e9abf3780 source=XrdFstOfs:2580 tident= sec=(null) uid=99 gid=99 name=- geo="" msg="update xrootd client timeouts" name=ConnectionRetry value=1
=====> fstofs.qdbcluster : eos-mgm1.alice-af.wigner.hu:7001 eos-mgm1.alice-af.wigner.hu:7002 eos-mgm1.alice-af.wigner.hu:7003
220524 09:35:05 time=1653384905.286286 func=SetXrdClTimeouts level=INFO logid=static.............................. unit=fstoss@localhost tid=00007f5e9abf3780 source=XrdFstOfs:2580 tident= sec=(null) uid=99 gid=99 name=- geo="" msg="update xrootd client timeouts" name=ConnectionWindow value=5
220524 09:35:05 time=1653384905.286302 func=SetXrdClTimeouts level=INFO logid=static.............................. unit=fstoss@localhost tid=00007f5e9abf3780 source=XrdFstOfs:2580 tident= sec=(null) uid=99 gid=99 name=- geo="" msg="update xrootd client timeouts" name=MetalinkProcessing value=0
220524 09:35:05 time=1653384905.286311 func=SetXrdClTimeouts level=INFO logid=static.............................. unit=fstoss@localhost tid=00007f5e9abf3780 source=XrdFstOfs:2580 tident= sec=(null) uid=99 gid=99 name=- geo="" msg="update xrootd client timeouts" name=StreamErrorWindow value=0
220524 09:35:05 time=1653384905.286316 func=SetXrdClTimeouts level=INFO logid=static.............................. unit=fstoss@localhost tid=00007f5e9abf3780 source=XrdFstOfs:2580 tident= sec=(null) uid=99 gid=99 name=- geo="" msg="update xrootd client timeouts" name=TimeoutResolution value=1
=====> fstofs.qdbpassword length : 89
=====> fstofs.autoboot : true
=====> fstofs.broker : root://eos-mgm1.alice-af.wigner.hu:1097//eos/eos-fst34.alice-af.wigner.hu:1095/fst
=====> eoscp-log : /var/log/eos/fst/eoscp.log
220524 09:35:05 7529 XrootdConfig: Unable to create file system object via libXrdEosFst.so
220524 09:35:05 time=1653384905.302195 func=Configure level=ERROR logid=static.............................. unit=fst@eos-fst34.alice-af.wigner.hu:1095 tid=00007f5e9abf3780 source=XrdFstOfs:747 tident= sec=(null) uid=99 gid=99 name=- geo="" msg="failed to update geotag, wrongly formatted" geotag="%s"
220524 09:35:05 7529 XrootdConfig: Unable to load file system.
------ xrootd protocol initialization failed.
220524 09:35:05 7529 XrdProtocol: Protocol xrootd could not be loaded
------ xrootd fst@eos-fst34.alice-af.wigner.hu:1095 initialization failed.
The /etc/sysconfig/eos_env is the same as on the other nodes, containing the line EOS_GEOTAG='::KFKI'
We are a little bit confused now, so we would be grateful for any help!
Thanks,
esindril
May 24, 2022, 3:59pm
7
Hi Gabor,
According to the error message the geotag for you FST is not properly set. The geotag should be a seriese of token in the form: <token1>::<token2> ...https://gitlab.cern.ch/dss/eos/-/blob/master/common/ParseUtils.hh#L164
Cheers,