Paul Millar

OK, so there's a few things going on here. First, the file is on a pool, but pool-manager didn't select that pool. Unfortunately, we don't know why. Possible reasons include:...

Separate from the underlying problem (which we currently don't understand), there's a compounding problem in that pool-manager only records part of its decision-making progress. The log entry says `Pool to...

Thanks for reporting this @cfgamboa , Could you check whether you have `transfermanagers.enable.db` set to `true` ?

Thanks. My suspicion is that the problem comes from the persistency framework (DataNucleus) rather than from dCache code directly: either because of a bug in DataNucleus or we're somehow using...

@DmitryLitvintsev The code-path corresponds to the monitoring that the WebDAV door does to discover how far a transfer has progressed, in order to send FTS progress information. My guess is...

The `Post-processing failed: No such file or directory` message comes from the error-recovery procedure within dCache. When the WebDAV door detects that a PULL request has failed, it deletes the...

Thanks @vingar for the info. Unfortunately, the cell message queue length is a little tricky to get. It is available from the `System` cell (of the domain hosting the WebDAV...

Two more things: Could you check the domain log file (for domain `webdav2-dcdndoor04_httpsDomain`) to see whether the WebDAV door logged anything about this transfer ... or anything else (out of...

Reconstructed timeline: ``` 10:35:28 Transfer starts 10:35:33 WebDAV queries RTM for progress. 10:35:38 WebDAV queries RTM for progress. 10:35:43 WebDAV queries RTM for progress. 10:35:48 WebDAV queries RTM for progress....

My initial thought was that this problem is due to the race-condition, between the RTM notifying the WebDAV door that the transfer has completed and the WebDAV door discovering this...