> the actual script that was used so far and was working in v4 is https://github.com/xrootd/xrootd/blob/master/utils/cms_monPerf FWIW, I am using: ``` cms.perf int 60s pgm /usr/share/xrootd/utils/cms_monPerf 30 ``` with `/usr/share/xrootd/utils/cms_monPerf` shipped with 5.0.2 here, and do neither observe the connection issues nor the `monitor` error message (and I can confirm from the process tree that the monitoring script is running successfully as subprocess). I am using the packages from `http://xrootd.org/binaries/stable/slc/7/x86_64` here. But of course, Andy is right and the main issue (`xrootd` not connecting) should of course be the first focus here. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1324#issuecomment-724641401 ######################################################################## 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