-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xrdcp/3.2 complains for a certificate error, while xrdcp/4.0 crashes #136
Comments
Nope, it's not known. I will have a look. |
Any chance you can reproduce with debug symbols installed? |
Or a valgrind trace (also with debug symbols)? |
problematic, since this is production machine where I cannot install stuff (and valgrind is not there...) let me see if I can find a more "friendly" machine with the same version installed ... tom |
in the end, since I do not have a similar machine I can tweak, I asked brian if he can reproduce it + provide debug. stay tuned, and sorry if I am not of much help here ... tom |
No worries, thanks for spotting and reporting! |
Hi, Here's what I got from valgrind:
This happened with 4.0.3 (fresh from xrootd.org) and did not happen with the 4.0.0 pre-release that I used to have on my development host. I think (but am not sure) it happens before authorization is finished (meaning Lukasz could probably reproduce this too). |
Merci! |
It's gets a malformed kXR_error response and my retarded code does not seem to compensate. Will fix. Thanks for reporting. |
Hi Lukasz, Please document the malformed response so we can fix that in the server. Andy On Thu, 4 Sep 2014, Lukasz Janyst wrote:
|
The response is OK, I just made a silly mistake when allocating a buffer for the error message. |
Ciao, I was trying to debug a problem in a server (gridtutorial8.ba.infn.it), which results in xrdcp/3.2. (as shipped by CMS) in
--->
ok, probably there is a problem with certificate chain, we will look into it.
But then I tried with a newer xrdcp (as shipped by xrootd4-client-4.0.3-1.slc6.x86_64)
there I get as below. Error is the same (certificate problems, but then a segfault ...)
Is it known?
thanks
tom
The text was updated successfully, but these errors were encountered: