Last modified 3 years ago Last modified on 07/11/17 15:08:13

dCache Tier I meeting July 11, 2017

[part of a series of meetings]

Present, IN2P3(), Sara(), Triumf(), BNL(), NDGF(), PIC(Marc, Elena), KIT(Xavier), Fermi(), CERN()


(see box on the other side)

Site reports


dCache has been running just fine for the past week.

Running without alarms

This problem was reported in RT ticket 9154

The problem is that the default configuration has alarms attempting to connect to localhost, but unless the alarms service is running this spams the log file and even prevents dCache from starting up.

Al has recorded this as GitHub issue #9154.


Marc reported that there were no issues in the past week.

They have seen some pools become disabled due to the known issue writing file metadata; manual intervention was necessary and fixed the problem.

New pools are bought with an additional disk to store pool metadata, so alleviating the problem.

Space reporting

Marc was asking what is the plan for supporting sites, given WLCG move away from SRM for space accounting.

Paul reported that, although current master (dCache v3.2) supports space accounting through GridFTP and WebDAV protocols, it isn't clear what format WLCG is expecting space-accounting information.

Once this has settled, we ( hope to back-port whatever is necessary for sites to support WLCG's new reporting format. If the agreement is for WebDAV, this shouldn't be too big a problem.

Support tickets for discussion

[Items are added here automagically]


Same time, next week.