Print

Print


Hi Wei,

   Not sure if this helps

This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/xrdadler32...Reading symbols from /usr/lib/debug/usr/bin/xrdadler32.debug...
warning: section .gnu.liblist not found in /usr/lib/debug/usr/bin/xrdadler32.debug

warning: section .gnu.conflict not found in /usr/lib/debug/usr/bin/xrdadler32.debug

warning: section .dynbss not found in /usr/lib/debug/usr/bin/xrdadler32.debug
done.
done.
(gdb) run
Starting program: /usr/bin/xrdadler32 root://nsfprv//atlas/dq2/mc10_7TeV/NTUP_SUSY/e577_s933_s946_r1831_r2040_p428/mc10_7TeV.105802.JF17_pythia_jet_filter.merge.NTUP_SUSY.e577_s933_s946_r1831_r2040_p428_tid281327_00/NTUP_SUSY.281327._006235.root.1
warning: section .gnu.liblist not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .gnu.conflict not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .dynbss not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .gnu.liblist not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .gnu.conflict not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .dynbss not found in /usr/lib/debug/usr/bin/xrdadler32.debug
[Thread debugging using libthread_db enabled]
warning: section .gnu.liblist not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .gnu.conflict not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .dynbss not found in /usr/lib/debug/usr/bin/xrdadler32.debug
[New Thread 0x40a00940 (LWP 18537)]
warning: section .gnu.liblist not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .gnu.conflict not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .dynbss not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .gnu.liblist not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .gnu.conflict not found in /usr/lib/debug/usr/bin/xrdadler32.debug
warning: section .dynbss not found in /usr/lib/debug/usr/bin/xrdadler32.debug
Error_accessing: root://nsfprv//atlas/dq2/mc10_7TeV/NTUP_SUSY/e577_s933_s946_r1831_r2040_p428/mc10_7TeV.105802.JF17_pythia_jet_filter.merge.NTUP_SUSY.e577_s933_s946_r1831_r2040_p428_tid281327_00/NTUP_SUSY.281327._006235.root.1
[Thread 0x40a00940 (LWP 18537) exited]


Also xrd command fails.

Doug

On Aug 13, 2011, at 3:00 AM, Yang, Wei wrote:

> Ok, I probably need you to run debugger and tell me which line print out that Error_accessing. Also, can you use xrd's getchecksum sub-command to retrieve the checksum?
> 
> regards,
> Wei Yang  |  [log in to unmask]  |  650-926-3338(O)
> 
> 
> 
> 
> On Aug 11, 2011, at 1:01 PM, Doug Benjamin wrote:
> 
>> Hi,
>> 
>>   the security is unix security and I did xrdcp by hand.
>> Thanks,
>> Doug
>> 
>> On Aug 11, 2011, at 3:24 PM, Yang, Wei wrote:
>> 
>>> another think I forget to ask, how about the security module? and can you do an xrdcp?
>>> 
>>> regards,
>>> Wei Yang  |  [log in to unmask]  |  650-926-3338(O)
>>> 
>>> 
>>> On Aug 11, 2011, at 10:57 AM, Doug Benjamin wrote:
>>> 
>>>> Hi Wei,
>>>> 
>>>> The some machines that was using for these tests all are dual nic machines on a public and private network
>>>> (yes -  I know a very troublesome idea).   I can use xrdcp to copy the files by hand using the private addresses.
>>>> Somehow the xrdalder32 command is failing.
>>>> 
>>>> Cheers,
>>>> 
>>>> Doug
>>>> 
>>>> On Aug 11, 2011, at 1:49 PM, Yang, Wei wrote:
>>>> 
>>>>> Hi Doug,
>>>>> 
>>>>> I noticed that the data server is on private IP. Just want to make sure that doesn't play a role.
>>>>> 
>>>>> regards,
>>>>> Wei Yang  |  [log in to unmask]  |  650-926-3338(O)
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On Aug 11, 2011, at 5:18 AM, Doug Benjamin wrote:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> I am trying to understand why my use of xrdalder32 command is failing.
>>>>>> 
>>>>>> I have a file in xrootd storage -
>>>>>> I can see it from the redirector 
>>>>>> 
>>>>>> [root@wnode01 ~]# xrd hnode.atlaspitt:1094 locateall /atlas/local/bdouglas/data11_7TeV.00180224.physics_Egamma.merge.NTUP_EGAMMA.f368_m806_p536_tid327358_00/NTUP_EGAMMA.327358._000001.root.1
>>>>>> 
>>>>>> 
>>>>>> ------------- Location #1
>>>>>> InfoType: kXrdcLocDataServer
>>>>>> CanWrite: true
>>>>>> Location: '192.168.100.101:1094'
>>>>>> 
>>>>>> Yet I get this result from xrdalder32
>>>>>> 
>>>>>> [root@wnode01 ~]# /usr/bin/xrdadler32  root://hnode.atlaspitt:1094//atlas/local/bdouglas/data11_7TeV.00180224.physics_Egamma.merge.NTUP_EGAMMA.f368_m806_p536_tid327358_00/NTUP_EGAMMA.327358._000001.root.1
>>>>>> Error_accessing root://hnode.atlaspitt:1094//atlas/local/bdouglas/data11_7TeV.00180224.physics_Egamma.merge.NTUP_EGAMMA.f368_m806_p536_tid327358_00/NTUP_EGAMMA.327358._000001.root.1
>>>>>> 
>>>>>> I get a similar error when I query the data server with the file :
>>>>>> 
>>>>>> [root@wnode01 ~]# /usr/bin/xrdadler32  root://wnode01.atlaspitt:1094//atlas/local/bdouglas/data11_7TeV.00180224.physics_Egamma.merge.NTUP_EGAMMA.f368_m806_p536_tid327358_00/NTUP_EGAMMA.327358._000001.root.1
>>>>>> Error_accessing root://wnode01.atlaspitt:1094//atlas/local/bdouglas/data11_7TeV.00180224.physics_Egamma.merge.NTUP_EGAMMA.f368_m806_p536_tid327358_00/NTUP_EGAMMA.327358._000001.root.1
>>>>>> 
>>>>>> Yet when I query the actual file on disk:   the xrdalder32 succeeds.
>>>>>> 
>>>>>> [root@wnode01 ~]# /usr/bin/xrdadler32  /local/xrootd/a/atlas/local/bdouglas/data11_7TeV.00180224.physics_Egamma.merge.NTUP_EGAMMA.f368_m806_p536_tid327358_00/NTUP_EGAMMA.327358._000001.root.1
>>>>>> d26e385b /local/xrootd/a/atlas/local/bdouglas/data11_7TeV.00180224.physics_Egamma.merge.NTUP_EGAMMA.f368_m806_p536_tid327358_00/NTUP_EGAMMA.327358._000001.root.1
>>>>>> 
>>>>>> Am I doing something wrong or did I find an undocumented feature.
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> Doug Benjamin
>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>