Dear *,
Bristol's been ticketed for bdii publishing.
https://ggus.eu/index.php?mode=ticket_info&ticket_id=109314
-----------
*ALARM #0
-----------
created_at : 2014-10-13 04:30:55
test_name : org.bdii.GLUE2-Validate
host_name : lcgbdii02.phy.bris.ac.uk
service : Site-BDII
status : Nagios critical
nagios_info :
https://midmon.egi.eu/nagios/cgi-bin/extinfo.cgi?host=lcgbdii02.phy.bris.ac.uk&type=2&service=org.bdii.GLUE2-Validate
When I look at this I see no critical it's only yellow:
lcgbdii02.phy.bris.ac.uk org.bdii.GLUE2-Validate WARNING - errors 0,
warnings 44, info 546
What is this "critical" they're talking about? Also many others seem
similar:
bdii02.esc.qmul.ac.uk org.bdii.GLUE2-Validate WARNING - errors 0, warnings
140, info 148
epgr09.ph.bham.ac.uk org.bdii.GLUE2-Validate WARNING - errors 0, warnings
20, info 253
fal-pygrid-14.lancs.ac.uk org.bdii.GLUE2-Validate WARNING - errors 0,
warnings 14, info 102
hepgrid4.ph.liv.ac.uk org.bdii.GLUE2-Validate WARNING - errors 0, warnings
256, info 749
No tickets for those? Anyway looking into it the first one is
I012 - Unknown VO name in share (GLUE2EntityOtherInfo): 2
Ok,
lacesso@pplxint8> ldapsearch -x -H ldap://lcgbdii02.phy.bris.ac.uk:2170 -b GLUE2DomainID=UKI-SOUTHGRID-BRIS-HEP,o=glue > bris.141015
Is that the correct ldapsearch command? If not corrections most welcome!
Assuming it is,
lacesso@pplxint8> grep GLUE2EntityOtherInfo bris.141015 | grep -i vo | wc -l
0
No string "vo" in any GLUE2EntityOtherInfo value.
So has anyone got any advice how to debug "Unknown VO name in share
(GLUE2EntityOtherInfo)" ?
Winnie Lacesso / Bristol University Particle Physics Computing Systems
HH Wills Physics Laboratory, Tyndall Avenue, Bristol, BS8 1TL, UK
|