You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 @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:
how (precisely - no time to dig in source code of an integration) canl is configured
what is a call to canl lib method, and with what input
what error is generated by canl and what would be expected.
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.
The text was updated successfully, but these errors were encountered: