From: CERN / AsiaPacific
To: SouthEast Europe / Italy
Issues from AsiaPAcific ROC:
Seems CIC dashboard was not stable this week, we encountered problems to access it for many times during Taiwan's work time(+8).
The error msg showed "Data source is unreachable" on dashboard.
23 Jan: An issue regard to "open ticket for the node not in production", it was sent to CIC mail list but no any responses for now. Detail:
We are the lead team (Taiwan) this week. There is one thing need to consult with you. We found that there is a attribute for node as below on GOCDB.
Production status: Not in production.
Site admin can decide if put their node in production or not. But Gstat does not check it for now and seems has the same situation on SAM. So we as COD would see a failed alarm for the node that site admin put it in "Not in production" but still switch on the monitor of it. How to deal with this knid of situation?
Should we not to open ticket for the node not in production? In this case CIC dashboard may provide us the information in the alarm.
For detail please see the ticket #7169
In this ticket site admin suggested us should not open ticket for the node
"Not in production".
Any comments about this?
In fact every nodes from a production site are supposed to be in production .
That is the case now in GOC DB . You could not disable monitoring for nodes of a production site . I've sent a mail to COD people to explain what to do for the moment with these nodes.
Since the last update of GOC DB some old nodes with monitoring off in
the previous version are now monitored. And this is now not possible to switch off the monitoring on nodes for a production site.
Consequently site admins must delete now in GOCDB all old nodes which are not used anymore. And these nodes must be removed from the information system in order not to be monitored by SAM. In case of differences between GOC DB and BDII , a node is registered in the BDII and not in GOC BD , or a node is not in the GOC DB but in the BDII , you must open a ticket to inform site about it.
Either site admin register these nodes into both BDII and GOC DB and
eventually put a downtime , either they must delete nodes from GOC DB