On Mon, 2005-11-21 at 11:25, Graeme Stewart wrote:
>
> Try running the openssl command on hostkey.pem too. In particular check the
> "Subject Key Identifier"s match in both cases.
Yeah, I checked that - the two "Subject Key Identifier"s are identical.
> > > > Starting rgma-servicetool: Site name is changeme.invalid - please
> > > > change to actual site name
>
> That looks ok. Have you restarted RGMA?
The file I had to modify to kick that error message out was:
/opt/glite/etc/rgma-servicetool/servicetool.conf
After that RGMA part is okay now.
> Actually perhaps not. I see that our RGMA, after the upgrade, is bound to
> 8443, which is the DPM srmv1 port. You could switch RGMA back to insecure (in
> which case it should revert to 8080), but eventually I think that RGMA will
> require a secure install, and probably require port 8443 too.
I don't think RGMA has started using 8443 here yet.
http://serv02.hep.phy.cam.ac.uk:8080/ prints the tomcat page so I it's
still in use. What are the impacts for the sites co-locating R-GMA, MON
and DPM box?
Thanks,
Santanu
|