14:02:10 I'm trying to work out why one of my machines can't run NFS in a lipkg zone. The nfs/server svc fails because it can't run mountd, and if I run that manually, it exits 1. Comparing a mountd truss from a working machine, everything looks the same up until a name_service_door call, after which the working one looks at nss.conf, and the broken one doesn't. (As shown in the gist at https://gist.github.com/snltd/28639add2108d0a21b4646e7a538f089) I 14:02:10 can't find anything different in the config of the working and non-working hosts, in either the global or local zones. Does anyone have any suggestions? They're both on the same revision of omnios-r151044. 15:13:12 is nss setup to use DNS? default from illumos is files only if omnios hasn't changed that. 17:50:29 Yes. Everything else works as expected in every other zone on the box, but no zone can start mountd. 17:57:40 blepe: I would make sure, that the own local name and IP are correctly resolved back and forward, check with the tool "getent" 17:57:51 getent hosts thezonemachinename 17:58:00 and getent hosts ip_of_zonemachinename 19:48:37 That was it! The DNS for the new box hadn't propagated. I didn't realise NFS and DNS were quite so tightly tangled. Thank you. 19:51:56 NFS and DNS are tangled if you use DNS :) Alternatives are /etc/hosts or other nss providers that are configured in /etc/nsswitch.conf 20:07:14 I'm getting NIS+ flashbacks! 20:08:32 no LDAP flashbacks? 20:15:05 No, that's always been someone else's problem :) 20:15:37 XD 20:25:05 blepe: glad to have helped. stumbled more then once into this little oddity with SunOS/Illumos based NFS serving 20:57:29 thanks for givinge 20:57:47 me ldapclient and dns flashbacks