** Tags removed: yakkety zesty
** Summary changed:
- autofs needs to be restarted to pick up some shares
+ [SRU] [xenial] autofs needs to be restarted to pick up some shares
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
htt
Would there be an updated version in the next xenial point release? Is
there any chance to get autofs (5.1.2-1) at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
autofs need
Package upgrade is needed
autofs (5.1.2-1) unstable; urgency=medium
* New upstream release [June 2016] (Closes: #846054).
* Build with "--disable-mount-locking" (Closes: #721331).
* service: fixed path to "kill" utility (Closes: #785563).
* Modernised and converted Vcs URLs to HTTPS.
*
I was able to reproduce the issue on a fresh install of Xenial today.
You could find the degug log at: https://paste.ubuntuusers.de/423433/
** Changed in: autofs (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
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
This still happens to us on 16.04.1 lTS with ldap (+ autofs + nfs).
Why is not fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pick up some
This still happens to us on 14.04.4 with ldap (+ autofs + nss). I'll be
trying the proposed fix #43.
Please reopen this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
autof
This is happening with us on Ubuntu 14.04.3 authenticating against ldap
using sssd. I have changed my /etc/init/autofs.conf as recommended by
Ruben (above #43) and it works for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bu
outdated flavor, report about a newer active version if needed
** Changed in: upstart (Ubuntu)
Status: Confirmed => Invalid
** Changed in: autofs5 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: autofs (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug not
Solution #43 perfectly works on our machines using autofs mounts on LDAP.
Thanks Ruben!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pick up so
I tried a bunch of fixes. Some from this thread. No luck. On Ubuntu
14.04 I ended up simply doing:
AUTOFS_UPSTART=/etc/init/autofs.conf
cat $AUTOFS_UPSTART | sed "s/^start on runlevel.*$/start on (local-filesystems
and net-device-up IFACE!=lo)/" | tee $AUTOFS_UPSTART
works like a charm
--
You
I ha ve the same problem between Synology DS411j NAS shares and a Debian
Wheezy autofs install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pic
Ubuntu 12.04 LTS support here. I can confirm this bug. The automount service
needs to retrieve the automount NFS maps auto_home and auto_group from LDAP
which it is unable to do because the network isn't up yet. To make things a bit
more complicated, these are Kerberized (krb5) NFSv4 mounts.
A
We have the same problems on our clients within our company
(ldap+nfs+autofs, 12.04). Because of this bug we started migrating to
SUSE for new machines. A fix would be really great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug repor
Same for Ubuntu 12.04 LTS. Since this isn't acceptable in a company
environment I've stopped migrating to Ubuntu 12.04 from 10.04. It is
something that has to be fixed before any further upgrades.
The whole thing doesn't work not only for Windows XP shares, it doesn't
for NFS too. I have to restar
** Also affects: autofs5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: autofs5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/4018
I just want to add that I got the same bug on 11.10 and that the
rc.local trick doesn't seem to work but if I run `reload autofs` once as
a local user, it will start to work instantly!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug re
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title
Still present in oneiric 11.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pick up some shares
To manage notifications about this bug go to:
h
FYI, in my case, 11.04, reload autofs is not enough. I need to use
restart autofs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pick up some shar
I maintain a 10.04 LTS based cluster of workstations where each node is subject
to some stress and need to be restarted once in a while. Autofs maps of nfs
shares are communicated via LDAP. Autofs fails to initialize (or even start in
some rare cases) in its default configuration in about 50%
Hello Canonical guys,
I have this problem specially for new and fast machines. Boot is just
too fast. If autofs uses network shares (nis, nis+, ldap), it only can
start autofs after the network is up (upstart bug?). Another solution is
to start immediatelly (for static entries) and, after network
Bug still exists on Natty. A revised script for NetworkManager seems to
fix it for me:
/etc/network/if-up.d/autofs
#!/bin/sh
# Local interface changes are irrelevant to this
if [ "$IFACE" = lo ]; then
exit 0
fi
reload autofs
--
You received this bug notification because you are a member
post #25 did not seem to work for me (10.10).
In my case , NFS entries I need to mount are stored in a NIS server.
as a fix I've created the following file :
--
###/etc/init/waitnis.conf
description "Wait for NIS"
author "moi"
start on starting autofs
task
script
while [ !
Is this an Ubuntu bug? Is there a configuration problem in Ubuntu?
Upstart problem? Or is it an upstream issue? This has been kicking
around for over 5 years now.
How does the workaround in post #25 work? It seems like that would start
autofs as soon as any network device comes up, when what you'd
I had the same bug in the past but with 10.10 everything was smooth.
With Natty 11.04 the bug is hitting again.
When I restart autofs the automounter starts to work as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bu
Still hitting this bug under natty as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pick up some shares
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I can confirm that Hans' upstart configuration change in post #25 fixes
the bug in Karmic 9.10. I didn't notice the start up time being any
slower but I haven't measured it.
--
autofs needs to be restarted to pick up some shares
https://bugs.launchpad.net/bugs/40189
You received this bug notific
I am noticing this in my Maverick installations, and am now seeing it in
some of my 10.04.1 installations as well. I did not have this issue
with 10.04 or previous, though I was (am) affected by the boot priority
of NIS bug (569757), which affects auto mounts.
It seems that Hans' post #25 has all
For me, running Maverick, this problem still exists.
It seems autofs is starting up correctly when changing the upstart
configuration file for autofs.
--- /tmp/autofs.conf.orig 2010-10-12 20:08:12.0 +0200
+++ /etc/init/autofs.conf 2010-10-10 21:25:34.0 +0200
@@ -2,7 +2
Can anyone confirm whether or not this problem still exists in 10.04.1
or 10.10? I'm asking because we pushed out an upstart patch that works
around an issue with writing to /dev/console in the kernel, which was
causing certain services trying to write to /dev/console, not to start.
See http://bug
I also can confirm the problem in Kubuntu 10.04. Autofs is not started
when booting, only with 'service autofs start'. It was working though in
Kubuntu 9.10. So something changed again.
--
autofs needs to be restarted to pick up some shares
https://bugs.launchpad.net/bugs/40189
You received this
Problem is still there in the final release of Ubuntu 10.04. autofs
isn't started at all when booting up, which mean I have to manually
start it each time with a 'service autofs start'.
So far none of the workarounds I tried seem to work. This is pretty
troublesome, as having to manually start aut
I am experiencing what I think is the same problem in 10.04. It wasn't
a problem in any of the versions prior to this on the one machine, but
an upgrade recently caused this to affect ~50% of cold boots.
It's not difficult to solve - once the failed login happens (home is not
mapped), I go to one
I have this problem as well: Ubuntu 9.10 and reading mount points from
an ldap server. The ldap server is running on a guest virtual machine,
while the host itself needs autofs. Tried moving autofs from S19 in the
init scripts to S30 (after libnss-ldap and after qemu-kvm and libvirt-
bin), but that
I'm still seeing this with
automount: files ldap
on 9.10 server x86_64.
seems to work okay once the machine is booted and /etc/init.d/autofs restart is
run.
--
autofs needs to be restarted to pick up some shares
https://bugs.launchpad.net/bugs/40189
You received this bug notification because
Our site configuration stores auto.master in NFS for ease of updating.
(Yes it should perhaps move to LDAP, but that is beyond my control.)
Karmic autofs starts correctly about half of the time, depending on
whether the NFS mount finishes before autofs gets around to reading its
config. (I'm not su
This bug is still at large in Ubuntu 9.10, as observed on the desktop
x86-64 variant.
This may not be reproducible with 'static' configurations where the
automount tables are configured in files, but when they are specified in
nsswitch.conf as 'automount: ldap', this fails to initialise -
restarti
My autofs master map is in LDAP, thus I experience this issue with
Jaunty 9.04 server - this is slightly different, in that NetworkManager
isn't involved here.
autofs needs restarting before network mounts are available, due to
incorrect starting order, as S20autofs is earlier than
S35networking..
The solution by Sebastiaan Veldhuisen above works for me on one machine,
but not on other. Both machines have 9.04. I don't know what could be
the difference.
--
autofs needs to be restarted to pick up some shares
https://bugs.launchpad.net/bugs/40189
You received this bug notification because yo
I also saw this problem while using Ubuntu 8.10 x86_64. I think I may
have found the source of the problem.
I'm using this computer in a corporate environment, where each users
home directory is mounted using autofs, and authentication is done using
NIS.
The ssh daemon and automounting of the us
** Summary changed:
- autofs needs to be restarted to pick up Windows XP shares
+ autofs needs to be restarted to pick up some shares
** Description changed:
I am using autofs to access shares on a Windows XP machine from a
Kubuntu AMD64 machine. The problems applies in both Breezy and Dapp
42 matches
Mail list logo
