 |
 |
Some ATLAS users reported crashes or hangs of their workflow; I've made some checks and believe it was due to a (relatively) recent addition to their ATLAS environment which set XRD_ENABLEFORKHANDLERS. The workflow was using xroot file access via XrdPosixXrootd.so.1 (so using XrdClient). The OS is 64bit SL(C)6. The process did fork a child process (due to a popen()). I've made a minimal program which shows a problem fairly often, which directly uses XrdClient (either libXrdClient.so.1 from the 3.3.6 compatibility package or with .so.2 from 4.2.1). e.g. (edit fork_handler_test2.cpp to open a file on a convenient xrootd server) c++ fork_handler_test2.cpp -I/usr/include/xrootd -lXrdClient export XRD_ENABLEFORKHANDLERS=1 ./a.out observed result is that in a fairly high fraction of attempts the program hangs or give a segmentation fault. Expected result is to read 1 byte from the file, no output. --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/244 ######################################################################## 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