Dear All,
EOS instance at Kolkata T2 is fail due to eosd is failed with following Error:
[root@eos ~]# service eosd start
Starting eosd for instance: mainmkdir: cannot create directory /eos/': File exists chmod: cannot access/eos/’: Transport endpoint is not connected
EOS_FUSE_PING_TIMEOUT : 15
EOS_FUSE_DEBUG : 0
=================
I think it may be failure of FUSE. When we manually try to mount the /eos , it’s gives mountpoint failed error.
+++++++
[root@eos ~]# ps -aef | grep fuse
root 23091 11768 0 20:28 pts/2 00:00:00 grep fuse
[root@eos ~]# eos fuse mount /eos
… trying to create … /eos
error: creation of mountpoint failederror: cannot create mountpoint /eos !
[root@eos ~]#
+++++++++
EOS and XROOT version in eos mgm and fst are same:
++++++
[root@eos ~]# xrootd -v
190121 20:21:01 13849 Scalla is starting. . .
Copr. 2004-2012 Stanford University, xrd version v20170724-0e6b1f5
++++++ xrootd anon@eos.tier2-kol.res.in initialization started.
Config maximum number of connections restricted to 4096
190121 20:21:01 13849 XrdOpen: Unable to bind socket to port 1094; address already in use
------ xrootd anon@eos.tier2-kol.res.in:-1 initialization failed.
[root@eos ~]# cexec “eos -v”
************************* eos_kolkata_cluster *************************
--------- eos01.tier2-kol.res.in---------
EOS 0.3.268 (CERN)
Written by CERN-IT-DSS (Andreas-Joachim Peters, Lukasz Janyst & Elvin Sindrilaru)
--------- eos02.tier2-kol.res.in---------
EOS 0.3.268 (CERN)
Written by CERN-IT-DSS (Andreas-Joachim Peters, Lukasz Janyst & Elvin Sindrilaru)
--------- eos03.tier2-kol.res.in---------
EOS 0.3.268 (CERN)
Written by CERN-IT-DSS (Andreas-Joachim Peters, Lukasz Janyst & Elvin Sindrilaru)
[root@eos ~]
+++++++
So, help to up the EOS at Kolkata T2.