Print

Print


Correct, as I said the monperf directive has nothing to do with the 
companion xrootd not connecting to its cmsd. This is the first report of 
any issues in this regard. So, while I look at what might be the issue 
with the monperf script, let's concentrate on why the xrootd doesn't want 
to connect. Is it that it never started up? The log will tell us 
everything.

Andy


On Mon, 9 Nov 2020, Adrian Sevcenco wrote:

> so, the monPerf does not matter as the problem stays also with it's directive commented out.
> the actual script that was used so far and was working in v4 is https://github.com/xrootd/xrootd/blob/master/utils/cms_monPerf
>
> -- 
> 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-724530685


-- 
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-724534702

########################################################################
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