Following the discussion related to #8080, I've set AL and RP for the namespaces of experiments we at KIT host. Since this action takes long and in case it is performed in running mode, some files ended up without appropriate AL and RP, it seems.
While this is a separate issue, it seems like this leads to a crash of admin interface on rep ls, see:
[dccmsadmin-e] (PnfsManager@pnfsManager-dccmscore-eDomain) admin > \c f01-124-153-e_D_cms
[dccmsadmin-e] (f01-124-153-e_D_cms@f01-124-153-e_D_cmsDomain) admin > rep ls
Command 'rep ls' triggered a bug (java.lang.IllegalStateException: Attribute is not defined: ACCESS_LATENCY); the service log file contains additional information. Please contact support@dcache.org.
Corresponding log entry for the pool:
26 Jun 2026 11:17:01 (f01-124-153-e_D_cms) [] Command failed due to a bug, please contact support@dcache.org.
java.lang.IllegalStateException: Attribute is not defined: ACCESS_LATENCY
at org.dcache.vehicles.FileAttributes.guard(FileAttributes.java:335)
at org.dcache.vehicles.FileAttributes.getAccessLatency(FileAttributes.java:393)
at org.dcache.pool.repository.RepositoryInterpreter$ListCommand.listAll(RepositoryInterpreter.java:327)
at org.dcache.pool.repository.RepositoryInterpreter$ListCommand.execute(RepositoryInterpreter.java:303)
at dmg.util.command.DelayedCommand.run(DelayedCommand.java:48)
at java.base/java.lang.Thread.run(Thread.java:1583)
This makes it a bit more difficult to debug that. Maybe it is worth safe-guarding the access to AL and RP here:
https://github.com/dCache/dcache/blob/11.2.4/modules/dcache/src/main/java/org/dcache/pool/repository/RepositoryInterpreter.java#L327-L328
And in other, similar places?
Following the discussion related to #8080, I've set AL and RP for the namespaces of experiments we at KIT host. Since this action takes long and in case it is performed in running mode, some files ended up without appropriate AL and RP, it seems.
While this is a separate issue, it seems like this leads to a crash of admin interface on
rep ls, see:Corresponding log entry for the pool:
26 Jun 2026 11:17:01 (f01-124-153-e_D_cms) [] Command failed due to a bug, please contact support@dcache.org. java.lang.IllegalStateException: Attribute is not defined: ACCESS_LATENCY at org.dcache.vehicles.FileAttributes.guard(FileAttributes.java:335) at org.dcache.vehicles.FileAttributes.getAccessLatency(FileAttributes.java:393) at org.dcache.pool.repository.RepositoryInterpreter$ListCommand.listAll(RepositoryInterpreter.java:327) at org.dcache.pool.repository.RepositoryInterpreter$ListCommand.execute(RepositoryInterpreter.java:303) at dmg.util.command.DelayedCommand.run(DelayedCommand.java:48) at java.base/java.lang.Thread.run(Thread.java:1583)This makes it a bit more difficult to debug that. Maybe it is worth safe-guarding the access to AL and RP here:
https://github.com/dCache/dcache/blob/11.2.4/modules/dcache/src/main/java/org/dcache/pool/repository/RepositoryInterpreter.java#L327-L328
And in other, similar places?