Hi Tapas,Yes, this is a known bug and will be corrected in 4.1. If you have enabled blacklisting (i.e. cms.blacklist directive) you should remove it. The bug was fixed with this patch:AndyP.S. The NODELAY error message is also suppressed in 4.1 – it causes no harm.From: [log in to unmask] href="mailto:[log in to unmask]">Tapas SarangiSent: Thursday, November 20, 2014 1:41 PMTo: [log in to unmask] href="mailto:[log in to unmask]">[log in to unmask]Subject: Login: localhost login failed; blacklistedDear Xrootd Developers,
Here at T2_US_Wisconsin, we are using xroot-4.0.4 OSG 32 released version. We are seeing problems with cmsd.log for all of our supervisor nodes.
/var/log/xrootd/cmsd.log repeats these messages,
141120 15:19:47 12849 setOpts: Unable to set socket NODELAY; operation not supported
141120 15:19:47 12849 Inet: Accepted connection from 7@localhost
141120 15:19:47 12849 Login: localhost login failed; blacklisted
and /var/log/xrootd/xrootd.log repeats this one :
141120 15:35:23 12755 cms_Login: localhost login failed; localhost is blacklisted
As a result we have limited number of servers without the supervisors. All our xrootd servers, redirector and supervisors have dual stack IPv6/v4 network.Any help to understand and solve the problem is appreciated. Let us know if you need more information from us.Thanks-Tapas
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
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
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