The only thing I see in the config file is that you are exporting gpfs. Is it possible that gpfs gets overloaded at some point due to activity other than xroot? For instance, we do know that gps can become very slow when backups happen or some other job (other than xroot) is writing a lot of small files. The log appears to imply this is what is happening. We can do a deeper analysis by looking at what each thread is doing. This can be done online or offline.
offline: Generate a core file of stalled xroot using the gcore command.
online: You will have to attach gdb to the stalled process
In either case, please make sure you have installed the debug xroot RPM package so that we get statement numbers in the following steps:
If you have generated a gcore then use gdb to look at it if you've done the online step then you ae already in gdb. Either way, do the following:
(gdb) set logging on
{gdb} set logging redirect on
(gdb) thread apply all bt
This will generate a full back trace for each thread and write it to gdb.txt. This will take some time if there are many threads and the file could be very large.
Once this is done, please send a link to where we can download the resulting file and then we can see what is going on.
--
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/1799#issuecomment-1305872129
You are receiving this because you commented.
Message ID: <[log in to unmask]>
########################################################################
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
