 |
 |
I'd try this: redirector: xrootd.trace emsg login stall redirect xrd.trace conn cms.trace defer files redirect stage server: # For debug, to see files being searched # cms.trace defer files redirect stage cms.trace defer redirect stage You say xrdmapc shows the configured servers, right? We had some trouble with ipv4/6 at ucsd lately, clients will be redirected to ipv6 servers only if they come in via ipv6 to the redirector. Can you restart redirector cmsd and then (after 30sec) look at: [1131] root@xrootd /var/log/xrootd/xcacheucsd# grep Routing cmsd.log | sort =====> Routing for bcache-1.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for bcache-1.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-00.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-01.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-02.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-03.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-04.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-05.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-06.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-07.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-08.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-09.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xcache-10.t2.ucsd.edu: local pub4 prv4 =====> Routing for xcache-11.t2.ucsd.edu: local pub4 prv4 pub6 prv6 =====> Routing for xrd-cache-1.ultralight.org: local pub4 prv4 pub6 prv6 =====> Routing for xrd-cache-2.ultralight.org: local pub4 prv4 pub6 prv6 Matevz On 2019-12-02 11:24, Sam Skipsey wrote: > No, I explicitly did that. (As I noted, there's a typo for that in the > example, as it uses "rw" not "r/w" , which doesn't work). > > I've tried basically every variation of stage/nostage/ r/w / r/o at > different parts of the network, but the manager cmsd never seems to > actually consider the servers (even when I've already pre-staged the > file it's looking for by directly talking to the server xrootd service > and getting it to cache). > > Sam > > On Mon, 2 Dec 2019 at 19:09, Matevz Tadel <[log in to unmask]> wrote: >> >> Hi, >> >> Before I go looking at what's wrong on the web page, have a look at this, page 21: >> >> https://indico.cern.ch/event/727208/contributions/3444604/ >> >> Maybe you're missing the r/w for xrootd, stage r/o for cmsd trick? >> >> Cheers, >> Matevz >> >> On 2019-11-28 08:22, Sam Skipsey wrote: >>> Hello everyone, >>> >>> So, I have another question, working entirely from the documentation >>> on xrootd.org >>> >>> In the documentation for cache configuration, there's an example of >>> how to set up a cluster of disk caching proxies: >>> >>> https://xrootd.slac.stanford.edu/doc/dev410/pss_config.pdf [page 38, >>> you can't copy it because weirdly its an image] >>> >>> I'm following that exactly (except for fixing the typo where the >>> example has an export using "rw" and not "r/w" as an option), and, >>> well, it just doesn't seem to work. >>> >>> If I talk directly to the server that the proxies talk to: I can get a file. >>> If I talk to an individual proxy: I can also get a file (and it is cached) >>> If I talk to the *redirector*, I get, with debugging on "Open has >>> returned with status [ERROR] Server responded with an error: [3011] No >>> servers have read access to the file" >>> >>> The redirector logs show that the cmsd on the proxy logs in (and is >>> listed as a "server" in its list of servers), and the proxy cmsd logs >>> also show that it happily registers to the redirector. >>> >>> How do I debug this? >>> >>> I've already tried adding and removing options to the various exports, >>> making sure that all the relevant ports are open, etc. >>> >>> Sam >>> >>> ######################################################################## >>> Use REPLY-ALL to reply to list >>> >>> To unsubscribe from the XROOTD-L list, click the following link: >>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1 >>> >> ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1