Paul Millar

@drfalken , Thanks for reporting your experience. When you say you're seeing "the same issue", is this the occasional missing information that Chris originally reported, or the complete absence of...

Hi guys, Sorry for the delay ... I was off on holiday. WOW! There's a lot to say about this issue. I've broken this down into sections, to make it...

Thanks for reporting this @calestyo. I've created some tickets to manage the transition to supporting Python v3.

Thanks for reporting this problem. The problem appears to be with a file that a client wrote using the WebDAV door. Does that correspond you what you know about this...

Hi @XMol, Thanks for reporting this. The log entries mentioned `RemoteTransferManager@remoteTransferManagerDomain`, so it looks like the WebDAV door is trying to contact a specific RTM cell, rather than the generic...

> Here is where I shut down the WebDAV door and the first messages after it was started again: Thanks. The first stack-trace (`Unexpected exception during shutdown`) is unexpected. It...

@vingar, Thanks for letting us know. At first blush, this sounds like an unrelated problem. Could you open a fresh issue for this? Cheers, Paul.

@XMol, The shutdown shouldn't generate any stack-traces (stack-traces == bugs) .. but I probably would need some more information to figure out what is going wrong. I'd say we leave...

This sounds very familiar: see eu-emi/canl-java#92. Previously, the problem was triggered by a CA changing their signing algorithm (from SHA-1 to SHA-256) without changing other aspected. This resulted in CaNL...

The fix involves a major version upgrade for CaNL. We are (naturally) being rather cautious about back-porting this to our stable branches. The current status is that the upgrade has...