Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @


From EGIWiki
Jump to navigation Jump to search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators


General information


CREAM End Of Support Notice

Preview repository




Feedback from DMSU

Notifications from ARGO about the nagios probes failures

In the process of implementing the notification system in ARGO, it was introduced the following changes in GOC-DB:

  • Notifications flag at the site level
  • Notifications flag at the service endpoint level

In this way ARGO will retrieve from GOC-DB the information about the sites and services whom sending the email notification and the related recipients.

The logic of the notifications is the following:

Site Service Notify?

If there isn't any email contact defined at the service endpoint level, it will be used the site contact. Please review your contacts.

You can enable the notifications.

NOTE: It is not mandatory for the sites

Verify configuration records

On a yearly basis, the information registered into GOC-DB need to be verified. NGIs and RCs have been asked to check them. In particular:

  1. NGI managers should review the people registered and the roles assigned to them, and in particular check the following information:
    • E-Mail
    • ROD E-Mail
    • Security E-Mail
NGI Managers should also review the status of the "not certified" RCs, in according to the RC Status Workflow;
  1. RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information:
    • E-Mail
    • telephone numbers
    • CSIRT E-Mail
RC administrators should also review the information related to the registered service endpoints.

The process should be completed by June 21th.

Tickets to track the process are listed here

  • 12 SOLVED, 4 In progress (out of 31)

Monthly Availability/Reliability

suspended sites:

IPv6 readiness plans

LCGDM end of support and migration to / enabling of DOME

  • Deployment statistics: 93 sites (108 servers)
$ ldapsearch -x -LLL -H ldap:// -b "Mds-Vo-Name=local,o=grid" '(&(objectClass=GlueSE)(GlueSEImplementationName=DPM))' GlueSEImplementationVersion | grep -i ^glue | sort | uniq -c
    24 GlueSEImplementationVersion: 1.10.0
    34 GlueSEImplementationVersion: 1.12.0
     1 GlueSEImplementationVersion: 1.12.1
    16 GlueSEImplementationVersion: 1.8.10
     2 GlueSEImplementationVersion: 1.8.11
     2 GlueSEImplementationVersion: 1.8.7
     4 GlueSEImplementationVersion: 1.8.8
     5 GlueSEImplementationVersion: 1.8.9
    20 GlueSEImplementationVersion: 1.9.0
  • all the sites with older DPM versions than 1.12 are suggested to upgrade to the latest DPM version , following the guide DPM upgrade (chapter 1 Upgrade to DPM 1.10.0 "Legacy Flavour" and chapter 2 Upgrade to DPM 1.10.0 "Dome Flavour")
    • DOME and the old LCGDM (srm protocol) will coexist
  • the upgrade will be followed-up mainly by WLCG
  • EGI Operations will liaise with the non-WLCG sites

HTCondorCE integration

Link to procedure:

GGUS ticket:

Steps status:

webdav probes in CRITICAL profile

In June the webdav probes have been included in the ARGO_MON_CRITICAL profile, so the results of these probes will be taken into account for the A/R figures:

Still to fix:

Storage accounting deployment

During the September 2017 meeting, OMB has approved the full-scale deployment of storage accounting. The APEL team tested it with a group of early adopters sites, and the results prove that storage accounting is now production-ready.

Storage accounting is currently supported only for the DPM and dCache storage elements therefore only the resource centres deploying these kind of storage elements are requested to publish storage accounting data.

In order to properly install and configure the storage accounting scripts, please follow the instructions reported in the wiki:

IMPORTANT: be sure to have installed the script v1.0.4 (

After setting up a daily cron job and running the accounting software, look for your data in the Accounting Portal: If it does not appear within 24 hours, or there are other errors, please open a GGUS ticket to APEL who will help debug the process.

Test portal:

IMPORTANT: Do not encrypt the storage records with your host certificate, please comment out the “server_cert” variable in sender.cfg

List of sites already publishing and of tickets opened is reported here.

Several sites are not publishing the storage accounting data yet. NGIs please follow-up with the sites the configuration of the script in order to speed-up the process.


Next meeting