Open paulmillar opened 10 months ago
OK, Can you please be bit more specific, about the situation in which canl is not providing this information? I.e. how it is used (API calls) and what is missing in error precisely?
Hi @golbi , Thanks for the quick reply.
Did you see the additional information that @onnozweers posted in the above mentioned dCache issue?
Is this sufficient information to understand the problem?
Hi @paulmillar I was sure I've answered, but it somehow didn't happen. Sorry about that.
So, no it is not very helpful :-) I'd need to get the following pieces of information:
In here... I don't think that canl supports lsc files, so likely there is some integration asking canl to do something basing on the messed up lsc file. It is very hard to decipher what is going on in that.
We have an issue from a dCache admin, that the error message indicating that an LSC file is missing doesn't provide enough information to know which LSC file is expected.
The error message comes from CaNL, so updating CaNL to provide additional information in the error message would seem a natural way to resolve the dCache issue.