Good evening,
I see this bug in Ubuntu 16.04.1 LTS with autofs version 5.1.1-1ubuntu3
when I try to access cifs shares from my NAS.
When I try to access the shares with 'cd' or 'ls' after boot with
network on both sides up and running I got the error message: "File or
Directory not found." After running `sudo systemctl restart
autofs.service` it works like a charme.
Here is my '''/etc/auto.master.d/diskstation.autofs''':
~~~
/home/tronde/diskstation /etc/auto.diskstation
~~~
And my '''/etc/auto.diskstation''':
~~~
music -fstype=cifs,uid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/music
photo -fstype=cifs,uid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/photo
share -fstype=cifs,uid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/share
video -fstype=cifs,uid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/video
home -fstype=cifs,uid=1000,gid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/home
~~~
The service configuration looks like:
~~~
cat /run/systemd/generator.late/graphical.target.wants/autofs.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/autofs
Description=LSB: Automounts filesystems on demand
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
Before=shutdown.target
After=network-online.target
After=remote-fs.target
After=systemd-journald-dev-log.socket
After=ypbind.service
After=nslcd.service
After=slapd.service
Wants=network-online.target
Conflicts=shutdown.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/autofs start
ExecStop=/etc/init.d/autofs stop
ExecReload=/etc/init.d/autofs reload
~~~
The source of this configuration from '''/etc/init.d/autofs''':
~~~
cat /etc/init.d/autofs
#! /bin/sh
#
### BEGIN INIT INFO
# Provides: autofs
# Required-Start: $network $remote_fs $syslog
# Required-Stop: $network $remote_fs $syslog
# Should-Start: ypbind nslcd slapd
# Should-Stop: ypbind nslcd slapd
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Automounts filesystems on demand
# Description: Automounts filesystems on demand
### END INIT INFO
# Location of the automount daemon and the init directory
#
PROG=automount
DAEMON=/usr/sbin/$PROG
NAME=autofs
PIDFILE="/var/run/$NAME.pid"
test -e $DAEMON || exit 0
PATH=/sbin:/usr/sbin:/bin:/usr/bin
export PATH
. /lib/lsb/init-functions
#
# load customized configuation settings
#
if [ -r /etc/default/autofs ]; then
. /etc/default/autofs
fi
start_stop_autofs() {
start-stop-daemon "$@" --pidfile $PIDFILE --exec $DAEMON -- \
$OPTIONS --pid-file $PIDFILE
}
start() {
log_action_begin_msg "Starting $PROG"
if ! grep -qw autofs /proc/filesystems
then
if ! modprobe autofs4 >/dev/null 2>&1
then
log_action_end_msg 1 "failed to load autofs4 module"
return 1
fi
elif [ -f /proc/modules ] && grep -q "^autofs[^4]" /proc/modules
then
log_action_end_msg 1 "autofs kernel module is loaded, autofs4
required"
return 1
fi
if ! start_stop_autofs --start --oknodo --quiet ; then
log_action_end_msg 1 "no valid automount entries defined."
return 1
fi
log_end_msg 0
return 0
}
stop() {
log_action_begin_msg "Stopping $PROG"
if ! start_stop_autofs --stop --retry 5 --oknodo --quiet ; then
log_action_end_msg 1
return 1
fi
log_end_msg 0
return 0
}
reload() {
log_action_begin_msg "Reloading $PROG maps"
if ! start_stop_autofs --stop --signal=HUP --quiet
then
log_action_end_msg 1 "$PROG not running"
return 1
fi
log_action_end_msg 0
return 0
}
forcestart() {
OPTIONS="$OPTIONS --force"
start
}
case "$1" in
start|forcestart|stop|reload)
$1
;;
restart|force-reload)
stop
start
;;
forcerestart)
stop
forcestart
;;
status)
status_of_proc -p $PIDFILE $DAEMON $PROG
;;
*)
echo "Usage: $0
{start|forcestart|stop|restart|forcerestart|reload|force-reload|status}"
exit 1
;;
esac
~~~
This way autofs has no advantage over the manual mount with mount.cifs.
Open this bug and fix ist, please.
Best regards,
Tronde
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pick up some shares
Status in autofs package in Ubuntu:
Invalid
Status in autofs5 package in Ubuntu:
Invalid
Status in upstart package in Ubuntu:
Invalid
Bug description:
I am using autofs to access shares on a Windows XP machine from a
Kubuntu AMD64 machine. The problems applies in both Breezy and
Dapper.
EDIT: confirmed with similar configuration on Intrepid with a NetApp
filer hosting NFS. Server OS removed from summary.
When I first try to access the mount point via cd or in Konqueror it
does not exist. However, if I then restart autofs
(/etc/init.d/autofs restart) everythin then works OK. My config files
are:
auto.master
#
# $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc /etc/auto.misc --timeout=60
#/misc /etc/auto.misc
#/net /etc/auto.net
/petunia /etc/petunia.misc --timeout=60
petunia.misc
#
# $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
#
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# Details may be found in the autofs(5) manpage
cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/tony
chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/chris
shared -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/SharedDocs
linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/linuxbackups
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
