On 04/13/2014 06:43 PM, Franco Broi wrote:
This message seems spurious, there have been no network changes and the system has been in operation for many months. I restarted the volume and it worked for a while and crashed in the same way. [2014-04-14 01:17:59.291103] E [nlm4.c:968:nlm4_establish_callback] 0-nfs-NLM: Unable to get NLM port of the client. Is the firewall running on client? patchset: git://git.gluster.com/glusterfs.git signal received: 11 time of crash: 2014-04-14 01:18:29configuration details: argp 1 backtrace 1 dlfcn 1 fdatasync 1 libpthread 1 llistxattr 1 setfsid 1 spinlock 1 epoll.h 1 xattr.h 1 st_atim.tv_nsec 1 package-string: glusterfs 3.4.1 /lib64/libc.so.6(+0x329a0)[0x7f43750899a0] /lib64/libc.so.6(inet_ntop+0x88)[0x7f437514fc88] /usr/lib64/glusterfs/3.4.1/xlator/nfs/server.so(nlm4_establish_callback+0x397)[0x7f436b540467] /usr/lib64/glusterfs/3.4.1/xlator/nfs/server.so(nlm4svc_send_granted+0x308)[0x7f436b540808]
This seems to be fixed through: http://review.gluster.org/#/c/5452/. Thanks, Vijay _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
