On 27/01/2010, at 5:40 AM, Mike Weaver wrote: > I'm trying to set up & experiment with the AG 3 Venue Server. Got my > service certificate approved & installed and the Venue Server started > successfully, but can't connect with the Venue Manager. The > relevant part > of the VenueServer.log file looks like this: > > 01/26/10 14:26:52 -1260389520 Hosting ServiceContainer.py:187 > ERROR None > Traceback (most recent call last): > File "/usr/lib/python2.6/site-packages/M2Crypto/SSL/SSLServer.py", > line > 33, in handle_request > request, client_address = self.get_request() > File "/usr/lib/python2.6/SocketServer.py", line 444, in get_request > return self.socket.accept() > File > "/usr/lib/python2.6/site-packages/AccessGrid3/AccessGrid/hosting/ZSI/ > Service > Container.py", line 156, in M2CryptoConnectionAccept > ret = ssl.accept_ssl() > File "/usr/lib/python2.6/site-packages/M2Crypto/SSL/Connection.py", > line > 152, in accept_ssl > return m2.ssl_accept(self.ssl, self._timeout) > SSLError: tlsv1 alert unknown ca > > Seems to say that the CA for my certificate is unknown. Running the > Certificate Manager shows 3 trusted CAs - "DOEGrids CA 1", "ESnet > Root CA 1" > & "Anonymous Certificate Authority" (issued by ANL Futures lab). The > service certificate was issued by the "Access Grid Developers CA". > Did I > miss a step or do something wrong?
Mike, There should be four CA's so one of them is either missing or expired. Could you send a long listing (ls -l) of /etc/AccessGrid3/Config/ CAcertificates please? chris Christoph Willing +61 7 3365 8316 QCIF Access Grid Manager University of Queensland
