FOLLOWUP: automounter oddness on a Solaris 2.3 box
2007-12-25 8:59:00
> > I am having a very odd problem with the automounter on my Solaris 2.3
> > box. If I try to cd to any filesystem on the server "alexandria", I
> > get a "No such file or directory." message after a lengthy pause for
> > timeout:
> >
> > (~) Banjo 30 % cd /stage/src
> > /stage/src: No such file or directory.
> >
> > From this machine I can cd to all of the automounted filesystems on my
> > other servers, and I can connect to alexandria's automounted filesystems
> > from other client machines. All of these servers are running 4.1.4. I
> > can cd into the automounted filesystems from alexandria from my other
> > Solaris 2.x machine (running 2.4) without difficulty. My solaris 2.3
> > machine does have the proper auto.stage NIS MAP:
> >
> > (~) Banjo 41 % ypcat auto.stage | grep src
> > alexandria${SUBNET},alexandria:/export/src
> >
> > Does anyone have any ideas why this machine will not mount these
> > filesystems from this one particular machine? I will summarize.
> > Thanks a lot.
>
> [ originally summarizing that I got many answers, but none of them worked.
> I added one additional piece of information: ]
>
> I realized that I forgot to look at a key item when I initially started
> working on the problem. /var/adm/messages on banjo contains the following
> lines every time I try to mount this filesystem:
>
> Mar 29 11:27:21 banjo automountd[6411]: servers alexandria13 not responding: RPC: Timed out
> Mar 29 11:27:31 banjo automountd[6411]: servers alexandria13alexandria13,alexandria not responding: RPC: Timed out
> Mar 29 11:27:41 banjo automountd[6411]: servers alex/export/srcalexandria13 not responding: RPC: Timed out
> Mar 29 11:27:51 banjo automountd[6411]: servers alex/export/srcalexandria13alexandria13,alexandria not responding: RPC: Timed out
>
> (I start automountd with the -D SUBNET=13 option, which sets ${SUBNET} equal
> to 13)
>
> As the entry in the auto.stage file above shows, it should by trying the
> server "alexandria13" and if that doesn't work, "alexandria". Both machine
> names exist and are pingable. I think that I have two problems here.
> The first is that alexandria13 is not responding to an RPC call, even though
> no other machine has this problem. The second problem is the bizarre way
> that banjo is interpreting the machine name in the 2nd, 3rd, and 4th lines
> of the messages file. Has anyone else ever seen this? This is getting
> curiouser and curiouser...
Thanks for all of the suggestions. I think the problem is basically a
bug in solaris 2.3, since my Solaris 2.4 machines do not have this problem.
I'll just upgrade banjo to 2.4.
Thanks to:
pburyk@leis.leis.bellcore.com (Patrick Buryk)
epl@caps.kodak.com (Gene Loriot (epl@kodak.com))
Anchi Zhang <anchi@Starbase.NeoSoft.COM>
murphy!acmcr!vr@uunet.uu.net (Vicki Rosenzweig)
Trevor Morrison <trevor@if.ssci.liv.ac.uk>
Leonard Sitongia <sitongia@zia.hao.ucar.edu>
gratz@ite101.inf.tu-dresden.de (Achim Gratz)
+-----------------------------------------------------------------------+
| Christopher L. Barnard O When I was a boy I was told that |
| cbarnard@cs.uchicago.edu / \ anybody could become president. |
| (312) 702-8850 O---O Now I'm beginning to believe it. |
| http://cs-www.uchicago.edu/~cbarnard --Clarence Darrow |
| Cyber Rights Now: Accept No Compromise. |
+----------PGP public key available via finger or PGP keyserver---------+
Comments
Got something to say?
You must be logged in to post a comment.
