If there were anything it would probably be in
/var/log/dpm/log.*
certainly a No route to host
maybe in dpm_getpoolconf
maybe also something about the disabling. (Ah but I see you say the last time it says disabled was not recent...)
I think I've only seen this if the pool was not contactable when dpm was starting....
Wahid
On 10 Mar 2011, at 12:02, Simon George wrote:
> Thanks Sam. Any idea how this would be logged on the head node if it happened?
>
> Sam Skipsey <[log in to unmask]> wrote:
>
>> Hi Govind,
>>
>>
>> On 10 March 2011 10:15, Govind Songara <[log in to unmask]> wrote:
>>> Hi,
>>> We found that one of our pool node got disabled itself which triggers some
>>> job failures.
>>> As per dpm log it was disabled in last time in January.
>>> Does any one have noticed similar behavior.
>>
>> This can happen if the head node has persistent issues in talking to a
>> given pool node, I believe. (I've seen it happen once before.)
>>
>> Sam
>>
>>> Thanks
>>> Govind
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
|