Closed Plopix closed 7 years ago
Please see the readme and provide all information for submitting a ticket
I have been using d4m since almost the beginning my installation is correct. I think it might be a last update on Mac OS X that can break the export or something,
I am curious if some people are in the same case.
$ mount -t nfs 127.0.0.1:/Users/plopix/DOCKFILES /tmp/plop
mount_nfs: can't mount /Users/plopix/DOCKFILES from 127.0.0.1 onto /private/tmp/plop: RPC prog. not avail
It sounds like something weird with RPC
We have no idea what mac version, docker, or anything based on what you submitted.
First thank you for your reactivity :)
Docker: Version 17.03.0-ce-mac2 (15654) Mac OS Sierra: 10.12.3 (16D32)
$ cat /etc/exports
/Users/plopix/DOCKFILES -mapall=plopix:staff localhost
That is when I try manually, using d4m it loops here: https://github.com/IFSight/d4m-nfs/blob/master/d4m-nfs.sh#L144
I think that is something related to Mac OS more than d4m .. but I bet people are going to have to same one:
extract from log:
Mar 24 12:44:16 PlopixUSMBP com.apple.xpc.launchd[1] (com.apple.nfsd[1048]): Service did not exit 5 seconds after SIGTERM. Sending SIGKILL.
Mar 24 12:46:28 PlopixUSMBP com.apple.xpc.launchd[1] (com.apple.lockd[1157]): Service exited with abnormal code: 1
PlopixUSMBP:~ root# ps axu | grep rpcbind
root 1493 0.4 0.0 2442020 1864 s001 S+ 12:52PM 0:00.00 grep rpcbind
daemon 729 0.0 0.0 2515740 4364 ?? Ss 12:36PM 0:00.03 /usr/sbin/rpcbind
PlopixUSMBP:~ root# rpcinfo -u localhost nfs
Can't contact rpcbind on localhost
rpcinfo: RPC: Unknown host
PlopixUSMBP:~ root# rpcinfo localhost
Can't contact rpcbind on localhost
rpcinfo: RPC: Unknown host
PlopixUSMBP:~ root# rpcinfo 127.0.0.1
program version netid address service owner
100000 2 udp 0.0.0.0.0.111 rpcbind root
100000 3 udp 0.0.0.0.0.111 rpcbind root
100000 4 udp 0.0.0.0.0.111 rpcbind root
100000 2 tcp 0.0.0.0.0.111 rpcbind root
100000 3 tcp 0.0.0.0.0.111 rpcbind root
100000 4 tcp 0.0.0.0.0.111 rpcbind root
100000 2 udp6 ::.0.111 rpcbind root
100000 3 udp6 ::.0.111 rpcbind root
100000 4 udp6 ::.0.111 rpcbind root
100000 2 tcp6 ::.0.111 rpcbind root
100000 3 tcp6 ::.0.111 rpcbind root
100000 4 tcp6 ::.0.111 rpcbind root
100024 1 udp 0.0.0.0.2.97 status root
100024 1 udp6 ::.3.188 status root
100024 1 tcp 0.0.0.0.3.253 status root
100024 1 tcp6 ::.3.251 status root
100021 0 udp 0.0.0.0.3.237 nlockmgr root
100021 1 udp 0.0.0.0.3.237 nlockmgr root
100021 3 udp 0.0.0.0.3.237 nlockmgr root
100021 4 udp 0.0.0.0.3.237 nlockmgr root
100021 0 udp6 ::.3.121 nlockmgr root
100021 1 udp6 ::.3.121 nlockmgr root
100021 3 udp6 ::.3.121 nlockmgr root
100021 4 udp6 ::.3.121 nlockmgr root
100021 0 tcp 0.0.0.0.3.201 nlockmgr root
100021 1 tcp 0.0.0.0.3.201 nlockmgr root
100021 3 tcp 0.0.0.0.3.201 nlockmgr root
100021 4 tcp 0.0.0.0.3.201 nlockmgr root
100021 0 tcp6 ::.3.196 nlockmgr root
100021 1 tcp6 ::.3.196 nlockmgr root
100021 3 tcp6 ::.3.196 nlockmgr root
100021 4 tcp6 ::.3.196 nlockmgr root
PlopixUSMBP:~ root# rpcinfo -u 127.0.0.1 nfs
Can't contact rpcbind on 127.0.0.1
rpcinfo: RPC: Program not registered
PlopixUSMBP:~ root#
Can you review your "App Store" > "Updates" and list the time your system last had an OS patch.
Also, this is a bit more risky on your end, but I am using Docker for mac 1.13 -- You can try downgrade to it via https://download.docker.com/mac/stable/1.13.0.15072/Docker.dmg and see if you have the issue or not still.
Last update was Twitter and iTunes (3x times since Mar 22, 2017)
But do you think it is related to Docker? Because even locally I can not mount my export.
:/
Have you tried rebooting recently? We have seem odd instances of docker getting hung and bounded and a reboot was the only solution for it.
yes I have multiple times. Looking to see if I can not install NFS through brew as it seems related more to the Mac but I have no clue why.
Can you do: rpcinfo -p
what does that do for you?
rpcinfo -p
program vers proto port
100000 2 udp 111 portmapper
100000 3 udp 111 portmapper
100000 4 udp 111 portmapper
100000 2 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 4 tcp 111 portmapper
100024 1 udp 746 status
100024 1 tcp 1019 status
100021 0 udp 906 nlockmgr
100021 1 udp 906 nlockmgr
100021 3 udp 906 nlockmgr
100021 4 udp 906 nlockmgr
100021 0 tcp 1015 nlockmgr
100021 1 tcp 1015 nlockmgr
100021 3 tcp 1015 nlockmgr
100021 4 tcp 1015 nlockmgr
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100005 1 udp 827 mountd
100005 3 udp 827 mountd
100005 1 tcp 732 mountd
100005 3 tcp 732 mountd
100011 1 udp 739 rquotad
100011 2 udp 739 rquotad
100011 1 tcp 722 rquotad
100011 2 tcp 722 rquotad
Mac: 10.11.6 Docker for mac: Version 1.13.0 (15072) Channel: Stable 0c6d765c54
Well I think I am on my own for now then. I don't have this return and it is probably why I can't mount and then MobyVM can not mount either...
Got it ! Please don't laugh I lost my morning on that... That is crazy .. my /etc/hosts was empty....
Unknown host
it was written...
But how! how can /etc/hosts can empty... I don't know cause it is file managed by root..
Anyway I feel better.
For those to who it happens, for any reason, default /etc/hosts is:
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
@Plopix glad to hear you figured it out! Don't think we do anything with /etc/hosts in d4m-nfs.
Hello guys, suddently, probably after an update or something it does not work anymore.
On my mac:
Do you have an idea?