On 08/12/2013 10:46 AM, Dennis van Dok wrote:
> On 12-08-13 09:20, Jean-Michel Barbet wrote:
>> Hello,
>>
>> On newly installed SL6.3 worker nodes, I had problems making gLexec
>> work. I came accross 2 issues :
>
>> b) [gLExec]: Failed to lock
>> gLexec could not acquire a file lock on the local proxy.
>> The local proxy was on an NFS filesystem and I could make it work
>> by disabling the lock in /etc/glexec.conf :
>> [...]
>> input_lock_mechanism = disabled
>
> Hi Jean-Michel,
>
> the default locking mechanism 'flock' is known to give issues on NFS
> system, did you try the alternative 'fcntl' before turning locking off
> altogether?
Thank you Dennis,
Using fcntl fails also :
[gLExec]: Failed to lock
$GLEXEC_CLIENT_CERT=/users/lcg/pltops004/x509up_u102,
$GLEXEC_SOURCE_PROXY=(NULL) or destination proxy.
In /var/log/message, I see :
[...]
Aug 12 11:05:59 nanpcw1 kernel: lockd: cannot monitor nant2fis
[...]
Elements of the NFS config on the worker node :
[root@nanpcw1 ~]# rpm -qa | grep nfs
nfs-utils-lib-1.1.5-4.el6.x86_64
nfs-utils-1.2.3-26.el6.x86_64
ncm-nfs-2.0.0-4.noarch
[root@nanpcw1 ~]# service nfslock status
rpc.statd (pid 1558) is running...
JM
--
------------------------------------------------------------------------
Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: [log in to unmask]
------------------------------------------------------------------------
|