XROOTD-L Archives

Support use of xrootd by HEP experiments

XROOTD-L@LISTSERV.SLAC.STANFORD.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michal Kamil Simon <[log in to unmask]>
Reply To:
Support use of xrootd by HEP experiments <[log in to unmask]>
Date:
Fri, 27 Sep 2019 14:07:36 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (95 lines)
Hi Adrian,

Sorry for the delay, which version (or commit) of xrootd is this?

Thanks,
Michal
________________________________________
From: Adrian Sevcenco
Sent: 25 September 2019 23:55
To: Michal Kamil Simon; xrootd-l
Subject: Re: python :: segfault in copyprocess.py

On 9/25/19 6:30 PM, Michal Kamil Simon wrote:
> Hi Adrian,
Hi!

> I don't think the segv is due to the fact you haven't added any jobs,
> at least I cannot reproduce it.
>
> Could you provide a small reproducer and/or a backtrace from your
i managed to have this:
https://cernbox.cern.ch/index.php/s/2G6qByVkoZhp5TC

i hope it is enough... if you need more, could you tell me how can debug
further? maybe a gdb command file?

Thank you!!
Adrian


> coredump?
>
> Cheers,
> Michal
> ________________________________________
> From: Adrian Sevcenco
> Sent: 25 September 2019 09:39
> To: Michal Kamil Simon; xrootd-l
> Subject: python :: segfault in copyprocess.py
>
> Hi Michal! I have a strange occurrence of
> Fatal Python error: Segmentation fault
>
> Thread 0x00007fbab90a4700 (most recent call first):
>     File "/usr/lib64/python3.7/concurrent/futures/thread.py", line 78 in
> _worker
>     File "/usr/lib64/python3.7/threading.py", line 870 in run
>     File "/usr/lib64/python3.7/threading.py", line 926 in _bootstrap_inner
>     File "/usr/lib64/python3.7/threading.py", line 890 in _bootstrap
>
> Current thread 0x00007fbabaa25740 (most recent call first):
>     File
> "/home/adrian/.local/lib/python3.7/site-packages/XRootD/client/copyprocess.py",
> line 145 in run
>     File "/home/adrian/bin/alien.py", line 594 in XrdCopy
>     File "/home/adrian/bin/alien.py", line 451 in ProcessXrootdCp
>     File "/home/adrian/bin/alien.py", line 1051 in ProcessInput
>     File "/home/adrian/bin/alien.py", line 1118 in JAlien
>     File "/usr/lib64/python3.7/asyncio/events.py", line 88 in _run
>     File "/usr/lib64/python3.7/asyncio/base_events.py", line 1771 in
> _run_once
>     File "/usr/lib64/python3.7/asyncio/base_events.py", line 534 in
> run_forever
>     File "/usr/lib64/python3.7/asyncio/base_events.py", line 566 in
> run_until_complete
>     File "/home/adrian/bin/alien.py", line 1199 in main
>     File "/home/adrian/bin/alien.py", line 1203 in <module>
> Segmentation fault (core dumped)
>
> i believe that this happens because the i do run without any job added
> ... of course i could protect the case of no jobs added but maybe can
> upstream check if copy jobs are in queue and if not then give a message
> that "No copy jobs to run" or something?
>
> Thanks!!
> Adrian
>
>
>


--
----------------------------------------------
Adrian Sevcenco, Ph.D.                       |
Institute of Space Science - ISS, Romania    |
adrian.sevcenco at {cern.ch,spacescience.ro} |
----------------------------------------------


########################################################################
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

ATOM RSS1 RSS2