Hi Everyone
Thanks for your reply. As only one out of three partition on the pool node got disabled so chances are that it is not related to any service common to all partition. As Marcus suggested I am running dpm-disk-to-dpns on that particular pool to get list of files before putting it back online. The command is running and listing files but I am getting lots of these errors
send2nsd: Error during lookup of t2se01.physics.ox.ac.uk: Temporary failure in name resolution
Could not get virtual id for /C=UK/O=eScience/OU=Oxford/L=OeSC/CN=t2se01.physics.ox.ac.uk: No user mapping !
send2nsd: NS002 - send error : client_establish_context: The expected name of the server is not available
send2nsd: Error during lookup of t2se01.physics.ox.ac.uk: Temporary failure in name resolution
send2nsd: Error during lookup of t2se01.physics.ox.ac.uk: Temporary failure in name resolution
send2nsd: NS002 - send error : client_establish_context: The expected name of the server is not available
send2nsd: Error during lookup of t2se01.physics.ox.ac.uk: Temporary failure in name resolution
send2nsd: NS002 - send error : client_establish_context: The expected name of the server is not available
send2nsd: NS002 - send error : client_establish_context: The expected name of the server is not available
t2se01 is our head node and command is running on t2se01 itself. Again the same question, has anyone seen this error?
Cheers
Kashif
________________________________________
From: Testbed Support for GridPP member institutes [[log in to unmask]] on behalf of RAUL H C LOPES [[log in to unmask]]
Sent: Thursday, March 16, 2017 1:53 PM
To: [log in to unmask]
Subject: Re: dpm pool node
Hi Kashif,
I may have seen it in the following conditions:
- HN couldn't ping the pool node for some time. Then it goes in
'DISABLED' and stays like that even if the network becomes stable again.
- A service dead in the pool node.
- Security issues, like SElinux block in either side.
- times not sync'ed between HN and poool node.
Thanks, raul
On 16/03/17 12:13, Kashif Mohammad wrote:
> Hi
>
> I noticed that in our dpm setup, one partition of a pool node has become 'disable' by itself
>
> dpm-qryconf --si
> ....
> t2se35.physics.ox.ac.uk /dpm/pool3 CAPACITY 6.48T FREE 133.54G ( 2.1%)
> t2se36.physics.ox.ac.uk /dpm/pool1 CAPACITY 6.50T FREE 130.55G ( 2.0%)
> t2se36.physics.ox.ac.uk /dpm/pool2 CAPACITY 6.50T FREE 130.59G ( 2.0%)
> t2se36.physics.ox.ac.uk /dpm/pool3 CAPACITY 0 FREE 175.99k ( 0.0%) DISABLED
> t2se37.physics.ox.ac.uk /dpm/pool1 CAPACITY 6.50T FREE 130.42G ( 2.0%)
> t2se37.physics.ox.ac.uk /dpm/pool2 CAPACITY 6.50T FREE 131.01G ( 2.0%)
>
> I can not see any error at server or at pool node. Has some one seen it earlier and what is best way to enable it ?
>
> Thanks
>
> Kashif
