From: Ian Kent <raven@themaw.net>
To: hpc.admin@uea.ac.uk
Cc: autofs@linux.kernel.org
Subject: Re: autofs problem
Date: Mon, 14 Mar 2011 23:08:30 +0800 [thread overview]
Message-ID: <1300115310.6620.8.camel@perseus> (raw)
In-Reply-To: <1300114769.6620.2.camel@perseus>
On Mon, 2011-03-14 at 22:59 +0800, Ian Kent wrote:
> On Mon, 2011-03-14 at 10:09 +0000, hpc.admin@uea.ac.uk wrote:
> > Hello Ian,
> >
> > Thank you for your reply. The contents of /etc/sysconfig/autofs are:
> >
> > [root@head00 ~]# grep -v '^#' /etc/sysconfig/autofs
> > TIMEOUT=300
> > BROWSE_MODE="no"
> > USE_MISC_DEVICE="yes"
> > [root@head00 ~]#
> >
> > When the machine boots up, it completely fails to mount /home/<username>; it
> > just complains that /home/<username> doesn't exist. The contents of
> > /var/log/messages then show the message given below, thus I assume that they
> > are related. Do let me know if you require further information. Googling
> > around for the error message hasn't been very successful :-(
>
> Failing to open a control file handle on an automount is fatal.
> I don't know why that's happening.
>
> We would probably need to add some log prints to get more information.
Where does the map come from, is it network based?
If it is and you use NetworkManager, have you checked to see if
automount is starting up during NetworkManager initialization?
In the log you show why do we see automount shutting down, then starting
up, you say the problem is at boot but the example log doesn't show an
error at boot?
And, did you check if /home was already mounted after the shutdown and
before that startup in the log.
>
> >
> > Thanks for your help,
> > Wadud.
> >
> > >-----Original Message-----
> > >From: hpc.admin-bounces@uea.ac.uk [mailto:hpc.admin-bounces@uea.ac.uk] On
> > >Behalf Of Ian Kent
> > >Sent: Sunday, March 13, 2011 1:29 AM
> > >To: hpc.admin@uea.ac.uk
> > >Cc: autofs@linux.kernel.org
> > >Subject: Re: [autofs] autofs problem
> > >
> > >On Tue, 2011-03-08 at 11:24 +0000, hpc.admin@uea.ac.uk wrote:
> > >> Hello,
> > >>
> > >> I am experiencing autofs problems with my Centos 5.5 system. Upon boot,
> > the
> > >> mount fails with the following error messages (created by passing the -d
> > >> option in the automount):
> > >>
> > >> Mar 8 10:38:19 cn024 automount[6395]: do_notify_state: signal 15
> > >> Mar 8 10:38:19 cn024 automount[6395]: master_notify_state_change: sig 15
> > >> switching /home from 1 to 5
> > >> Mar 8 10:38:19 cn024 automount[6395]: st_prepare_shutdown: state 1 path
> > >> /home
> > >> Mar 8 10:38:19 cn024 automount[6395]: expire_proc: exp_proc = 1090562368
> > >> path /home
> > >> Mar 8 10:38:19 cn024 automount[6395]: expire_cleanup: got thid
> > 1090562368
> > >> path /home stat 0
> > >> Mar 8 10:38:19 cn024 automount[6395]: expire_cleanup: sigchld: exp
> > >> 1090562368 finished, switching from 5 to 7
> > >> Mar 8 10:38:19 cn024 automount[6395]: st_shutdown: state 5 path /home
> > >> Mar 8 10:38:19 cn024 smartd[7258]: smartd has fork()ed into background
> > >> mode. New PID=7258.
> > >> Mar 8 10:38:19 cn024 automount[6395]: umount_multi: path /home incl 0
> > >> Mar 8 10:38:19 cn024 automount[6395]: umounted indirect mount /home
> > >> Mar 8 10:38:19 cn024 automount[6395]: automount_path_to_fifo: fifo name
> > >> /var/run/autofs.fifo-home
> > >> Mar 8 10:38:19 cn024 automount[6395]: shut down path /home
> > >> Mar 8 10:38:19 cn024 automount[6395]: autofs stopped
> > >> Mar 8 10:38:28 cn024 automount[7334]: Starting automounter version
> > >> 5.0.1-0.rc2.143.el5, master map auto.master
> > >> Mar 8 10:38:28 cn024 automount[7334]: using kernel protocol version 5.01
> > >> Mar 8 10:38:28 cn024 automount[7334]: lookup_nss_read_master: reading
> > >> master files auto.master
> > >> Mar 8 10:38:28 cn024 automount[7334]: parse_init: parse(sun): init
> > gathered
> > >> global options: (null)
> > >> Mar 8 10:38:28 cn024 automount[7334]: lookup_read_master: lookup(file):
> > >> read entry /home
> > >> Mar 8 10:38:28 cn024 automount[7334]: master_do_mount: mounting /home
> > >> Mar 8 10:38:28 cn024 automount[7334]: automount_path_to_fifo: fifo name
> > >> /var/run/autofs.fifo-home
> > >> Mar 8 10:38:28 cn024 automount[7334]: lookup_nss_read_map: reading map
> > file
> > >> /etc/auto.home
> > >> Mar 8 10:38:28 cn024 automount[7334]: parse_init: parse(sun): init
> > gathered
> > >> global options: rw,intr
> > >> Mar 8 10:38:28 cn024 automount[7334]: do_mount_autofs_indirect: failed
> > to
> > >> create ioctl fd for autofs path /home
> > >> Mar 8 10:38:28 cn024 automount[7334]: handle_mounts: mount of /home
> > failed!
> > >> Mar 8 10:38:28 cn024 automount[7334]: master_do_mount: failed to startup
> > >> mount
> > >> Mar 8 10:38:28 cn024 automount[7334]: no mounts in table
> > >>
> > >> The error messages to note are the last four lines. When I restart the
> > >> daemon, the automount works, but fails after a day or two. The version of
> > >> autofs I am using is:
> > >
> > >What makes you think these are the same problem?
> > >Did you check to see if /home was already mounted when it failed?
> > >What is in your /etc/sysconfig/autofs?
> > >
> > >>
> > >> Name : autofs Relocations: (not relocatable)
> > >> Version : 5.0.1 Vendor: CentOS
> > >> Release : 0.rc2.143.el5_5.6
> > >>
> > >> Any help will be greatly appreciated. Thanks in advance.
> > >>
> > >> ----------
> > >> Wadud Miah
> > >> High Performance Computing Systems Developer
> > >> Research Computing Services, University of East Anglia
> > >> Telephone: 01603 593856
> > >>
> > >> Information Services
> > >> ----------
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> autofs mailing list
> > >> autofs@linux.kernel.org
> > >> http://linux.kernel.org/mailman/listinfo/autofs
> > >
> > >
> > >
> > >_______________________________________________
> > >Hpc.admin mailing list
> > >Hpc.admin@uea.ac.uk
> > >http://www.uea.ac.uk/mailman21/listinfo/hpc.admin
> >
>
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
next prev parent reply other threads:[~2011-03-14 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000501cbdd83$5e9a35d0$1bcea170$@admin@uea.ac.uk>
2011-03-13 1:29 ` autofs problem Ian Kent
2011-03-14 10:09 ` hpc.admin
[not found] ` <000101cbe22f$df5d3900$9e17ab00$@admin@uea.ac.uk>
2011-03-14 14:59 ` Ian Kent
2011-03-14 15:08 ` Ian Kent [this message]
2011-03-08 11:24 hpc.admin
-- strict thread matches above, loose matches on Subject: below --
2004-05-28 7:42 AutoFS problem Giovanni Romanenghi
2004-05-26 15:07 Giovanni Romanenghi
2004-05-28 2:14 ` Ian Kent
2004-05-28 14:23 ` raven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1300115310.6620.8.camel@perseus \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=hpc.admin@uea.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.