Hi Stuart,
Lancaster got one too (77663), but I set it to solved right away as this
was the *second* ticket that Biomed's sent us with the exact same
symptoms. Either they didn't update their original UI (which is worrying
if they're using to submit their nagios tests) or they're using a
different, un-updated UI (which is still worrying).
Shall we ticket them back?
Cheers,
Matt
Stuart Purdie wrote:
> We've got a group of them in the UK:
>
> 77675
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> biomed UKI-SCOTGRID-GLASGOW SE svr018.gla.scotgrid.ac.uk is not working for th...
> 77665
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> biomed UKI-SOUTHGRID-RALPP SE heplnx204.pp.rl.ac.uk is not working for the bi...
> 77662
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> biomed UKI-LT2-Brunel SE dgc-grid-50.brunel.ac.uk is not working for the...
> 77661
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> biomed UKI-LT2-Brunel SE dc2-grid-64.brunel.ac.uk is not working for the...
> 77460
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> biomed UKI-LT2-QMUL SE se04.esc.qmul.ac.uk is not working for the biom...
> 77008
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> biomed UKI-SOUTHGRID-CAM-HEP SE serv02.hep.phy.cam.ac.uk is not workig for biom
>
> I'm pretty sure that these could be related. Prodceding on that assumption , I examined all the above tickets.
>
> In some of them, the error is that the UI host is refusing to establish a security context, due to signing policy problems. I have updated 77675 to request that the submitter check this.
>
> Because of the 'On solution' default, I've marked it as solved, to notify the submitter. If the ticket disappears forever, or if it turns out to be the UI CA versions, then it strongly suggests that the otehr tickets will be down to the same root problem.
|