Hi list,
Over the past week our network has been dying a slow and painful
death, with random application crashes. Seems something finally gave
up the ghost this week, and now all of our machines lock up when
trying to browse /Network in Finder. All home folders are mounted
over NFS, which seems to be causing the crashes, but nothing about the
configuration has changed in the past three weeks.
If I SSH into a machine and trigger the crash, I can follow system.log
and see the following appear:
Mar 3 20:42:21 news3 automount[187]: objc: FREED(id): message
newServiceWithName:service:serviceURL: sent to freed object=0x180e800
Mar 3 20:42:34 news3 kernel[0]: nfs server automount -nsl [187]: not responding
Mar 3 20:42:34 news3 kernel[0]: nfs server automount -nsl [187]: not responding
Mar 3 20:42:34 news3 KernelEventAgent[33]: tid 00000000 received
VQ_NOTRESP event (1)
Mar 3 20:42:34 news3 KernelEventAgent[33]: tid 00000000 type 'nfs',
mounted on '/Network', from 'automount -nsl [187]', not responding
Mar 3 20:43:05 news3 kernel[0]: nfs server automount -nsl [187]: not responding
Mar 3 20:43:05 news3 kernel[0]: nfs server automount -nsl [187]: not responding
Mar 3 20:43:36 news3 kernel[0]: nfs server automount -nsl [187]: not responding
Mar 3 20:43:36 news3 kernel[0]: nfs server automount -nsl [187]: not responding
The only way to get the machine back is a hard power cycle. Has
anyone seen this issue before? Regardless of if what is causing it is
under my domain, there should never be a case where automount
double-frees an object, so I've already filed this as rdar #5778638.
Upgrading to 10.5 and ditching automount altogether, while very
appealing, is out of the question.
Thanks,
--Kyle Sluder
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden