 |
 |
Hi Gregory, > 041217 14:43:22 035 XrootdXeq: User logged in as gregor.9191:38@lnx243 > 041217 14:43:44 036 XrootdXeq: User logged in as gregor.8748:39@sol184 > 041217 14:45:11 037 XrootdXeq: User logged in as gregor.3086:40@sol199 > 041217 14:45:21 038 XrootdXeq: User logged in as gregor.26617:41@lnx6211 > 041217 14:45:22 038 XrootdXeq: User logged in as gregor.9191:42@lnx243 > 041217 14:45:44 038 XrootdXeq: User logged in as gregor.8748:43@sol184 > 041217 14:47:11 038 XrootdXeq: User logged in as gregor.3086:44@sol199 > 041217 14:47:21 038 XrootdXeq: User logged in as gregor.26617:45@lnx6211 > 041217 14:47:22 038 XrootdXeq: User logged in as gregor.9191:46@lnx243 > 041217 14:47:44 038 XrootdXeq: User logged in as gregor.8748:47@sol184 > 041217 14:49:11 038 XrdScheduler: Thread limit has been reached! > 041217 14:49:11 038 XrootdXeq: User logged in as gregor.3086:48@sol199 Given the timing and the fact that the thread limit was reached is indicative of someone not releasing a lock. A dbx/gdb traceback would identify which lock is the one in question. Possible to do? Andy