Hi Andy,
On 10/05/12 16:12, Andrew Hanushevsky wrote:
> Hi Matevz,
>
> On Fri, 5 Oct 2012, Matevz Tadel wrote:
>
>> OK, I'm trying to do this now. I have the main redirector (hadoop) on
>> port 1094 that uses
>> cms.dfs lookup distrib redirect immed
>> all.export /store/ global readonly
>> xrootd.redirect localhost:1095 all /tas
>> and the second one for nfs space running on port 1095. Contacting the
>> one on port 1095 works ok, I can see all four disk servers behind it.
>> However, when I try to access it via the "default" redirector (config frags
>> above) I get:
>>
>> 121005 12:37:25 23260 Xrd: CheckErrorStatus: Server [xrootd.t2.ucsd.edu]
>> declared: Opening path '/tas-5/matevz/XrdAuthzVo.tgz' is disallowed.(error
>> code: 3010)
>>
>> If I add:
>> all.export /tas local writable
>> then I get:
>> 121005 12:53:23 23323 Xrd: CheckErrorStatus: Server [xrootd.t2.ucsd.edu]
>> declared: No servers have read access to the file(error code: 3011)
>> which seems to indicate redirect did not kick in at all.
>
>> So ... how can I do static redirect here while maintaining single lookup via
>> cms.dfs for stuff under the default redirector?
> Well, the problem is with your exports. The first error was that you didn't
> export "/tas" and, as you suspected, by adding it you avoided the "disallowed"
> error. However, since you declared "/tas" local the redirector basically ignores
> the export and, correctly, tells you that no one has that path exported to the
> outside world. Why are you specifying "global" and "local" anyway?
So that /store gets "exported" to meta-manager at UNL and /tas does not. This
used to work fine when all NFS servers were reporting directly to this manager.
Why doesn't the xrootd.redirect kick in?
Matevz
########################################################################
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
|