Hi,
I find putting it in the GOCDB and turning the monitoring off seems to
do the trick in cases like this.
You are advertising this machine on your bdii, hence the world knows about it:
lx07:dbauer :-> ldapsearch -x -H
ldap://grid-bdii.physik.uni-wuppertal.de:2170 -b
mds-vo-name=wuppertalprod,o=grid | grep grid-ce5.physik.uni | head
# grid-ce5.physik.uni-wuppertal.de:2119/jobmanager-lcgpbs-dg_med, wuppertalpr
dn: GlueCEUniqueID=grid-ce5.physik.uni-wuppertal.de:2119/jobmanager-lcgpbs-dg_
GlueCEHostingCluster: grid-ce5.physik.uni-wuppertal.de
GlueCEUniqueID: grid-ce5.physik.uni-wuppertal.de:2119/jobmanager-lcgpbs-dg_med
GlueCEInfoHostName: grid-ce5.physik.uni-wuppertal.de
[...]
Daniela
2009/10/15 Torsten Harenberg <[log in to unmask]>:
> Dear all,
>
> I installed a new CE, which I want to use as a next production machine (this
> CE points to RHEL 5 Worker nodes).
>
> I'm still in the phase of installation ATLAS software, so the CE is NOT in
> the GOC DB and is NOT used as a production machine.
>
> However, suddenly SAM tests arrive and this machine:
>
> https://lcg-sam.cern.ch:8443/sam/sam.py?funct=ShowHistory&option=old&sensors=CE&vo=ops&nodename=grid-ce5.physik.uni-wuppertal.de
>
> and as one of those failed, I'm about to receive a ticket.
>
> Why is the machine tested at all?? I cannot set it into downtime, as it is
> not in the GOC DB. And I don't want to have it there as long as I'm still in
> the phase of testing it.
>
> Best regards,
>
> Torsten
>
> --
> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
> <> <>
> <> Dr. Torsten Harenberg [log in to unmask] <>
> <> Bergische Universitaet <>
> <> FB C - Physik Tel.: +49 (0)202 439-3521 <>
> <> Gaussstr. 20 Fax : +49 (0)202 439-2811 <>
> <> 42097 Wuppertal <>
> <> <>
> <><><><><><><>< Of course it runs NetBSD http://www.netbsd.org ><>
>
--
-----------------------------------------------------------
HEP Group
Physics Dep
Imperial College
Tel: +44-(0)20-75947810
http://www.hep.ph.ic.ac.uk/~dbauer/
|