Print

Print


Hi,

You should be able to disable the production+monitored statuses from the service in GOCDB. APEL only requires that you have a service in GOCDB with the correct DN, not that it's set to production. This should be the same for the message brokers.

Regards,
Adrian Coveney
(APEL person)


-----Original Message-----
From: Testbed Support for GridPP member institutes [mailto:[log in to unmask]] On Behalf Of Mark Slater
Sent: 24 June 2019 14:23
To: [log in to unmask]
Subject: APEL and VAC

Hi All,


So it turns out that when you go full VAC (oo-er) and turn off/remove 
your APEL box from GOCDB (which would be pointless because VAC does it's 
own transfer of accounting records) you hit a problem that you no longer 
get any accounting because the APEL service can't see an associated 
service in GOCDB. I've just re-added mine but the problem now is that 
I'll almost certainly start getting errors because there is a service 
listed in GOCDB that doesn't exist and isn't contactable. I don't 
suppose anyone has any thoughts about how to get around this or should I 
start knocking on the APEL people's door?


Thanks!


Mark

########################################################################

To unsubscribe from the TB-SUPPORT list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=TB-SUPPORT&A=1

########################################################################

To unsubscribe from the TB-SUPPORT list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=TB-SUPPORT&A=1