 |
 |
Affected sites: Any site whose clients use a private IP address to connect to a redirector’s public IP address. If this is not your situation, may you stop reading this post. Synopsis: When no interfaces have been identified for a server via the xrd.network directive the interface management code in the redirector to which the server connects may exit early thus not honoring the network routing (specified or defaulted). Impact: Clients connecting with a private IP address may, and many times do, get the error message: No reachable servers are available to read the file. or some variation of it. Severity: Stopper for any site whose clients use private IP addresses and servers that use public IP addresses. Otherwise, there is no apparent problem and you may ignore this posting. Version affected: A particular combination of versions needs to be installed, as follows: a) Redirector at 4.0.2 b) Server or supervisor at 4.0.2 or earlier. c) Client version is immaterial. Mitigations (in increasing complexity); choose one of the below: 1) Downgrade the redirector to 3.3.6 or earlier. However, doing so disables IPv6 and public-private network support. Server/supervisors may remain at the 4.0.2 or earlier release level. This configuration has been tested and found to work; or 2) If all servers/supervisors are at 4.0.2 then for each of these add the xrd.network directive to the configuration file identifying the interfaces that the server/supervisor is using via the routes and use options. You will need to do this for the redirector if the routing is other than local. http://xrootd.org/doc/dev4/xrd_config.htm#_Toc383723505 provides details on how to do this. 3) For those sites that run a specialized cmsd, it is possible to run the redirector based on code in git head. The latest code omitted the offending code path to avoid this particular problem. However, git head has only undergone successful alpha testing and may have other, yet undiscovered, issues. Proceed with caution. Log term solution: Only a source code change can correct this end-case problem. While the fix is not complicated it does require a new patch release, 4.0.3. Upcoming release 4.1.0 should not have this particular problem. However, 4.1.0 is not scheduled to be released until September. --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/130 ######################################################################## 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