-
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
dbg option in http.secxtractor causes stuck of HTTP protocol initialization #1245
Comments
Could you attach gdb and do:
thread apply bt all
and send me the output? It will be too large to post. If you need more
specific instructions on how to capture the backtrace I can supply that.
Andy
…On Wed, 8 Jul 2020, riccardodimaria wrote:
Hi,
while testing XRootD HEAD I noticed that one of the options I was using before for http.secxtractor directive causes now stuck of the HTTP protocol initialization.
In particular, setting:
`http.secxtractor libXrdSecgsiVOMS.so vos=atlas,cms,escape,dteam|grpopt=02|dbg`
results in an unfinished log in the cache as:
`Plugin unreleased XrdHttpProtocolTest v20200708-9364927 is using unreleased XrdVomsHttp v20200708-9364927 version in secxtractorlib libXrdSecgsiVOMS-5.so
200708 17:24:10 21406 XrdVomsInit: ++++++++++++++++++ VOMS plug-in +++++++++++++++++++++++++++++++
200708 17:24:10 21406 XrdVomsInit: +++ proxy fmt: raw
200708 17:24:10 21406 XrdVomsInit: +++ group option: all of all groups
200708 17:24:10 21406 XrdVomsInit: +++ group(s): <not specified>
200708 17:24:10 21406 XrdVomsInit: +++ VO(s): atlas,cms,escape,dteam
200708 17:24:10 21406 XrdVomsInit: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++`
The removal of option `|dbg` results in the success of the HTTP protocol initialization, and hence of the cache, otherwise stuck.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#1245
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
|
To be honest, I am quite new to GDB. So not sure what I did is correct. Please tell me otherwise.
The file attached contains the output of these 2 actions. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
while testing XRootD HEAD I noticed that one of the options I was using before for http.secxtractor directive causes now stuck of the HTTP protocol initialization.
In particular, setting:
http.secxtractor libXrdSecgsiVOMS.so vos=atlas,cms,escape,dteam|grpopt=02|dbg
results in an unfinished log in the cache as:
The removal of option
|dbg
results in the success of the HTTP protocol initialization, and hence of the cache, otherwise stuck.The text was updated successfully, but these errors were encountered: