 |
 |
Dear,
This is and starge behaviour for our xrootd datatransfer systems (based on 8 identical CentOS 7 VMs):
[root@pool02 ~]# xrootd -v
v4.12.4
[root@pool02 ~]# rpm -qa| grep xrootd
xrootd-client-libs-4.12.4-1.el7.x86_64
xrootd-4.12.4-1.el7.x86_64
xrootd-lcmaps-1.7.8-2.osg35.el7.x86_64
xrootd-server-4.12.4-1.el7.x86_64
xrootd-client-4.12.4-1.el7.x86_64
xrootd-server-libs-4.12.4-1.el7.x86_64
xrootd-cmstfc-1.5.2-6.osg35.el7.x86_64
xrootd-voms-4.12.4-1.el7.x86_64
xrootd-libs-4.12.4-1.el7.x86_64
xrootd-selinux-4.12.4-1.el7.noarch
Apr 12 20:06:41 pool02 systemd: [log in to unmask] failed.
Apr 12 20:06:41 pool02 systemd: [log in to unmask] has no holdoff time, scheduling restart.
Apr 12 20:06:41 pool02 systemd: Stopped XRootD xrootd daemon instance clustered.
Apr 12 20:06:41 pool02 systemd: Started XRootD xrootd daemon instance clustered.
Apr 12 20:07:21 pool02 systemd: [log in to unmask]: main process exited, code=killed, status=64/RTMIN+30
Apr 12 20:07:21 pool02 systemd: Unit [log in to unmask] entered failed state.
Apr 12 20:07:21 pool02 systemd: [log in to unmask] failed.
Apr 12 20:07:21 pool02 systemd: [log in to unmask] has no holdoff time, scheduling restart.
Apr 12 20:07:21 pool02 systemd: Stopped XRootD xrootd daemon instance clustered.
Apr 12 20:07:21 pool02 systemd: Started XRootD xrootd daemon instance clustered.
During these reboots transfers are jumpling from server to server until it is finished.
Has anyone any notice about this behaviour?
Regards, I
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1