For some reason the eos@mgm service (running on the single MGM node of our test EOS instance) enters a failed state due to segmentation fault. Only once I managed to start it and after a client command (like “eos fs ls”) it stopped again. Do you know what should I do? Many thanks, George
systemd: Started EOS mgm.
Mar 19 17:36:45 host-172-16-103-63 sh: /opt/eos/xrootd/bin/xrootd
Mar 19 17:36:45 host-172-16-103-63 sh: Register objects provided by NsQuarkdbPlugin …
Mar 19 17:36:46 host-172-16-103-63 kernel: xrootd: segfault at 70 ip 00007fdffbed54a9 sp 00007fe0066368c0 error 4 in libEosCommon.so.4.7.7[7fdffbd44000+416000]
Mar 19 17:36:46 host-172-16-103-63 systemd: email@example.com: main process exited, code=exited, status=139/n/a
Mar 19 17:36:46 host-172-16-103-63 sh: /bin/sh: line 1: 13684 Segmentation fault $XRDPROG -n mgm -c /etc/xrd.cf.mgm -l /var/log/eos/xrdlog.mgm -s /tmp/xrootd.mgm.pid -Rdaemon
Mar 19 17:36:46 host-172-16-103-63 systemd: Unit firstname.lastname@example.org entered failed state.
Mar 19 17:36:46 host-172-16-103-63 systemd: email@example.com failed.