Hi Simon,
Have you made the change yet? Something still isn't right. Are you sure
that everything is OK on the DPM head node?
Can you run commands like
dpns-ls /dpm
on it as the root user?
Cheers,
Greig
On 03/01/08 12:14, Simon George wrote:
> btw the pool node with the out of date cert is gridraid3 which is
> currently read-only. So the one used by the SAM test should be gridraid2
> which does have an up-to-date cert.
>
> Do you think this could still cause the error?
>
> I wonder if I should completely disable gridraid3 until the cert is fixed.
>
> Greig Alan Cowan wrote:
>> Hi Simon,
>>
>> Best thing to do is re-run the YAIM configuration step.
>>
>> /opt/glite/yaim/bin/yaim -c -s /path/to/site-info.def -n SE_dpm_mysql
>>
>> That should do the trick and make sure all the certificates are in the
>> right place with the right permissions etc.
>>
>> You should also think about upgrading to the latest version of DPM
>> (1.6.7). More about that in a forthcoming email...
>>
>> Cheers,
>> Greig
>>
>> On 03/01/08 11:49, Simon George wrote:
>>> Hi Greig,
>>>
>>> thanks for your quick reply.
>>> I've checked, all the CRLs are up to date. The host certificates are
>>> up to date as in:
>>>
>>> openssl x509 -in /etc/grid-security/hostcert.pem -dates -text|head -2
>>> notBefore=Oct 5 11:25:32 2007 GMT
>>> notAfter=Nov 3 11:25:32 2008 GMT
>>>
>>> But I've noticed that on the pool node, this certificate is not
>>> propagated to /etc/grid-security/dpmmgr/dpmcert.pem
>>> (nor the corresponding key file). The files there are old and have
>>> expired.
>>>
>>> Is it just a case of copying these new certificate files to
>>> dpmmgr/dpmcert.* or do I need to do something else too?
>>>
>>> Thanks,
>>> Simon
>>>
>>>
>>> Greig Alan Cowan wrote:
>>>> Hi Simon,
>>>>
>>>> It looks like a security issue. Are the certificates and CRLs up
>>>> to date?
>>>>
>>>> Cheers,
>>>> Greig
>>>>
>>>>
>>>>
>>>> On 03/01/08 10:44, Simon George wrote:
>>>>> Hi,
>>>>>
>>>>> I have the problem described here:
>>>>> http://www.gridpp.ac.uk/wiki/Random_DPM_errors_in_SAM#Error_reading_token_data
>>>>>
>>>>>
>>>>> Does anyone know the solution to this?
>>>>>
>>>>> For example:
>>>>> https://lcg-sam.cern.ch:8443/sam/sam.py?funct=TestResult&nodename=ce1.pp.rhul.ac.uk&vo=ops&testname=CE-sft-lcg-rm-cr&testtimestamp=1199352207
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Simon
|